EP2564313A2

EP2564313A2 - Terminal services view toolbox

Info

Publication number: EP2564313A2
Application number: EP11777767A
Authority: EP
Inventors: Travis Eby; Ryan Kim; Nadia Fortini
Original assignee: Microsoft Corp
Current assignee: Microsoft Technology Licensing LLC
Priority date: 2010-04-27
Filing date: 2011-04-04
Publication date: 2013-03-06
Also published as: CN102859937A; US20110265009A1; US20160261925A9; EP2564313A4; US20190007749A1; WO2011139450A3; US20130031573A1; WO2011139450A2; US10116999B2

Abstract

The disclosed architecture includes a view toolbox that offers a dynamic view of remote monitors and which enables the user to move quickly between one area and another across all remote monitors. The view toolbox enables the user to customize the view of the remote monitors ranging from fitting the view (remote desktop) of all remote monitors to the local computer display, showing a remote monitor at actual size on the local computer display, showing a dynamic view of each remote monitor, and/or allowing the user to move around the view area of the remote monitors.

Description

TERMINAL SERVICES VIEW TOOLBOX

BACKGROUND

[0001] Businesses are placing more demands on employees to travel. Even for non- employment purposes, users seek to remotely access resources at work and at home. Advances in computing hardware and software enable users to travel with portable device such as laptop computers, for example, and then connect to remote computing systems to access data.

[0002] However, in many cases the remote system has multiple monitors that when accessed remotely presents a view that is difficult to perceive. One existing approach allows the user to work on multiple monitors connected to a remote computer but does not provide a dynamic view of each monitor or a method to quickly navigate from one area to another. Another existing approach allows remote connections; however, this approach minimizes to the actual size of the monitor in order to fit all monitors to the screen, but there is no preview window or a direct way to get to a specific area of the remote computer by dragging the area in a preview window.

SUMMARY

[0003] The following presents a simplified summary in order to provide a basic understanding of some novel embodiments described herein. This summary is not an extensive overview, and it is not intended to identify key/critical elements or to delineate the scope thereof. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.

[0004] The disclosed architecture includes a view toolbox that offers a dynamic view of remote monitors and which enables the user to move quickly between one area and another across all remote monitors. The view toolbox enables the user to customize the view of the remote monitors ranging from fitting the view (remote desktop) of all the remote monitors to the local computer display, showing a remote monitor at actual size on the local computer display, showing a dynamic view of each remote monitor, and/or allowing the user to move around the view area of the remote monitors.

[0005] To the accomplishment of the foregoing and related ends, certain illustrative aspects are described herein in connection with the following description and the annexed drawings. These aspects are indicative of the various ways in which the principles disclosed herein can be practiced and all aspects and equivalents thereof are intended to be within the scope of the claimed subject matter. Other advantages and novel features will become apparent from the following detailed description when considered in conjunction with the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

[0006] FIG. 1 illustrates a view management system in accordance with the disclosed architecture.

[0007] FIG. 2 illustrates a multi-monitor preview of a remote computer system having three monitors over which a remote desktop extends.

[0008] FIG. 3 illustrates an embodiment of the preview window.

[0009] FIG. 4 illustrates a computer-implemented view management method in accordance with the disclosed architecture.

[0010] FIG. 5 illustrates further aspects of the method of FIG. 4.

[0011] FIG. 6 illustrates a block diagram of a computing system that executes a terminal services toolbox in accordance with the disclosed architecture.

DETAILED DESCRIPTION

[0012] The disclosed architecture includes a view toolbox for interacting with applications and data of a multi-monitor remote computer system. The architecture provides a dynamic preview of remote computer desktop via the view toolbox. The current viewable area on the local computer display of a portion of the remote computer desktop is selected via a selection tool (e.g., a movable rectangle) that defines an area on a scaled-down preview of the remote computer system desktop across all monitors.

[0013] The view toolbox enable a user to customize the view of remote monitors between fitting all monitors to the local computer display and showing the remote display at actual size. The view toolbox provides a dynamic view of each remote monitor, updated as the user opens and closes files and performs other actions via the local computer. The view toolbox allows a user to move a rectangle the area of which defines a portion of one or several remote monitors in a scaled-down preview of the remote computer monitors desktop. Moreover, the toolbox allows the user to jump directly from one remote monitor to another remote monitor, for example. If the user can already see all of a remote display on the local computer display, the view toolbox is hidden and a message is presented that explains why the toolbox is not presented. Selecting (e.g., a single click) a remote monitor preview, for example, in the scaled-down preview automatically sets the local display viewing area to the specific remote monitor.

