Device to device migration in a unified endpoint management system
Described herein are example methods and systems for enrolling a user device with an unified endpoint management system (“UEMS”) directly from another user device. The examples describe a first user device that is already enrolled with the UEMS and a second user device that is seeking to be enrolled. The two user devices can establish a direct connection with each other. The second user device can be authenticated by a user inputting the same migration password or pin at both user device. The first user device can generate and send a migration data file to the second user device. The migration data file can include settings, policies, software packages, and files managed by the UEMS. The second user device can copy settings, policies, and files, and install the applications from the migration data file. The second user device can notify an UEMS server of the device migration.
1. A method for device migration in a unified endpoint management system (“UEMS”), comprising:
establishing a direct connection at a first user device with a second user device;
receiving device migration user credentials at the second user device, the migration user credentials being based on user input provided at the first user device;
authenticating the migration by comparing user input at the second user device to the device migration user credentials;
identifying, to the first user device, an operating system (“OS”) running on the second user device, and determining whether or not the first user device and the second user device are running the same OS;
receiving a migration data file at the second user device, the migration data file originating from the first user device; and
initiating a device migration at the second user device using the migration data file, wherein
in an instance where the first and second user devices are running different operating systems:
the migration data file omits at least one application that is managed on the first device as part of the UEMS;
the device migration comprises installing files from the migration data file at the second user device; and
the installed files use the same file structure as the first user device.
2. The method of claim 1 , wherein in an instance where the first and second user devices are running the same operating system, the method further comprises:
verifying the integrity of the migration data file;
applying user profile settings and policies at the second user device;
retrieving, at the second user device, a software package from the migration data file;
installing, at the second user device, a software application using the software package;
copying, at the second user device, data files from the migration data file using the same file structure as the first user device; and
notifying a UEMS management server of the migration.
3. The method of claim 2 , wherein the software application, files, and policies are managed by the UEMS.
4. The method of claim 2 , wherein the integrity of the migration data file is verified using an encryption key, a hash, or a cryptographic hash.
5. The method of claim 1 , wherein in the instance where the first and second user devices are running different operating systems:
the device migration comprises installing policies from the migration data file at the second user device.
6. The method of claim 1 , wherein the first user device prompts the user to choose between at least:
migrating to the second user device and keeping the first user device enrolled the UEMS; and
migrating to the second user device and unenrolling the first user device from the UEMS, wherein selection of unenrolling the first user device causes the first user device to erase all data files and applications associated with the UEMS.
7. The method of claim 1 , wherein the device to device migration is managed by a portal application installed on each of the first and second user devices.
8. A non-transitory, computer-readable medium containing instructions that, when executed by a hardware-based processor, performs stages for device migration in a unified endpoint management system (“UEMS”), the stages comprising:
establishing a direct connection at a first user device with a second user device;
receiving device migration user credentials at the second user device, the migration user credentials being based on user input provided at the first user device;
authenticating the migration by comparing user input at the second user device to the device migration user credentials;
identifying, to the first user device, an operating system (“OS”) running on the second user device, and determining whether or not the first user device and the second user device are running the same OS;
receiving a migration data file at the second user device, the migration data file originating from the first user device; and
initiating a device migration at the second user device using the migration data file, wherein
in an instance where the first and second user devices are running different operating systems:
the migration data file omits at least one application that is managed on the first device as part of the UEMS;
the device migration comprises installing files from the migration data file at the second user device; and
the installed files use the same file structure as the first user device.
9. The non-transitory, computer-readable medium of claim 8 , wherein in an instance where the first and second user devices are running the same operating system, the stages further comprise:
verifying the integrity of the migration data file;
applying user profile settings and policies at the second user device;
retrieving, at the second user device, a software package from the migration data file;
installing, at the second user device, a software application using the software package;
copying, at the second user device, data files from the migration data file using the same file structure as the first user device; and
notifying a UEMS management server of the migration.
10. The non-transitory, computer-readable medium of claim 9 , wherein the software application, files, and policies are managed by the UEMS.
11. The non-transitory, computer-readable medium of claim 9 , wherein the integrity of the migration data file is verified using an encryption key, a hash, or a cryptographic hash.
12. The non-transitory, computer-readable medium of claim 8 , wherein in the instance where the first and second user devices are running different operating systems:
the device migration comprises installing policies from the migration data file at the second user device.
13. The non-transitory, computer-readable medium of claim 8 , wherein the first user device prompts the user to choose between at least:
migrating to the second user device and keeping the first user device the UEMS; and
migrating to the second user device and unenrolling the first user device from the UEMS, wherein selection of unenrolling the first user device causes the first user device to erase all data files and applications associated with the UEMS.
14. The non-transitory, computer-readable medium of claim 8 , wherein the device to device migration is managed by a portal application installed on each of the first and second user devices.
15. A system for device migration in a unified endpoint management system (“UEMS”), comprising:
a memory storage including a non-transitory, computer-readable medium comprising instructions; and
a computing device including a hardware-based processor that executes the instructions to carry out stages comprising:
establishing a direct connection at a first user device with a second user device;
receiving device migration user credentials at the second user device, the migration user credentials being based on user input provided at the first user device;
authenticating the migration by comparing user input at the second user device to the device migration user credentials;
identifying, to the first user device, an operating system (“OS”) running on the second user device, and determining whether or not the first user device and the second user device are running the same OS;
receiving a migration data file at the second user device, the migration data file originating from the first user device; and
initiating a device migration at the second user device using the migration data file, wherein
in an instance where the first and second user devices are running different operating systems:
the migration data file omits at least one application that is managed on the first device as part of the UEMS;
the device migration comprises installing files from the migration data file at the second user device; and
the installed files use the same file structure as the first user device.
16. The system of claim 15 , wherein in an instance where the first and second user devices are running the same operating system, the stages further comprise:
verifying the integrity of the migration data file;
applying user profile settings and policies at the second user device;
retrieving, at the second user device, a software package from the migration data file;
installing, at the second user device, a software application using the software package;
copying, at the second user device, data files from the migration data file using the same file structure as the first user device; and
notifying a UEMS management server of the migration.
17. The system of claim 16 , wherein the software application, files, and policies are managed by the UEMS.
18. The system of claim 16 , wherein the integrity of the migration data file is verified using an encryption key, a hash, or a cryptographic hash.
19. The system of claim 15 , wherein the first user device prompts the user to choose between at least:
migrating to the second user device and keeping the first user device enrolled the UEMS; and
migrating to the second user device and unenrolling the first user device from the UEMS, wherein selection of unenrolling the first user device causes the first user device to erase all data files and applications associated with the UEMS.
20. The system of claim 15 , wherein
the device to device migration is managed by a portal application installed on each of the first and second user devices, and
in the instance where the first and second user devices are running different operating systems, the device migration comprises installing policies from the migration data file at the second user device.