Migrator Pro for Active Directory 20.11 - Release Notes

In some cases, the machine reboot process may cause the cutover process to run multiple times. The cutover completes successfully, however, the cutover status in the Migrator Pro for Active Directory console may not reflect this. If a rollback of the cutover is needed in this scenario, the cutover status must be "Completed" in the SQL database. Contact Support for assistance modifying this properly in order to perform a cutover rollback. This issue will be resolved in a future release.

Devices should not be ReACL'd once they have been cutover to the Target. This is not best practice and not supported. ReACL'ing post cutover can cause problems with the registry and user profiles.

There is no pre-requisite checking in the Migrator Pro for Active Directory agent installer to make sure that the supported .NET and PowerShell are installed. The installation of the agent will fail if these prerequisites are not met. The specific version of the prerequisites is documented in the product requirements.

When a Folder Redirect GPO is setup using a UNC share path instead of the user's local machine, ReACL will not update the permissions for that folder. The file share should be ReACL'd.

Users should backup any content in their Recycle Bin that they would like to keep and empty the Recycle Bin prior to their workstation being joined to a new domain. If this is not done, they will receive a message that their Recycle Bin is corrupt and a new Recycle Bin will be automatically created by Windows for their new target domain account. The Migration Options Settings in the Migrator Pro for Active Directory console does have the ability to Empty the Recycle Bin as part of the device cutover, but note, this will not back up the content.

Full Access Permission is required to ReACL NAS shares on Windows XP machines.

SID history must be migrated to the target domain in order for Windows Modern (Metro) applications in Windows 8.1 to work properly post ReACL and cutover to the target domain. This is not a problem in Windows 8.

On Windows 8, Windows 8.1, and Windows 10, after a ReACL, Network Printers may be removed and will need to be re-added manually.

On Windows 10, after a ReACL and cutover, the target user logged in may get an error "Invalid value for registry" when opening files that were associated with Windows applications (Modern UI or Metro apps). To resolve the issue, the user should run the application from the Windows Store from the Start menu. This will fix the file associations. Note, this problem will also resolve or fix itself in Windows after some time has passed.

Groups synced as members of another group are not added to ReACL mapping files.

If a Migration Group is added, it will not appear in the Migration Group filter on the Reports until you either close the Migrator Pro for Active Directory console or switch to a different report.

The Custom Action Download Target file path requires a trailing backslash (\) to work for custom target path.

If a registered device is upgraded during a migration, the Operating System Version value is not properly updated when performing a new Discovery. (4614)

When Devices are cutover to the Target Domain, the Source Device object will remain enabled in the Source Active Directory environment. This will change in a future release.