[0014] Reference is now made to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding thereof. It may be evident, however, that the novel embodiments can be practiced without these specific details. In other instances, well known structures and devices are shown in block diagram form in order to facilitate a description thereof. The intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the claimed subject matter.

[0015] FIG. 1 illustrates a view management system 100 in accordance with the disclosed architecture. The system 100 includes a connection component 102 of a local computer 104 that executes remote services 106 (e.g., Windows Live Sync Remote Service by Microsoft Corporation) to establish communications between the local computer 104 and a remote computer 108 having multiple monitors 110 connected thereto. The remote computer 108 presents a remote desktop 112 as encompasses the remote display areas (114 and 116) of the monitors 110, and the local computer 104 has a local display area 118 in a local monitor 120.

[0016] A preview component 122 of the local computer 104 presents a scaled-down preview 124 of the remote desktop 112 in a preview window 126 in the local display area 118. The preview component 122 further presents a preview object 128 on the scaled- down preview 124 that defines an area of the remote desktop 112 that is a current view as presented in the local display area 118.

[0017] In this example, the remote desktop 112 presents an object 130 that is easily viewable when the user is sitting in front of the remote computer 108 (e.g., when at home), but difficult to view remotely (e.g., while on travel) when connecting via the remote services 106 to view the remote desktop 112 and the object 130 (e.g., windows, webpages, documents, etc.) and associated object details (e.g., text, menu options, etc.). The user can now easily view the object 130 (or portions thereof) and associated object details by moving the preview object 128 over the object 130 (or portions thereof) in the preview 126.

[0018] In response, the preview component 122 (in cooperation with the remote services 106) dynamically presents an enlarged view 132 of the object 130 (or portion thereof) and object details circumscribed by the preview object 128 in the scaled-down preview 124, in the local display area 118.

[0019] In operation, the remote computer 108 extends series of drawing commands to the local computer 104. The local computer 104 assembles the commands and presents a copy of the remote display areas (114 and 116) onto the local display area 118 (also, the local desktop). The scaled-down preview window 124 is a copy of the remote desktop 112 that is assembled.

[0020] The preview object 128 enables of the zoom (enlargement) changes and the preview object 128 movement is performed on the local computer 104. In other words, the local computer 104 has information about all of the screens of the remote desktop 112 that may be currently displayed. The local computer 104 receives all the information needed to compute a complete rendering of the remote desktop 112 and the objects, screens, etc., displayed via the remote desktop 112. The bi-directional communications between the local computer 104 and the remote computer 108 is such that the any change on the remote computer 108 is quickly effected on the local display area 118 for data that is in the current view (e.g., for partial object 132) and in the scaled-down preview 124 for user selection and preview.

[0021] The preview component 122 (and remote services 106) interfaces to operating system programs and modules such that in a multi-monitor situation implementation on the remote computer 108 the orientation information of the monitors 110 is obtained as well as monitor resolution and other settings of the remote monitors 110.

[0022] As part of the remote services protocol the remote computer 108 sends this information upon connection by the local computer 104. Moreover, each time the remote desktop 112 changes resolution or monitor configuration the remote computer sends the change information to the local computer 104.

[0023] Put another way, the preview component enables dynamic viewing of the remote desktop in the local display area in response to movement of the preview object relative to the scaled-down preview. The scaled-down preview includes a control object that zooms in on the area defined by the preview object and enlarges the corresponding view presented in the local display area. The scaled-down preview includes a control object that zooms out of the area defined by the preview object and reduces the corresponding view presented in the local display area. The preview object is dragged over the scaled-down preview of the remote desktop and the preview component dynamically changes the current view in the local display area to a new view as defined according to a new area of the preview object.

