US9270785B2 - System and method for a distributed virtual desktop infrastructure - Google Patents
System and method for a distributed virtual desktop infrastructure Download PDFInfo
- Publication number
- US9270785B2 US9270785B2 US13/651,886 US201213651886A US9270785B2 US 9270785 B2 US9270785 B2 US 9270785B2 US 201213651886 A US201213651886 A US 201213651886A US 9270785 B2 US9270785 B2 US 9270785B2
- Authority
- US
- United States
- Prior art keywords
- computer
- client
- memory state
- virtual machine
- desktop
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active, expires
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
-
- H04L67/42—
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
- G06F21/41—User authentication where a single sign-on provides access to a plurality of computers
-
- G06F9/4445—
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
- G06F9/452—Remote windowing, e.g. X-Window System, desktop virtualisation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
Definitions
- This invention relates generally to virtual desktop infrastructures and, more specifically, to systems and methods for providing, executing, and/or interacting with a distributed virtual desktop infrastructure.
- VDIs virtual desktop infrastructures
- thin clients used by end-users to access the VDI sessions generally serve no greater purpose than normal thick clients.
- the price differential between a suitably configured thin client and a fully robust thick client is small.
- users often want or need to perform some local processing while accessing a VDI, which results in them accessing their VDI session from a traditional laptop or desktop computing system.
- an object of the present invention to provide systems and methods for providing, executing, and/or interacting with distributed VDIs that address some or all of the above-mentioned drawbacks associated with existing systems.
- a computer-implemented method for providing distributed virtualized desktops the method performed on at least one computer including at least one processor, the method comprising: receiving, at a first computer, user credential data for at least one user; transmitting, to a management server, at least a portion of the user credential data and identifying information of the first computer; receiving, from central management server, an identification of a home system for the at least one user based at least partially on the user credential data, the home system comprising a second computer executing at least one virtual machine including a desktop; and receiving, at the first computer, display data from the second computer, the display data configured to generate a representation of at least a portion of the desktop on the first computer, such that the at least one user is able to access the desktop while the at least one virtual machine on the second computer is executing.
- the first computer and the second computer comprise a client management application configured to communicate with the management server.
- the first computer and the second computer are in communication through a local area network (LAN).
- the display data from the second computer is received by the first computer through a direct connection facilitated by a traversal of at least one network address translation (NAT) gateway.
- the computer-implemented method may further include the steps of receiving a copy of a memory state from the first computer; and identifying at least one portion of the memory state that was modified during the receiving of the copy of the memory state from the first computer.
- the method may continue with the steps of receiving a copy of the at least one portion of the memory state; identifying at least one other portion of the memory state that was modified during the receiving of the copy of the at least one portion of the memory state, wherein the at least one other portion of the memory state is a subset of the at least one portion of the memory state; and receiving a copy of the at least one other portion of the memory state. It will be further appreciated that the method may further involve repeatedly identifying parts of the memory state that changed during a previous iteration of copying and receiving the identified parts of the memory state until no further changed parts of the memory state are identified or the changed parts of the memory state are below a predetermined threshold.
- a system for providing distributed virtualized desktops comprising at least one management server including at least one processor, the at least one management server configured to: process user credential data for a user and device identification data for a first computing device, the user credential data and the device identification data received from the first computing device; determine a home system for the user based at least partially on at least a portion of the user credential data and the device identification data, the home system comprising a second computing device executing at least one virtual machine including at least one desktop; and transmit, to the first computing device, data configured to facilitate a direct connection between the first computing device and the second computing device, such that the first computing device displays the at least one desktop while the at least one virtual machine continues to execute on the second computing device.
- the management server may be further configured to cause at least one of the first and second computing devices to migrate the virtual machine from the second computing device to the first computing device while the virtual machine is executing.
- the virtual machine may be migrated by copying a memory state of the virtual machine from the second computer, identifying at least one portion of the memory state that changed during the copying of the memory state, and copying the at least one portion of the memory state from the second computing device.
- the first and second computing devices may comprise a client management application configured to communicate with the management server.
- the first and second computing devices may be in communication through a local area network (LAN).
- the management server may be further configured to receive at least one of a desktop state and a desktop status for at least one desktop on the second computing device. The at least one of a desktop state and a desktop status may be transmitted to the first computing device at predetermined intervals.
- the management server may be further configured to power on at least one of the first computing device and the second computing device.
- a distributed virtual desktop infrastructure system comprising at least one management server comprising at least one processor, the at least one management server configured to provide a plurality of centrally managed virtual machines to a plurality of client systems, the at least one management server further configured to determine a home system of the plurality of client systems for at least one user; and a plurality of client management applications in communication with the at least one management server, the plurality of client management applications configured to execute on the plurality of client systems, and display, on at least one client system, a virtual desktop of at least one virtual machine executing on the home system.
- the distributed virtual desktop infrastructure system if the home system is local to a first computing device being used by the at least one user, the virtual desktop is displayed from the at least one virtual machine local to the first computing device.
- the plurality of client management applications are configured to migrate the at least one virtual machine from the home system to the at least one client system while the at least one virtual machine is executing on the home system.
- the distributed virtual desktop infrastructure system may further include a storage area network in communication with the plurality of client systems.
- the home system is at least one other client system of the plurality of systems, and the at least one client system displays the virtual desktop through a communication link with the at least one other client system.
- FIG. 1 is a schematic view of a distributed VDI system according to the principles of the present invention
- FIG. 2 is another schematic view of a distributed VDI system according to the principles of the present invention.
- FIG. 3 is a further schematic view of a distributed VDI system according to the principles of the present invention.
- FIG. 4 is a flow diagram for a method for providing a distributed VDI system according to the principles of the present invention.
- FIG. 5 is a flow diagram for a method for migrating a virtual machine in a distributed VDI system according to the principles of the present invention.
- the terms “communication” and “communicate” refer to the receipt or transfer of one or more signals, messages, commands, and/or other types of data.
- one unit or component to be in communication with another unit or component means that the one unit or component is able to receive data from and/or transmit data to the other unit or component. This may refer to a direct or indirect connection that may be wired and/or wireless in nature.
- two units or components may be in communication with each other even though the data transmitted may be modified, processed, routed, etc., between the first and second unit or component.
- a first unit may be in communication with a second unit even though the first unit passively receives data, and does not actively transmit data to the second unit.
- a first unit may be in communication with a second unit if an intermediary unit processes data from one unit and transmits processed data to the second unit. It will be appreciated that numerous other arrangements are possible.
- the distributed video desktop infrastructure (VDI) system may be used with a system for providing centrally managed virtual machines (VM) in the form of disk images and/or other forms of data that are distributed to and executed by client systems on a hypervisor platform.
- VM virtual machines
- the systems and methods described in incorporated U.S. patent application Ser. No. 12/338,452 including but not limited to the virtual workspaces management architecture and the workspaces execution engine described therein, may be used to provide and execute the virtual machines.
- a management server may centrally store several virtual machines and allow for the central management of the same.
- the management server may provide disk images of the virtual machines to client systems for execution of the virtual machines locally on the client systems.
- various other implementations of the distributed VDI system may be possible.
- management server refers to one or more computing devices capable of transmitting and receiving data from multiple client systems, including hardware and/or software components, modules, functions, and/or the like.
- the management server includes or has access to one or more data structures including identifying information for the multiple client systems.
- data structures may include, for example, relational databases that associate multiple users with respective client systems.
- home system refers to a client system associated with and/or assigned to a particular user.
- the databases may also indicate what client systems do not have a particular user associated with and/or assigned to it. Identifying information for the multiple client systems may include, as an example, system names, IP addresses, MAC addresses, and/or the like.
- the management server may also provide connection information for client systems, such as port numbers, statuses, operating systems, memory information, and/or the like, to facilitate direct connections (e.g., remote desktop protocol (RDP) sessions, or other means) between client systems.
- RDP remote desktop protocol
- client system refers to one or more computing devices including hardware and/or software configured to communicate with a network and the management server.
- each client system is provided with a client management application that runs as a background process and helps manage the distributed VDI from the client-side.
- the client management application is a daemon that runs as a background process on a client system.
- the processing capabilities of the client systems are used to provide at least a portion of the distributed VDI, and facilitate the functionality of the distributed VDI system described herein.
- embodiments of the client systems may take on various forms.
- the distributed VDI system 1000 includes client systems client 1 102 , client 2 104 , and client 3 106 . Further, the system 1000 includes a management server 114 in communication with each of the client systems 102 , 104 , 106 . As can be seen, the client systems 102 , 104 , 106 communicate with the management server 114 through a network environment 116 , such as a local area network (LAN), a wide area network (WAN), the Internet, and/or the like.
- LAN local area network
- WAN wide area network
- the Internet and/or the like.
- client 1 102 and client 2 104 are in communication with each other through a communication link 118 , such as a direct connection, that is not routed through the management server 114 .
- client 1 102 is a home system for a first user
- client 2 104 is a home system for a second user.
- client 1 102 is associated with a virtual machine, including a desktop 108 , that is being executed on client 1 102 .
- client 2 104 displays the desktop 108 (i.e., as a virtual desktop) of the virtual machine assigned to and/or associated with the first user, while that virtual machine is simultaneously executing on client 1 102 .
- This remote desktop communication 118 may be performed without having to stop the execution of the virtual machine and virtual desktop 108 on client 1 102 .
- the first user is able to remotely access and interact with the desktop 108 on client 2 while the client 1 102 client system performs the necessary processing to run that virtual desktop 108 .
- the communication link 118 for the virtual desktop 108 may be established through the remote desktop protocol (RDP), or by any other means.
- Client 3 106 is in communication with the management server 114 and is executing a virtual machine including a desktop 110 .
- credentials refer to identifying and/or authenticating data for at least one user.
- a particular user's credentials may include a name, login, password, IP address, identification number, key, certificate, and/or the like.
- credentials may also include any form of data input that serves to identify and/or authenticate a user, such as biometric inputs, visual input, audible inputs, and the like.
- the client system determines whether the client system is a home system for that particular user, based at least on the user's credentials. With continued reference to FIG. 1 , the determination may also be performed by the management server 114 , which receives at least a portion of the credential data and, in some instances, identifying information from a client system (e.g., client 2 104 ) and makes a determination based on the received data.
- a client system e.g., client 2 104
- the client system (e.g., client 2 104 ) being used first determines if it is the home system for the user based on information it has locally and, if the client system 104 is not the home system for the user, it communicates identifying information for the client system 104 and/or credential data to the management server 114 and receives data configured to allow the client system 104 to establish a communication link 118 with a second client system (e.g., client 1 102 ) that is the home system for that user, and is executing a virtual machine including a desktop 108 .
- a second client system e.g., client 1 102
- the desktops of the remote virtual machines are presented transparently on the client systems 102 , 104 , 106 .
- the local user of that particular client system is provided with substantially the same experience as if he or she were using his or her home system locally.
- the client management application may immediately display the user's desktop provided by a virtual machine executing on that system. Otherwise, the client system may identify the home system for the local user, establish communication with the home system, and display a virtual desktop of a virtual machine that is simultaneously executing on the home system.
- the home system for a particular user can be changed from one client system to another client system by storing the user's data on a storage area network (SAN) and allowing different client systems in the SAN to mount that data.
- a SAN-based migration of a home system can be provided if the user's virtual machines are not actively running on the home system when the user logs onto a different client system, or if the user wants to move his home system through a home relocation process.
- a home relocation process may be initiated in various other ways, and using various methods of data transfer.
- the home system receives a command to unmount the SAN logical memory unit (e.g., one or more logical unit numbers (LUN), one or more SCSI device IDs, and/or the like) and clears information that it stored indicating that it is the home system for that user.
- the client system that will become the new home system for the user i.e., the client system that the virtual machine will be migrated to
- the client system that will become the new home system for the user is caused to mount the SAN LUN, or other memory unit(s), and become the home system for that user.
- Client systems client 1 102 , client 2 104 , and client 3 106 are in communication with a SAN 120 , including a network storage device 124 .
- the SAN is also in communication with an external network 122 , such as the internet.
- a management server 114 is in communication with the external network 122 and a management server storage device 126 , including a client information database 128 .
- a user at client 2 104 may wish to use his or her home system on client 2 104 .
- the credentials are communicated to the management server 114 .
- the management server 114 uses the client information database 128 to determine that the user (e.g., user 1 ) is associated with client 1 102 .
- user 1 is associated with client 1 in the client information database 128
- user 2 is associated with client 2 104
- client 3 106 does not have a particular user associated with it.
- the management server After identifying client 1 102 as the home system for the user local to client 2 104 , communicates this information to client 2 104 , and the client management application executing thereon. With the information that it receives, the client system client 2 104 establishes communication with client system client 1 102 over a connection 118 through the SAN 120 .
- a port number and/or internal IP address of client 1 102 may be provided to client 2 104 , although other identifiers may be used. If client 2 and client 1 are not part of the same SAN 120 , an external IP address and port number may be used to assist in connecting client 1 102 and client 2 104 through a NAT gateway.
- a user may want to migrate his or her home system in order to receive a fully localized run-time environment, or if errors are encountered in communicating between local client systems to the remote virtual machines running on the current home system for the user.
- a home relocation process may be performed to migrate the virtual machine by first transferring a copy of the virtual machine memory state while the virtual machine is running. Since the virtual machine is running, this process can be performed transparently while the user is interacting with the virtual machine through RDP, or by some other method.
- the user e.g., user 1
- client 2 104 may wish to migrate the virtual machine, including the desktop 108 , from client 1 102 to client 2 104 .
- a live migration may be performed while the virtual machine is accessed on the client system client 1 102 , utilizing the SAN and a memory storage device 124 in communication with the SAN 120 , client 1 102 and client 2 104 .
- client 1 102 has mounted at least a portion of the memory storage device 124 and receives a command to migrate the virtual machine to client 2 104 .
- client 1 102 transfers the entire memory state of the virtual machine to the memory storage device 124 and tracks the portions of memory (e.g., memory pages, blocks, or other units) that are changed during the transfer.
- the tracked portions of memory are subsequently transferred, and the process of tracking new changes is repeated until there are no changed portions of memory, until a predetermined number of iterations have been performed, until a predetermined time interval expires, and/or until the number of changed portions of memory is below a predetermined threshold.
- FIG. 5 A suitable home relocation process is depicted by FIG. 5 , although it will be appreciated that any number of methods may be employed.
- the virtual machine memory state of a first device is migrated to a second device within a SAN.
- the memory units that change are tracked.
- this method shows a looping process that occurs until the number of changed units is less than a predetermined value
- other parameters may be used to determine when to stop tracking and transferring changed memory units. For example, and as explained herein, the looping may occur until there are no changed portions of data, until the amount of changed portions of data drops below a predefined threshold, and/or until a predefined number of iterations have been performed.
- portions of data e.g., memory pages, blocks, or other units
- portions of data may be tracked by a tracking function of the client management application.
- the process of tracking changed portions of data during a transfer of the data may be performed repeatedly, as already explained, until there are no changed portions of data, until the amount of changed portions of data drops below a predefined threshold, and/or until a predefined number of iterations have been performed.
- the virtual machine is paused and the final portions of changed data are transferred.
- the complete virtual machine state is present on both client systems.
- the virtual machine files are then closed on the current home system and the LUN is unmounted from that client system.
- the LUN can then be mounted on the new home system (i.e., a target client system) and the virtual machine files reopened.
- the RDP session or other connection previously used to remotely access the virtual machine and desktop can then be terminated and a new desktop can be created on the new home system to resume the virtual machine locally.
- the functionality of the distributed VDI system 1000 may appear to be the same to an end user regardless of the client system used by that user.
- FIG. 4 a flow diagram is shown for a method for providing the distributed VDI to client systems according to one preferred and non-limiting embodiment of the present invention.
- the method begins by a user providing credential information to a first device (i.e., client system). For example, a user may approach a client system and enter credentials into a login prompt, scan a smartcard, or otherwise provide credentials. If the client system is the user's home system (e.g., a client system that is assigned to and/or associated with the user), the user will immediately see the normal, local desktop for that system.
- the client system If the client system is not the user's home system, the client system provides access to their desktop(s), running on their home system, as if executing locally. In this latter circumstance, any desktops that actually do run on the client system may not be visible to the user. If the user does not have a home system assigned to and/or associated with it, and the client system is not associated with and/or assigned to any user, then the client system may be assigned and/or associated with that user, the client system becoming that user's home system. If the client system is associated and/or assigned to another user, the user may be assigned a further client system as its home system.
- a transfer of the user's desktops can be completed as described herein.
- the desktop migration may be controlled by network policy on a managed LAN and/or SAN, as an example.
- the management server 114 includes one or more protocols to perform a number of functions.
- the management server 114 may be configured to communicate to a client system what user is associated with and/or assigned to the client system, and associate and/or assign an “unowned” client system (i.e., not established a home system for any particular user) to be a home system for a user.
- the management server 114 may be configured to communicate to a client system to indicate that a different client system is being utilized to access the desktop(s) associated with the user's home system. Such an indication may cause the client management application to change the frequency that it updates the management server 114 , reducing the check-in time with the server 114 .
- the client management application may manage client identifying information for the client system the application is running on, and transmit the same to the management server 114 and/or other client management applications running on different client systems.
- the client identifying information may be used by the different client systems in accessing the virtual machine This information may include, for example, an IP tuple to identify each client system and/or desktop that may be used to initiate RDP sessions, such as an IP address and port number.
- the client systems communicating with each other are not on the same LAN, or are otherwise behind Network Address Translation (NAT) gateways
- NAT Network Address Translation
- the client identifying information for a remote client system may be used by a local connecting client system to traverse the NAT gateway of the other client system or otherwise facilitate the establishment of a communication link. For example, if a NAT mode is in effect, the client management application may use port forwarding to provide remote access to another client management application running on a different client system.
- NAT Network Address Translation
- the client identifying information for a client system may also include a state and/or status of each desktop on that client system. This identifying information allows for other client systems to implement an interface that gives the appearance that the desktop running on the client system is running locally on the other client systems.
- the other client systems, connecting to the client system remotely, may receive this identifying information by way of the management server on a regular basis, maintaining the security of the client system such that it may prevent incoming connections and only allow outgoing connections to the management server.
- the client management application may also be used to control the state of each desktop running on a client system (e.g., client 1 102 ).
- the client management application may be able to start a stopped virtual machine, or stop an executing virtual machine
- a client system e.g., client 2 104
- the home system for that user may communicate requests to the management server 114 to change the state of the virtual machine executing on the user's home system 102 .
- the management server 114 would then provide a request to the home system 102 the next time it polls. Therefore, the client system 102 being accessed remotely would communicate with the management server 114 at a rapid frequency.
- varying frequencies, and non-frequent polling may be used as well.
- the communication exchange between the home system 102 and the client system 104 being used may involve the exchange of messages, such that the home system sends state changes and receives commands, and the client system 104 being used receives state changes and sends commands.
- the frequency of these communications may be set by administrative policy, or may be preset by the client management application and/or management server 114 .
- the client management application running on the client 2 104 client system receives graphical data from the client 1 102 client system.
- the client management application running on the client 1 102 client system may be configured to generate graphical user interface (GUI) data, such as information conveyed in extended mark-up language (XML) format or related metadata, and transmit the same to the management server 114 .
- GUI graphical user interface
- the client management application may create a window manager workspace and provide a full-screen instance of the desktop in that workspace using the identifying information of the client 1 102 client system received from the management server 114 .
- the window manager workspace may be treated like any other virtual machine workspace by the window manager workspace.
- the workspace may be run in the Dom 0 or DomS domains with a hypervisor client.
- the client system being used by the user transmits a command to the management server 114 .
- State changes are displayed and, when the client system indicates that the virtual machine is running and has an IP address, or other identifying information sufficient for the RDP client, the client system being used creates a desktop and executes the RDP client.
- a virtual networking computing (VNC) client may be executed initially, so that the boot process can be seen by the user, and subsequently the RDP session may be switched to once the virtual machine is running.
- An RDP server may also be implemented in the Dom 0 domain, as an example, which integrates with a frame buffer for the virtual machine, such that only screen updates need to be transmitted between client systems instead of the whole screen representing the desktop.
- the management server 114 may be configured to remotely manage and control the power of the client systems. In this embodiment, if a user's home system is powered off or sleeping, and is remote from the user, it would need to be turned on to allow remote access to the virtual machine and desktop. Further, an unowned system may have to be turned on if it is to be assigned to or associated with the user as the user's home system, and is off or sleeping.
- the power management functionality may be implemented with Active Management Technology (AMT), using Intel vPRO technology, as an example. It will be appreciated that the power may be managed through any other hardware and/or software means.
- the management server 114 may also be configured to deal with errors.
- the client system being used by that user may be notified by the management server 114 and any number of scripts and/or predetermined error messages to allow the user to understand and possibly alleviate the error.
- a management server 114 is in communication with a first client system 140 and a second client system 142 .
- Each client system includes one or more virtual machines 148 , 150 , 144 , 146 that may be accessible on either of the client systems.
- first client system 140 is currently executing a Windows 7 virtual machine 148 for Joe and a Windows XP virtual machine 150 for Joe
- the second client system 142 is currently executing a Windows 7 virtual machine 144 for Fred and a Linux virtual machine 146 for Fred.
- the first client system 140 is a home system for Joe and is currently being used by Fred.
- the second client system 142 is the home system for user Fred.
- User Fred logs into first client system 140 by presenting his credentials. These credentials may be forwarded to the management server 114 which may determine that user Fred desires to access his desktops 144 , 146 through the first client system 140 .
- Fred's credentials may be examined by the client management application running on the first client system 140 which makes the determination that the first client system 104 is not Fred's home system. After such a determination, Fred may be presented with a distributed VDI startup screen 152 that may be similar to the NxTop virtual machine user access screen described in United U.S. patent application Ser. No. 12/338,452.
- the startup screen 152 facilitates communication with the management server 114 for the purpose of allowing Fred to access his home system 142 virtual machine desktops 144 , 146 .
- the distributed VDI startup screen 152 may be identical to the user access screen that would be presented to Fred if he were to log into his home system 142 .
- Fred selects an existing virtual machine desktop or starts up a new virtual machine desktop.
- Communication between user Fred on the first client system 140 and Fred's home system 142 is brokered through the management server 114 to facilitate smooth operation and consistency of state information among the client systems 140 , 142 and the management server 114 .
- user Fred has selected a virtual machine desktop 144
- conventional remote desktop communication between the remote client system 142 and a host client system 140 executing the virtual machine desktop 144 may be enabled.
- Machine and client state information, and other data that may facilitate proper synchronization among the clients 140 , 142 and the management server 114 may continue to be communicated among the client systems to maintain status of the virtual machine on the management server 114 , as an example.
- the distributed VDI system may be used in hospital environments, as an example, where doctors, nurses, and other staff move from room to room and use different computer hardware throughout a shift. In this instance, the user would be able to continue to access a running virtual desktop on any number of terminals in any number of rooms.
- the terminals e.g., computing devices
- the terminals may be on the same LAN and/or SAN, and may mount and unmount the virtual machine from centralized SAN data storage each time a new terminal is used, or use RDP to simply virtualize the running desktop that the user wishes to access.
Abstract
Description
Claims (17)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/651,886 US9270785B2 (en) | 2008-12-18 | 2012-10-15 | System and method for a distributed virtual desktop infrastructure |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/338,452 US20090164994A1 (en) | 2007-12-20 | 2008-12-18 | Virtual computing management systems and methods |
US201161546701P | 2011-10-13 | 2011-10-13 | |
US13/651,886 US9270785B2 (en) | 2008-12-18 | 2012-10-15 | System and method for a distributed virtual desktop infrastructure |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/338,452 Continuation-In-Part US20090164994A1 (en) | 2007-12-20 | 2008-12-18 | Virtual computing management systems and methods |
Publications (2)
Publication Number | Publication Date |
---|---|
US20130282792A1 US20130282792A1 (en) | 2013-10-24 |
US9270785B2 true US9270785B2 (en) | 2016-02-23 |
Family
ID=49381145
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/651,886 Active 2030-02-10 US9270785B2 (en) | 2008-12-18 | 2012-10-15 | System and method for a distributed virtual desktop infrastructure |
Country Status (1)
Country | Link |
---|---|
US (1) | US9270785B2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109343970A (en) * | 2018-08-17 | 2019-02-15 | 北京密境和风科技有限公司 | Operating method, device, electronic equipment and computer media based on application program |
Families Citing this family (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8949408B2 (en) * | 2009-12-18 | 2015-02-03 | Microsoft Corporation | Session monitoring of virtual desktops in a virtual machine farm |
FI20100057A0 (en) * | 2010-02-12 | 2010-02-12 | Notava Oy | A method and system for creating a virtual device for redirecting data traffic |
US9055139B1 (en) * | 2012-03-12 | 2015-06-09 | Cisco Technology, Inc. | Display protocol interception in the network for services and network-based multimedia support for VDI |
US9383891B2 (en) * | 2012-03-28 | 2016-07-05 | Skytap | Methods and systems for an intermediate graphical desktop sharing protocol |
US20140068021A1 (en) * | 2012-08-28 | 2014-03-06 | Alexey Arseniev | Configuring client services |
US10248453B2 (en) | 2012-10-23 | 2019-04-02 | Red Hat Israel, Ltd. | Client live migration for a virtual machine |
US9521188B1 (en) * | 2013-03-07 | 2016-12-13 | Amazon Technologies, Inc. | Scheduled execution of instances |
US10228242B2 (en) | 2013-07-12 | 2019-03-12 | Magic Leap, Inc. | Method and system for determining user input based on gesture |
US20150081760A1 (en) * | 2013-09-19 | 2015-03-19 | Thomson Licensing | Method and device for providing access to a task |
US9436751B1 (en) * | 2013-12-18 | 2016-09-06 | Google Inc. | System and method for live migration of guest |
US10977063B2 (en) | 2013-12-20 | 2021-04-13 | Vmware, Inc. | Elastic compute fabric using virtual machine templates |
US9323565B2 (en) | 2013-12-20 | 2016-04-26 | Vmware, Inc. | Provisioning customized virtual machines without rebooting |
KR101548228B1 (en) * | 2013-12-27 | 2015-08-28 | 주식회사 케이티 | Apparatus for synchronizing user interface based on user state and method thereof |
US11385774B2 (en) * | 2014-01-06 | 2022-07-12 | Red Hat, Inc. | Intuitive workspace management |
US10268492B2 (en) * | 2014-05-20 | 2019-04-23 | Amazon Technologies, Inc. | Low latency connections to workspaces in a cloud computing environment |
US9619268B2 (en) | 2014-08-23 | 2017-04-11 | Vmware, Inc. | Rapid suspend/resume for virtual machines via resource sharing |
US10152342B2 (en) * | 2015-06-30 | 2018-12-11 | Vmware, Inc. | Method and system for providing virtual desktop and virtual application interactivity |
EP3355190A1 (en) * | 2017-01-31 | 2018-08-01 | Sony Corporation | Device and system for maintaining a ditributed ledger |
US11080041B1 (en) * | 2017-03-30 | 2021-08-03 | Amazon Technologies, Inc. | Operating system management for virtual workspaces |
US10956197B2 (en) * | 2017-12-13 | 2021-03-23 | Citrix Systems, Inc. | Virtual machine with an emulator manager for migration of synchronized streams of state data |
Citations (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20020015699A (en) | 1999-06-16 | 2002-02-28 | 추후제출 | Client/server based architecture for a telecommunication network |
JP2002533830A (en) | 1998-12-29 | 2002-10-08 | サイトリックス システムズ,インコーポレイテッド | Apparatus and method for determining a neighbor program of a client node in a client-server network |
US20030065676A1 (en) * | 2001-09-05 | 2003-04-03 | Microsoft Corporation | Methods and system of managing concurrent access to multiple resources |
US20040010787A1 (en) * | 2002-07-11 | 2004-01-15 | Traut Eric P. | Method for forking or migrating a virtual machine |
JP2004145889A (en) | 2002-10-24 | 2004-05-20 | Hewlett-Packard Development Co Lp | A plurality of platform computer programs to be dynamically changed, and method and device for using the same |
US20060005189A1 (en) * | 2004-06-30 | 2006-01-05 | Microsoft Corporation | Systems and methods for voluntary migration of a virtual machine between hosts with common storage connectivity |
JP2006099406A (en) | 2004-09-29 | 2006-04-13 | Nec Corp | Switch device, system and backup, and restoration method and program |
US20070179955A1 (en) * | 2006-01-24 | 2007-08-02 | Citrix Systems, Inc. | Methods and systems for providing authorized remote access to a computing environment provided by a virtual machine |
US20100017800A1 (en) * | 2008-07-15 | 2010-01-21 | International Business Machines Corporation | Method, computer program product, and hardware product for supporting virtual machine guest migration overcommit |
US20100146611A1 (en) * | 2008-12-09 | 2010-06-10 | Microsoft Corporation | Credential Sharing Between Multiple Client Applications |
US20100325278A1 (en) | 2009-06-22 | 2010-12-23 | Red Hat Israel, Ltd. | Methods for automatically launching a virtual machine associated with a client during startup |
US20120209812A1 (en) * | 2011-02-16 | 2012-08-16 | Microsoft Corporation | Incremental virtual machine backup supporting migration |
US8555274B1 (en) * | 2006-03-31 | 2013-10-08 | Vmware, Inc. | Virtualized desktop allocation system using virtual infrastructure |
US20140108588A1 (en) * | 2012-10-15 | 2014-04-17 | Dell Products L.P. | System and Method for Migration of Digital Assets Leveraging Data Protection |
US20140181286A1 (en) * | 2000-09-12 | 2014-06-26 | Cisco Technology, Inc. | Stateful network address translation protocol implemented over a data network |
-
2012
- 2012-10-15 US US13/651,886 patent/US9270785B2/en active Active
Patent Citations (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2002533830A (en) | 1998-12-29 | 2002-10-08 | サイトリックス システムズ,インコーポレイテッド | Apparatus and method for determining a neighbor program of a client node in a client-server network |
KR20020015699A (en) | 1999-06-16 | 2002-02-28 | 추후제출 | Client/server based architecture for a telecommunication network |
US20140181286A1 (en) * | 2000-09-12 | 2014-06-26 | Cisco Technology, Inc. | Stateful network address translation protocol implemented over a data network |
US20030065676A1 (en) * | 2001-09-05 | 2003-04-03 | Microsoft Corporation | Methods and system of managing concurrent access to multiple resources |
US20040010787A1 (en) * | 2002-07-11 | 2004-01-15 | Traut Eric P. | Method for forking or migrating a virtual machine |
JP2004145889A (en) | 2002-10-24 | 2004-05-20 | Hewlett-Packard Development Co Lp | A plurality of platform computer programs to be dynamically changed, and method and device for using the same |
US20060005189A1 (en) * | 2004-06-30 | 2006-01-05 | Microsoft Corporation | Systems and methods for voluntary migration of a virtual machine between hosts with common storage connectivity |
JP2006099406A (en) | 2004-09-29 | 2006-04-13 | Nec Corp | Switch device, system and backup, and restoration method and program |
US20070179955A1 (en) * | 2006-01-24 | 2007-08-02 | Citrix Systems, Inc. | Methods and systems for providing authorized remote access to a computing environment provided by a virtual machine |
US8555274B1 (en) * | 2006-03-31 | 2013-10-08 | Vmware, Inc. | Virtualized desktop allocation system using virtual infrastructure |
US20100017800A1 (en) * | 2008-07-15 | 2010-01-21 | International Business Machines Corporation | Method, computer program product, and hardware product for supporting virtual machine guest migration overcommit |
US20100146611A1 (en) * | 2008-12-09 | 2010-06-10 | Microsoft Corporation | Credential Sharing Between Multiple Client Applications |
US20100325278A1 (en) | 2009-06-22 | 2010-12-23 | Red Hat Israel, Ltd. | Methods for automatically launching a virtual machine associated with a client during startup |
US20120209812A1 (en) * | 2011-02-16 | 2012-08-16 | Microsoft Corporation | Incremental virtual machine backup supporting migration |
US20140108588A1 (en) * | 2012-10-15 | 2014-04-17 | Dell Products L.P. | System and Method for Migration of Digital Assets Leveraging Data Protection |
Non-Patent Citations (3)
Title |
---|
Extended European Search Report for EP Application No. 12840609.7, mailed Feb. 26, 2015; 8 pages. |
PCT International Search Report for International Application No. PCT/US2012/060252, mailed Mar. 28, 2013, 4 pages. |
PCT Written Opinion of the International Searching Authority for International Application No. PCT/US2012/060252, mailed Mar. 28, 2013, 6 pages. |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109343970A (en) * | 2018-08-17 | 2019-02-15 | 北京密境和风科技有限公司 | Operating method, device, electronic equipment and computer media based on application program |
Also Published As
Publication number | Publication date |
---|---|
US20130282792A1 (en) | 2013-10-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9270785B2 (en) | System and method for a distributed virtual desktop infrastructure | |
EP2766820B1 (en) | System and method for a distributed virtual desktop infrastructure | |
US9747125B2 (en) | Associating virtual machines on a server computer with particular users on an exclusive basis | |
US10073709B2 (en) | Session monitoring of virtual desktops in a virtual machine farm | |
CN108370379B (en) | Device management method and system with tunnel | |
US9864754B2 (en) | Virtual desktop infrastructure private cloud | |
KR102328193B1 (en) | Apparatus and method for virtual desktop service | |
US8973098B2 (en) | System and method for virtualized resource configuration | |
US8924592B2 (en) | Synchronization of server-side cookies with client-side cookies | |
US8015331B2 (en) | Multi-console workstations concurrently supporting multiple users | |
CN106104486B (en) | Method and system for secure transfer of volumes into the cloud | |
US20100042636A1 (en) | Internet server system, method of creating virtual machine of the internet server and method of starting the same | |
US20150334184A1 (en) | Enabling execution of remotely-hosted applications using application metadata and client updates | |
KR20130139894A (en) | Unified reconnection to multiple remote servers | |
AU2006302251A1 (en) | Apparatus system and method for real-time migration of data related to authentication | |
US20170046013A1 (en) | Web-browser based desktop and application remoting solution | |
CN107026875A (en) | The fusion method and device of multiple virtual desktop frameworks | |
CN108632354A (en) | Physical machine receives pipe method, apparatus and cloud desktop management platform | |
CN112187718B (en) | Remote access cloud terminal and system of IDV cloud desktop | |
US20210152420A1 (en) | Apparatuses and methods for remote computing node initialization using a configuration template and resource pools | |
US20060085381A1 (en) | Remote deployment access system and method | |
EP1497720B1 (en) | System and method for managing operating system option values | |
US11818183B2 (en) | System and method for workspace sharing | |
JP2022190790A (en) | Remote access management apparatus, virtual server management apparatus, remote access management method, virtual server management method, program, and recording medium | |
KR20020041359A (en) | System and method for real time controlling a web page |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: CITRIX SYSTEMS, INC., FLORIDA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:GRAHAM, SIMON;REEL/FRAME:029541/0233 Effective date: 20121218 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
AS | Assignment |
Owner name: WILMINGTON TRUST, NATIONAL ASSOCIATION, DELAWARE Free format text: SECURITY INTEREST;ASSIGNOR:CITRIX SYSTEMS, INC.;REEL/FRAME:062079/0001 Effective date: 20220930 |
|
AS | Assignment |
Owner name: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT, NEW YORK Free format text: SECOND LIEN PATENT SECURITY AGREEMENT;ASSIGNORS:TIBCO SOFTWARE INC.;CITRIX SYSTEMS, INC.;REEL/FRAME:062113/0001 Effective date: 20220930 Owner name: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT, DELAWARE Free format text: PATENT SECURITY AGREEMENT;ASSIGNORS:TIBCO SOFTWARE INC.;CITRIX SYSTEMS, INC.;REEL/FRAME:062113/0470 Effective date: 20220930 Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH CAROLINA Free format text: PATENT SECURITY AGREEMENT;ASSIGNORS:TIBCO SOFTWARE INC.;CITRIX SYSTEMS, INC.;REEL/FRAME:062112/0262 Effective date: 20220930 |
|
AS | Assignment |
Owner name: CLOUD SOFTWARE GROUP, INC. (F/K/A TIBCO SOFTWARE INC.), FLORIDA Free format text: RELEASE AND REASSIGNMENT OF SECURITY INTEREST IN PATENT (REEL/FRAME 062113/0001);ASSIGNOR:GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT;REEL/FRAME:063339/0525 Effective date: 20230410 Owner name: CITRIX SYSTEMS, INC., FLORIDA Free format text: RELEASE AND REASSIGNMENT OF SECURITY INTEREST IN PATENT (REEL/FRAME 062113/0001);ASSIGNOR:GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT;REEL/FRAME:063339/0525 Effective date: 20230410 Owner name: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT, DELAWARE Free format text: PATENT SECURITY AGREEMENT;ASSIGNORS:CLOUD SOFTWARE GROUP, INC. (F/K/A TIBCO SOFTWARE INC.);CITRIX SYSTEMS, INC.;REEL/FRAME:063340/0164 Effective date: 20230410 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |