ADPro: Issue with Cutover after a Rollback on Windows 10 with ODMAD and Migrator Pro for AD (4331855)

ADPro: Issue with Cutover after a Rollback on Windows 10 with ODMAD and Migrator Pro for AD

We have been having issues where with ODMAD or Migrator pro for AD (ADPRo) doesn’t properly roll back a Windows 10 workstation.

Scenario:

1.    Using ODMAD or Migrator Pro for AD migrate a Windows 10 PC to the target forest – Everything works as expected
2.    Roll back the Windows 10 workstation to the source forest – Everything appears to work properly
3.    Re-Migrate the same Windows 10 workstation to the target and the user always gets a blank (net new) Windows profile

Testing Completed:

1.    Verified there’s only one windows 10 profile for the user being migrated
2.    Deleted the users profile entirely and re-created and still having same issue with that user
3.    Can continue to migrate other users who didn’t log in to their target profile

This is an issue if the user is logged into the machine when the Rollback is initiated. This breaks the user profile.

This will be addressed in a future release.

Make sure the user(s) is logged out before starting the Rollback process.

Follow these steps to fix users already affected:

1. Uninstall workstation agent
2. Delete computer from SQL database
3. Run dirsync push to get computer object back into SQL database
4. Install workstation agent
5. Run reACL
6. Delete the broken user profile
7. Perform cutover
8. Log into windows 10 machine with target user

Confirm the new cutover is successful

Contact Product Support if you are still having issues.

28676