[0024] The preview component automatically changes the current view to a display area of one of the monitors in response to selection of an object (where objects include actionable graphics in preview component 126 such as a monitor object (the preview object 128), a Min object, Max object, slider objects, etc.) in the scaled-down preview. The preview component automatically sets the local display area to an entire remote display area of a remote monitor in response to selection of an object (e.g., a remote monitor object) in the scaled-down preview of the remote desktop. The preview object is a rectangle through which the area in the scaled-down preview of the remote desktop is viewed. The preview component automatically updates the scaled-down preview of the remote desktop in response to interaction with applications and data of the remote computer via the current view on the local display area.

[0025] FIG. 2 illustrates a multi-monitor preview 200 of a remote computer system having three monitors over which a remote desktop extends. Here, the remote computer uses three monitors (not shown), as represented by the three sections in the scaled-down preview 124. The remote desktop 112 extends across the remote display areas of the three monitors as indicated by three windows one (1), two (2) and three (3). When the user moves (drags) the preview object 128 over the third window, the display area 118 of the local monitor 120 dynamically enlarges and presents the portion 202 of the third window within the preview object 128. The user can then comfortably view and interact with objects such as controls 204 and images and/or other data 206 in the portion 202.

Similarly, when the user moves (drags) the preview object 128 over the first window, the display area 118 of the local monitor 120 dynamically changes and presents the portion 208 of the first window within the preview object 128. The user can then comfortably view and interact with objects such as text in the portion 208.

[0026] FIG. 3 illustrates an embodiment of the preview window 126. The preview window 126 can include a slider control object 300 that enables the user to zoom in or zoom out of the portion of the third window over which the preview object 128 is dragged. In other words, as the user moves the slider toward the Max position, the corresponding portion in the local display area 118 is enlarged to provide the zoom-in effect, and as the user moves the slider toward the Min position the corresponding portion in the local display area 118 is reduced to provide the zoom-out effect. Moving the slider entirely to the left (the lowest Min setting) will show the entire remote desktop 112 in the local display area 1 18.

[0027] The Max and Min objects can be made actionable. For example, when selecting the Min control object, the preview component 126 automatically sets the local display area 118 to present all remote monitors. In an alternative embodiment, the same result can be made to occur when the user clicks the outer edge of the preview area. When selecting the Max control object, the preview component can be made to automatically set the local display area 118 to show a ratio (e.g., 1-to-l) of pixels on the remote monitor(s). Other actions can be utilized as desired.

[0028] The preview component and preview window provide the dynamic view and the ability to change the local view of the remote computer to fit one or all remote monitors as well as dynamic interaction with the user. In other words, a dynamic preview of the remote computer is provided. In one implementation, the current viewable area showing is defined by a rectangle preview object that defines the space for the local display area. Additionally, moving a pointing device such as a mouse over the preview window 128 changes the pointer to a hand so that the user can drag the preview window 128 in order to move from the current view to a different area or monitor for a new view. Selecting on a monitor preview (e.g., third window) automatically sets the local viewing area to the specific monitor selected.

[0029] In an alternative implementation, rather than providing the preview window as an always-on or always-off feature, the user can hover the pointer over a part of the remote desktop as presented in the local display area, and the preview window will automatically appear for a predetermined period of time (e.g., three seconds) and then disappear. In another implementation, hovering the pointer over a toolbox area (e.g., menu item or button) will automatically present the preview window, and then moving away from the toolbox area or buttons will cause the preview window to disappear.

[0030] Included herein is a set of flow charts representative of exemplary

methodologies for performing novel aspects of the disclosed architecture. While, for purposes of simplicity of explanation, the one or more methodologies shown herein, for example, in the form of a flow chart or flow diagram, are shown and described as a series of acts, it is to be understood and appreciated that the methodologies are not limited by the order of acts, as some acts may, in accordance therewith, occur in a different order and/or concurrently with other acts from that shown and described herein. For example, those skilled in the art will understand and appreciate that a methodology could alternatively be represented as a series of interrelated states or events, such as in a state diagram.

Moreover, not all acts illustrated in a methodology may be required for a novel implementation.

[0031] FIG. 4 illustrates a computer-implemented view management method in accordance with the disclosed architecture. At 400, communications is established between a local computer and a remote computer that enables access of applications and data on the remote computer via the local computer. The remote computer has multiple monitors via which a remote desktop is presented. At 402, commands and images associated with the remote desktop of the remote computer are received at the local computer. At 404, a scaled-down preview of the remote desktop is presented on a local computer display. At 406, an area of the scaled-down preview is selected. At 408, a current view of the selected area is presented on the local computer display for user interaction.

[0032] FIG. 5 illustrates further aspects of the method of FIG. 4. Each of the blocks represents a single step that can be added to the method represented by the flow chart of FIG. 4. At 500, the current view is dynamically changed to a new view that corresponds to a new area selected on the scaled-down preview. At 502, the size of the current view in the local computer display is adjusted via an adjustment control associated with the scaled- down preview. At 504, the current view is dynamically changed to a new view of a portion of the remote desktop in response to dragging a preview object over the scaled- down preview. At 506, the scaled-down preview of the remote desktop is updated in response to interaction with the applications and data of the remote computer via the current view on the local computer display. At 508, a notification is presented that explains hiding of the scaled-down preview when a remote monitor is fully presented in the local computer display.

[0033] As used in this application, the terms "component" and "system" are intended to refer to a computer-related entity, either hardware, a combination of software and tangible hardware, software, or software in execution. For example, a component can be, but is not limited to, tangible components such as a processor, chip memory, mass storage devices (e.g., optical drives, solid state drives, and/or magnetic storage media drives), and computers, and software components such as a process running on a processor, an object, an executable, a module, a thread of execution, and/or a program. By way of illustration, both an application running on a server and the server can be a component. One or more components can reside within a process and/or thread of execution, and a component can be localized on one computer and/or distributed between two or more computers. The word "exemplary" may be used herein to mean serving as an example, instance, or illustration. Any aspect or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects or designs.

[0034] Referring now to FIG. 6, there is illustrated a block diagram of a computing system 600 that executes a terminal services toolbox in accordance with the disclosed architecture. In order to provide additional context for various aspects thereof, FIG. 6 and the following description are intended to provide a brief, general description of the suitable computing system 600 in which the various aspects can be implemented. While the description above is in the general context of computer-executable instructions that can run on one or more computers, those skilled in the art will recognize that a novel embodiment also can be implemented in combination with other program modules and/or as a combination of hardware and software.

[0035] The computing system 600 for implementing various aspects includes the computer 602 having processing unit(s) 604, a computer-readable storage such as a system memory 606, and a system bus 608. The processing unit(s) 604 can be any of various commercially available processors such as single-processor, multi-processor, single-core units and multi-core units. Moreover, those skilled in the art will appreciate that the novel methods can be practiced with other computer system configurations, including minicomputers, mainframe computers, as well as personal computers (e.g., desktop, laptop, etc.), hand-held computing devices, microprocessor-based or programmable consumer electronics, and the like, each of which can be operatively coupled to one or more associated devices.

[0036] The system memory 606 can include computer-readable storage (physical storage media) such as a volatile (VOL) memory 610 (e.g., random access memory (RAM)) and non-volatile memory (NON-VOL) 612 (e.g., ROM, EPROM, EEPROM, etc.). A basic input/output system (BIOS) can be stored in the non-volatile memory 612, and includes the basic routines that facilitate the communication of data and signals between components within the computer 602, such as during startup. The volatile memory 610 can also include a high-speed RAM such as static RAM for caching data.

[0037] The system bus 608 provides an interface for system components including, but not limited to, the system memory 606 to the processing unit(s) 604. The system bus 608 can be any of several types of bus structure that can further interconnect to a memory bus (with or without a memory controller), and a peripheral bus (e.g., PCI, PCIe, AGP, LPC, etc.), using any of a variety of commercially available bus architectures.

[0038] The computer 602 further includes machine readable storage subsystem(s) 614 and storage interface(s) 616 for interfacing the storage subsystem(s) 614 to the system bus 608 and other desired computer components. The storage subsystem(s) 614 (physical storage media) can include one or more of a hard disk drive (HDD), a magnetic floppy disk drive (FDD), and/or optical disk storage drive (e.g., a CD-ROM drive DVD drive), for example. The storage interface(s) 616 can include interface technologies such as EIDE, ATA, SAT A, and IEEE 1394, for example.

[0039] One or more programs and data can be stored in the memory subsystem 606, a machine readable and removable memory subsystem 618 (e.g., flash drive form factor technology), and/or the storage subsystem(s) 614 (e.g., optical, magnetic, solid state), including an operating system 620, one or more application programs 622, other program modules 624, and program data 626.

[0040] The one or more application programs 622, other program modules 624, and program data 626 can include the entities and components of the system 100 of FIG. 1, the entities and components of the system 200 of FIG. 2, the view and components of FIG. 3, and the methods represented by the flowcharts of Figures 4-5, for example.

[0041] Generally, programs include routines, methods, data structures, other software components, etc., that perform particular tasks or implement particular abstract data types. All or portions of the operating system 620, applications 622, modules 624, and/or data 626 can also be cached in memory such as the volatile memory 610, for example. It is to be appreciated that the disclosed architecture can be implemented with various

commercially available operating systems or combinations of operating systems (e.g., as virtual machines).

[0042] The storage subsystem(s) 614 and memory subsystems (606 and 618) serve as computer readable media for volatile and non-volatile storage of data, data structures, computer-executable instructions, and so forth. Such instructions, when executed by a computer or other machine, can cause the computer or other machine to perform one or more acts of a method. The instructions to perform the acts can be stored on one medium, or could be stored across multiple media, so that the instructions appear collectively on the one or more computer-readable storage media, regardless of whether all of the instructions are on the same media.

[0043] Computer readable media can be any available media that can be accessed by the computer 602 and includes volatile and non-volatile internal and/or external media that is removable or non-removable. For the computer 602, the media accommodate the storage of data in any suitable digital format. It should be appreciated by those skilled in the art that other types of computer readable media can be employed such as zip drives, magnetic tape, flash memory cards, flash drives, cartridges, and the like, for storing computer executable instructions for performing the novel methods of the disclosed architecture. [0044] A user can interact with the computer 602, programs, and data using external user input devices 628 such as a keyboard and a mouse. Other external user input devices 628 can include a microphone, an I (infrared) remote control, a joystick, a game pad, camera recognition systems, a stylus pen, touch screen, gesture systems (e.g., eye movement, head movement, etc.), and/or the like. The user can interact with the computer 602, programs, and data using onboard user input devices 630 such a touchpad, microphone, keyboard, etc., where the computer 602 is a portable computer, for example. These and other input devices are connected to the processing unit(s) 604 through input/output (I/O) device interface(s) 632 via the system bus 608, but can be connected by other interfaces such as a parallel port, IEEE 1394 serial port, a game port, a USB port, an IR interface, etc. The I/O device interface(s) 632 also facilitate the use of output peripherals 634 such as printers, audio devices, camera devices, and so on, such as a sound card and/or onboard audio processing capability.

[0045] One or more graphics interface(s) 636 (also commonly referred to as a graphics processing unit (GPU)) provide graphics and video signals between the computer 602 and external display(s) 638 (e.g., LCD, plasma) and/or onboard displays 640 (e.g., for portable computer). The graphics interface(s) 636 can also be manufactured as part of the computer system board.

[0046] The computer 602 can operate in a networked environment (e.g., IP-based) using logical connections via a wired/wireless communications subsystem 642 to one or more networks and/or other computers. The other computers can include workstations, servers, routers, personal computers, microprocessor-based entertainment appliances, peer devices or other common network nodes, and typically include many or all of the elements described relative to the computer 602. The logical connections can include

wired/wireless connectivity to a local area network (LAN), a wide area network (WAN), hotspot, and so on. LAN and WAN networking environments are commonplace in offices and companies and facilitate enterprise-wide computer networks, such as intranets, all of which may connect to a global communications network such as the Internet.

[0047] When used in a networking environment the computer 602 connects to the network via a wired/wireless communication subsystem 642 (e.g., a network interface adapter, onboard transceiver subsystem, etc.) to communicate with wired/wireless networks, wired/wireless printers, wired/wireless input devices 644, and so on. The computer 602 can include a modem or other means for establishing communications over the network. In a networked environment, programs and data relative to the computer 602 can be stored in the remote memory/storage device, as is associated with a distributed system. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers can be used.

[0048] The computer 602 is operable to communicate with wired/wireless devices or entities using the radio technologies such as the IEEE 802.xx family of standards, such as wireless devices operatively disposed in wireless communication (e.g., IEEE 802.11 over- the-air modulation techniques) with, for example, a printer, scanner, desktop and/or portable computer, personal digital assistant (PDA), communications satellite, any piece of equipment or location associated with a wirelessly detectable tag (e.g., a kiosk, news stand, restroom), and telephone. This includes at least Wi-Fi (or Wireless Fidelity) for hotspots, WiMax, and Bluetooth™ wireless technologies. Thus, the communications can be a predefined structure as with a conventional network or simply an ad hoc

communication between at least two devices. Wi-Fi networks use radio technologies called IEEE 802.1 lx (a, b, g, etc.) to provide secure, reliable, fast wireless connectivity. A Wi-Fi network can be used to connect computers to each other, to the Internet, and to wire networks (which use IEEE 802.3-related media and functions).

[0049] The illustrated and described aspects can be practiced in distributed computing environments where certain tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in local and/or remote storage and/or memory system.

[0050] What has been described above includes examples of the disclosed architecture. It is, of course, not possible to describe every conceivable combination of components and/or methodologies, but one of ordinary skill in the art may recognize that many further combinations and permutations are possible. Accordingly, the novel architecture is intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims. Furthermore, to the extent that the term

"includes" is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term "comprising" as "comprising" is interpreted when employed as a transitional word in a claim.

Claims

CLAIMS What is claimed is:

1. A computer-implemented view management system having computer readable media that store executable instructions executed by a processor, comprising:

a connection component of a local computer that executes remote services to establish communications between the local computer and a remote computer having multiple monitors connected thereto, the remote computer presenting a remote desktop across the monitors and the local computer having a local display area; and

a preview component of the local computer that presents a scaled-down preview of the remote desktop in the local display area, the preview component further presents a preview object on the scaled-down preview that defines an area of the remote desktop that is a current view as presented in the local display area.

2. The system of claim 1, wherein the preview component enables dynamic viewing of the remote desktop in the local display area in response to movement of the preview object relative to the scaled-down preview.

3. The system of claim 1, wherein the scaled-down preview includes a control object that when selected zooms in on the area defined by the preview object and enlarges the corresponding view presented in the local display area.

4. The system of claim 1, wherein the scaled-down preview includes a control object that when selected zooms out of the area defined by the preview object and reduces the corresponding view presented in the local display area.

5. The system of claim 1, wherein the preview object is dragged over the scaled-down preview of the remote desktop and the preview component dynamically changes the current view in the local display area to a new view as defined according to a new area of the preview object.

6. The system of claim 1, wherein the preview component automatically changes the current view to a display area of one of the monitors in response to selection of the one of the monitors in the scaled-down preview.

7. The system of claim 1, wherein the preview component automatically sets the local display area to an entire remote display area of a remote monitor in response to selection of the remote monitor in the scaled-down preview of the remote desktop.

8. The system of claim 1, wherein the preview object is a rectangle through which the area in the scaled-down preview of the remote desktop is viewed.

9. The system of claim 1, wherein the preview component automatically updates the scaled-down preview of the remote desktop in response to interaction with applications and data of the remote computer via the current view on the local display area.

10. A computer-implemented view management method executed via a processor, comprising:

establishing communications between a local computer and a remote computer that enables access of applications and data on the remote computer via the local computer, the remote computer having multiple monitors via which a remote desktop is presented;

receiving at the local computer commands and images associated with the remote desktop of the remote computer;

presenting a scaled-down preview of the remote desktop on a local computer display;

selecting an area of the scaled-down preview; and

presenting a current view of the selected area on the local computer display for user interaction.

11. The method of claim 10, further comprising dynamically changing the current view to a new view that corresponds to a new area selected on the scaled-down preview.

12. The method of claim 10, further comprising adjusting size of the current view in the local computer display via an adjustment control associated with the scaled- down preview.

13. The method of claim 10, further comprising dynamically changing the current view to a new view of a portion of the remote desktop in response to dragging a preview object over the scaled-down preview.

14. The method of claim 10, further comprising updating the scaled-down preview of the remote desktop in response to interaction with the applications and data of the remote computer via the current view on the local computer display.

15. The method of claim 10, further comprising presenting a notification that explains hiding of the scaled-down preview when a remote monitor is fully presented in the local computer display.