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. Exchange and AD Sync known limitations
|
Known limitation |
Issue ID |
|---|---|
|
Directory Sync Pro for Active Directory cannot sync the same source directory to more than one target directory using the same SQL database. The supported configuration for this is separate instances of Directory Sync Pro for Active Directory writing to separate SQL databases. |
4650 |
|
Renames and moves fail to work if you are using a manual /repushpull or /resync command. Before running the /repushpull /repush /repull and /resync commands, administrators should clear the target OU of any previously created Directory Sync Pro for Active Directory objects. |
4651 |
|
When synching objects into Exchange 2003 (only), the option to hide from the GAL will not function if the Recipient Update Service (RUS) is enabled. |
4657 |
|
Directory Sync Pro for Active Directory does not sync OU attributes such as Managed By or Description. |
4667 |
Table 4. Exchange and AD Sync - Device Synchronization known limitations
|
Known limitation |
Issue ID |
|---|---|
|
Support for mismatched device names using overrides and mapped values will be added in a future release. |
4666 |
Table 5. Exchange and AD Sync - Group Objects known limitations
|
Known limitation |
Issue ID |
|---|---|
|
Directory Sync Pro for Active Directory will create nested group objects as User Objects during syncing when Blank or Invalid LDAP filters have been applied in the Sync Profile for source OU under User Filter. The user should apply (ObjectClass=x) LDAP filter if they do not want to migrate any of the user objects. |
4662 |
Table 6. Exchange and AD Sync - Password Sync known limitations
|
Known limitation |
Issue ID |
|---|---|
|
Directory Sync Pro for Active Directory will encounter an error if the Administrator password contains special characters such as ", #, =. Take care using special characters in the Administrator password to avoid issues when performing the password copy portion of the synchronization. |
4661 |
|
Password sync does not support usernames that contain spaces. |
4675 |
|
Password sync does not support AES hashes. |
31353 |
Table 7. Exchange and AD Sync - User Objects known limitations
|
Known limitation |
Issue ID |
|---|---|
|
If the AD to AD profile is configured to create mail-enabled users, and the source objects are mail-disabled, the objects in the target directory will be incorrectly stamped with an email address policy (if configured). |
4658 |
|
There is an issue with the Target ThumbnailPhoto attribute being updated when it has been changed in the Source. |
4670 |
|
When synchronizing AD to AD, converting a contact to a mail enabled user fails with an error regarding duplicated ProxyAddress caused by Directory Sync Pro for Active Directory trying to add the Contact’s LegacyExchangeDN as the X500 address. Since the LegacyExchangeDN is already listed as a x500 address, it cannot be added. |
4672 |
|
To synchronize the UserAccountControl attribute, an Exchange Migration Directory Sync Pro for Active Directory profile should be utilized. This attribute will not be synchronized if using and Active Directory Sync profile. |
4678 |
Table 8. General Synchronization known limitations
|
Known limitation |
Issue ID |
|---|---|
|
Attempts to edit target objects synchronized from Exchange 2010 to Exchange 2003 will result in a dialog prompting you to click 'yes' to upgrade the object to the latest version. Objects should only be updated or deleted from the source directory. |
4652 |
|
If the BTDirsync or BinaryTree.Dirsync.Exchange.exe service is not running, a warning or error message does not appear in the UI when you attempt to sync. |
4660 |
|
Rooms, Resource, and Mail-in Databases are created without a proxyaddress or target address if the user mappings are removed. |
4669 |
|
Directory Sync Pro for Active Directory cannot create an AD Container Object in the Target AD and cannot create objects that are contained in a Container. |
4671 |
|
Directory Sync Pro for Active Directory does not populate the Manager attribute if the manager and subordinate are the same user. |
4673 |
|
When a user object has another user object set as a manager and the manager user object does not exist in Target, the user object gets created, but the manager attribute is not set and an "unable to find Manager object" error is logged. If sIDHistory is being migrated, since this occurs after the object is created in the target, the NeedsAttention field is Zero (0), so the object is not resync'd and the manager attribute is not updated. If sIDHistory is not being migrated, the NeedsAttention flag remains a 1, so when the manager object is synced, the manager attribute does update successfully. |
4674 |
|
Discover Custom Attributes may not launch or complete correctly when run multiple times. Restarting the Directory Sync Pro for Active Directory Service resolves this issue. |
4676 |
Table 9. Installation known limitations
|
Known limitation |
Issue ID |
|---|---|
|
The default installation path (C:\Program Files\Binary Tree) contains a space between "Binary" and "Tree". If you are also installing Notes Integration | CMT on the same servers, there will be two Binary Tree folders, one with a space and one without. This does not impact the functionality of either product. |
4659 |
|
If the Local Security Option FIPS is enabled on the system where the Directory Sync Pro for Active Directory console is installed, the Directory Sync Pro for Active Directory Profiles will not be saved due to Directory Sync profile encryption technology being blocked by FIPS security setting. It is recommended to disable this security setting on the Directory Sync Pro for Active Directory console machine. |
4665 |
|
A new passive node is created if Directory Sync Pro for Active Directory is uninstalled and re-installed and pointed to an existing SQL database. |
4668 |
|
If using McAfee Antivirus software, the BTPassSvc.exe file should be excluded so it is not viewed as a potential virus. |
4679 |
|
If using Symantec Antivirus software, the BTPassSvc.exe file should be added as an exception, so it is not viewed as a potential virus. |
4680 |
|
If certain values in the advanced menu, such as Auto Map or Discover custom attributes, are grayed out following an installation, you may need to wait a while and then restart the service for them to become active. |
14625 |
Table 10. Licensing known limitations
|
Known limitation |
Issue ID |
|---|---|
|
If an override TypeOfTransaction is set to an unrecognized value (i.e. "Skip) then a license will be burned. Valid TypeofTransaction values to use in an override are: Insert, Modify, Rename, Move and Delete. |
4648 |
Table 11. Mapping known limitations
|
Known limitation |
Issue ID |
|---|---|
|
Creating a mapping and synchronizing the group attribute msExchCoManagedByLink from AD to AD will cause a synchronization error in the Directory Sync Pro for Active Directory log and the group object will not be created or updated in the target AD. |
4663 |
Table 12. Matching known limitations
|
Known limitation |
Issue ID |
|---|---|
|
Enabled IPV6 on the Binary Tree Directory Sync Pro for Active Directory (DirSync) servers can cause referral matching to fail. IPV4 is the preferred version. |
4655 |
Table 13. Override known limitations
|
Known limitation |
Issue ID |
|---|---|
|
When you save an override, Directory Sync Pro for Active Directory re-generates the Person or Groups view. It does this by dynamically generating a single SQL statement using the snippet of SQL code that is part of all overrides. The max size for this SQL statement is 8000 total characters. If many new overrides are added this limit could be exceeded and an error when adding the overrides will occur. In addition to the default overrides, approximately 15-20 more Person and 20-25 Group overrides can be added before hitting the size limit. |
4664 |
Table 14. SQL known limitations
|
Known limitation |
Issue ID |
|---|---|
|
Deleting an object from both the target and source Active Directory (AD) will cause errors during the next directory synchronization, unless the object row is deleted from the SQL database. Binary Tree strongly recommends that updates and deletes are made from the source directory only. |
4649 |
|
Removing a synchronization profile by using the Remove Domain button in the Directory Sync Pro for Active Directory UI does not remove the information from the SQL database. |
4653 |
|
BT_Config.Description column exists in the SQL table, but is no longer used in the UI. |
4654 |
Table 15. UI known limitations
|
Known limitation |
Issue ID |
|---|---|
|
Resync (same as repushpull but runs for all profiles) and repushpull can only be run manually from a command line and are not available in the user interface. |
4656 |
Refer to the Binary Tree Directory Sync Pro for Active Directory and Migrator Pro for Active Directory 20.11 Requirements and Installation Guide (https://support.quest.com/technical-documents/binary-tree-directory-sync-pro-for-active-directory/20.11/requirements-and-installation-guide) for system requirements.
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:
In the upper-right menu, under Settings, select Licenses.
View the existing license info or click Add License.
Refer to the Binary Tree Directory Sync Pro for Active Directory and Migrator Pro for Active Directory 20.11 Requirements and Installation Guide (https://support.quest.com/technical-documents/binary-tree-directory-sync-pro-for-active-directory/20.11/requirements-and-installation-guide) for installation instructions.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center
