Techniques for desktop migration
View Patent ↗Techniques for desktop migration are presented. A user authenticates to an original device and a token is generated for remoting to that device's desktop. A target device acquires the token while in proximity to the original device and uses the token to authenticate to a third-party service that provides a second token back to the target device. The second token permits the target device to authenticate and to directly connect via remoting software to the original device's desktop.
1. A method implemented in a non-transitory machine-readable storage medium and processed by a device configured to perform the method, comprising:
acquiring, by the device, a token for desktop access to an original device, the token acquired directly from the original device;
sending, by the device, the token to a server desktop migration manager;
receiving, by the device, a second token from the sever session manager; and
establishing, on the device, remote access to a desktop and desktop resources of the original device using the second token and processing actions taken with the desktop resources remotely on the original device during the remote access, the original device maintaining the desktop resources as changed during the remote access from the actions taken, and the original device executes the desktop resources during remote access by the device.
2. The method of claim 1 , wherein acquiring further includes obtaining the token from a display screen of the original device as a Quick Response (QR) code.
3. The method of claim 1 , wherein acquiring further includes obtaining the token from one of: a Near Field Communication (NFC) driver, a Bluetooth driver, an Infrared driver, and a Radio Frequency (RF) driver of the original device as wireless encoded information.
4. The method of claim 1 , wherein sending further includes decoding the token to identify a network address for the server desktop migration manager, an original device identifier for the original device, and a principal identifier for a principal associated with the original device and the device.
5. The method of claim 4 , wherein decoding further includes selectively reassembling the token in a different format and digitally signing the new format before sending the signed reassembled token to the server desktop migration manager.
6. The method of claim 1 , wherein sending further includes registering the device with the server desktop migration manager when the device is unregistered.
7. The method of claim 6 , wherein registering further includes prompting a principal associated with the device to authenticate with the server desktop migration manager to register the device when the device is unregistered.
8. The method of claim 1 , wherein establishing further includes using the second token to initiate a remoting service on the device, the remoting service providing the remote access to the original device from the device.
9. The method of claim 8 , wherein using further includes authenticating a principal associated with the device and the device to the original device via the second token.
10. The method of claim 1 further comprising, processing the method on the device that is a portable device including one of: a tablet, a phone, and a laptop.
11. The method of claim 10 , wherein the method is initially acquired on the device as an app that is dynamically downloaded from a remote network site and installed on the portable device.
12. The method of claim 1 further comprising, migrating, from the device, the second token to a target device, the target device delegated by a principal of the device to remote the desktop and the desktop resources from the original device on the target device.
13. A method implemented in a non-transitory machine-readable storage medium and processed by a server configured to perform the method, comprising:
sending, by the server, data to an original device, the data generated for the original device and the data for authenticating a target device for remoting a desktop of the original device;
acquiring, by the server, a token from the target device, the token at least partially derived from the data by the original device;
validating, by the server, the token and the target device; and
communicating, by the server, a second token to the target device, the second token used by the target device to authenticate to the original device and to remote the desktop of the original device on the target device, and wherein resources of the original devices are executed on the original device during remoting of the desktop and when any resource is changed during the remoting by the target device that resources as changed remains on the original device.
14. The method of claim 13 , wherein sending further includes sending the data as the token.
15. The method of claim 13 , wherein sending further includes providing periodic updates to the data for the original device.
16. The method of claim 13 , wherein sending further includes providing the data over a secure communication channel.
17. The method of claim 13 , wherein validating further includes verifying a signature for the original device that is provided with the token from the target device.
18. The method of claim 13 further comprising, authenticating, via the server, the second token on behalf of the original device when the original device receives the second token from the target device.
19. A system, comprising:
a target device having memory configured with a device desktop migration manager, the device desktop migration manager processing on the target device; and
a server having memory configured with a server desktop migration manager, the server desktop migration manager processing on the server;
wherein the device desktop migration manager is configured to capture a token within a configured proximity from an original device and communicate the token to the server desktop migration manager, the server desktop migration manager configured to validate the token and the target device when received from the device desktop migration manager and supply a second token back to the device desktop migration manager, the device desktop migration manager further configured to use the second token to authenticate to the original device and to remote a desktop and desktop resources available from the original device on the target device, and wherein the desktop resources execute on the original device during the remoting of the desktop and when changes to a particular resource occurs during the remoting of the desktop as made by the target device, those changes are retained on the original device.
20. The system of claim 19 , wherein the server desktop migration manager is further configured to supply the token or data used to construct the token to the original device.