Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Migrator Pro for Active Directory 20.11.1 - Release Notes

Known limitations

The following is a list of known limitations or issues, including those attributed to third-party products, known to exist at the time of this release.

Table 3. Active Directory Reporter known limitations

Known limitation

Issue ID

In AD Reporter, there is an issue when running a custom report for a specific State or City value. Leave the search set for All and the report will be generated.

4592

Table 4. Cutover known limitations

Known limitation

Issue ID

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.

4613

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.

4602

The dot character (.) is not a valid character in usernames entered for Credentials.

4615

The Microsoft's security patch released on October 11, 2022 produces 2732 error - Domain Join Hardening Changes when rolling back a computer from cutover.

41441

Table 5. Installation known limitations

Known limitation

Issue ID

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.

4590

Due to compatibility issues, the version 20.11 agent is required for the version 20.11 installation.

29135

Table 6. Offline Domain Join known limitations

Known limitation

Issue ID

A Trust, at minimum Outgoing Trust established from Source to the Target, is required for the Offline Domain Join feature.

4597

Table 7. ReACL known limitations

Known limitation

Issue ID

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.

4591

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.

4593

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

4595

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.

4596

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.

4600

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.

4601

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

4604

Migrator Pro for Active Directory does not ReACL clustered SQL Servers.

4607

Table 8. Reports known limitations

Known limitation

Issue ID

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.

4598

At this time, reporting in Migrator Pro for Active Directory using SQL Server Reporting Services 2016 or higher is not supported. The reports included in this release of Migrator Pro for Active Directory are supported on SSRS 2012 and 2014.

4599

Table 9. SQL Re-Permission known limitations

Known limitation

Issue ID

For SQL Re-permissions, server logins that are valid AD accounts do not get updated as Target Domain accounts.

4589

Table 10. UI User Experience known limitations

Known limitation

Issue ID

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

4605

A global variable value's first character is skipped if the character is a zero (0).

4606

Table 11. Upgrade known limitations

Known limitation

Issue ID

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

4614

To preserve the Migrator Pro for Active Directory and Directory Sync Pro for Active Directory customizations, Offline Domain Join Files, and any uploaded Device Logs, the installation folder name will not be changed to the new ADPro and DirSyncPro folder name when upgrading from a previous version of Migrator Pro for Active Directory and Directory Sync Pro for Active Directory.

4603

Table 12. Workstation Agent – Cutover Options known limitations

Known limitation

Issue ID

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.

4594

Migrator Pro for Active Directory currently does not have the ability to set the DNS setting on a specific network card in dual network card setups. During cutover, the password and target AD cannot be authenticated if the first network Windows attempts to access cannot communicate to the new DNS server. To prevent this, the Network Card Binding Order must be correctly set. To set the Network Card Binding Order, go to Network and Internet\Network Connection, hold the Alt Key to access the Advanced Setting and change the order.

4612

System requirements

Refer to the Binary Tree Directory Sync Pro for Active Directory and Migrator Pro for Active Directory 20.11.1 Requirements and Installation Guide (https://support.quest.com/technical-documents/binary-tree-migrator-pro-for-active-directory/20.11.1/requirements-and-installation-guide) for system requirements.

Product licensing

A valid license is required for Binary Tree Directory Sync Pro for Active Directory and Binary Tree Migration Pro for Active Directory.

To obtain licenses, see information on this page https://www.quest.com/company/contact-us.aspx or contact the sales team at sales@quest.com

To specify a license file:

When opening the application for the first time, you are prompted to add a license before proceeding.

To view or add a license file:

  1. In the upper-right menu, under Settings, select Licenses.

  2. View the existing license info or click Add License.

Upgrade and installation instructions

Refer to the Binary Tree Directory Sync Pro for Active Directory and Migrator Pro for Active Directory 20.11.1 Requirements and Installation Guide (https://support.quest.com/technical-documents/binary-tree-migrator-pro-for-active-directory/20.11.1/requirements-and-installation-guide) for installation instructions.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation