FAQ
Should I be using this solution to move PCs instead of wiping and re-enrolling a device?
It all depends on your situation. The official method as directed by Microsoft would be to completely wipe/reset a PC that is joined to the source environment before joining the destination. However, there is a significant amount of downtime associated with that effort. The migration solution provides an alternate workflow to move devices to their destination while mitigating/eliminating any user downtime or loss of productivity.
Is this supported by Microsoft?
No. This is a community driven, open-source project that came out of necessity providing an alternate route for organizations that need to migrate devices. This tool is provided "as-is" without any support from Microsoft.
What is the best way to deploy this?
Every organization is different, but a typical migration deployment looks like this:
- Build solution
- Determine who the test users will be
- Validate migration process on 1-5 devices
- Tweak as needed
- Move to production migration with a small wave (10-30 devices)
- Repeat the loop, exponentially growing wave sizes until all devices are migrated
What happens if the solution doesn't work?
Even with thorough testing, there will be situations where a device cannot complete the migration, be it due to hardware issues, identity problems, etc.
The best course of action if a migration feels is to wipe the device and simply re-enroll to the destination (which is the Microsoft route anyway, so we're no worse off than when we started.)
Can I test this locally without Intune?
Yes, but remember; in order to run the solution locally, you will need to run as NT AUTHORITY\System context.
Make sure you have Sysinternals installed to use PSEXEC.exe link in requirements.