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. AD to Domino Sync - Group Objects
|
Known limitation |
Issue ID |
|
Syncing an AD group that does not have Exchange attributes to Domino as a Person document creates a group with no name in the Domino directory. |
14863 |
Table 4. Domino to AD Sync
|
Known limitation |
Issue ID |
|
If you attempt to manually sync from a command line, and either the source or target server are unavailable, no activity will appear in the command window. |
14847 |
|
When synchronizing objects from Domino to Active Directory using Directory Sync Pro, some special and accented characters in the source Domino data (such as ñaàeéêèioô ß œ æ) should be remediated prior to synchronization to AD as they are not allowed in AD. |
14873 |
Table 5. Domino to AD Sync - Group Objects
|
Known limitation |
Issue ID |
|
When synchronizing groups from Domino to Contact objects in Active Directory, two Domino groups with the same SMTP address will be synched to AD, instead of the second group being skipped. |
14845 |
|
A nested group will synchronize from Domino to Active Directory even if that group is explicitly listed in the Groups to Exclude list. |
14846 |
|
When synchronizing from Domino to Active Directory, a group with a "/" as the first character will synchronize to Active Directory as 'O=<groupname> (ex: /group13 will appear as O=group13 with mailNickname as O_Group13). |
14855 |
|
If a Domino group, which has already been synchronized, is updated with invalid characters in the SMTP Address, there is no warning regarding the invalid characters. |
14859 |
|
When Directory Sync Pro is syncing a group from Domino to AD, the CN part of the DN will be created by using the first non-empty field from SQL in the following order: DisplayName, Name, CommonName, PrimaryAlias. If any of these values exceed 64 characters, then the source data will need to be altered to be 64 characters or less, or overrides can be used to truncate the value to 64 characters. |
14872 |
|
The Directory Sync Pro Group synchronization process from Domino to AD only supports Domino Group members that are either SMTP addresses or Notes addresses. The Create External Members as Contacts in AD must be configured when synchronizing SMTP addresses as Group members. Group members in RFC822 format are not supported and this data should be remediated in the Source prior to Group synchronization. |
36787 |
|
|
|
Table 6. Domino to AD Sync - User Objects
|
Known limitation |
Issue ID |
|
Domino users with no value in the User Name field will not appear in the GAL without customizing the mapping table to build the Display Name. (14848) |
14848 |
|
The Domino to AD Directory Sync function to replace the internet domain for email routing to the Exchange SMTP domain, truncates the local part of the address if the source Internet Address Local Part is longer than 50 characters. The dbo.ReplaceDomain function can be copied and modified and used in an override to resolve this issue if it exists in an environment. |
25576 |
|
A user may be repeatedly added and removed to groups they are a member of if the user is added to a Domino group and synced, and then deleted and later re-added to Domino and synced again. |
47359 |
Table 7. Exchange and AD Sync
|
Known limitation |
Issue ID |
|
Directory Sync Pro 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 writing to separate SQL databases. |
14839 |
|
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 objects. |
14840 |
|
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. |
14851 |
|
Directory Sync Pro does not sync OU attributes such as Managed By or Description. |
15680 |
Table 8. Exchange and AD Sync - Device Synchronization
|
Known limitation |
Issue ID |
|
Support for mismatched device names using overrides and mapped values will be added in a future release. |
14876 |
Table 9. Exchange and AD Sync - Group Objects
|
Known limitation |
Issue ID |
|
Directory Sync Pro 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. |
14868 |
Table 10. Exchange and AD Sync - Password Sync
|
Known limitation |
Issue ID |
|
Directory Sync Pro 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. |
14867 |
|
Password sync does not support usernames that contain spaces. |
37933 |
Table 11. Exchange and AD Sync - User Objects
|
Known limitation |
Issue ID |
|
There is an issue with the Target ThumbnailPhoto attribute being updated when it has been changed in the Source. |
29210 |
|
To synchronize the UserAccountControl attribute, an Exchange Migration Directory Sync Pro profile should be utilized. This attribute will not be synchronized if using and Active Directory Sync profile. |
34387 |
|
Objects moved between source OUs results in duplicate Person Configuration entries. |
43956 |
Table 12. General Synchronization
|
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. |
14841 |
|
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. |
14864 |
|
No shutdown complete message is sent when the BTDirsync service is stopped on the Domino server. |
14864 |
|
Rooms, Resource, and Mail-in Databases are created without a proxyaddress or target address if the user mappings are removed. |
27877 |
|
Directory Sync Pro cannot create an AD Container Object in the Target AD and cannot create objects that are contained in a Container. |
29690 |
|
Directory Sync Pro does not populate the Manager attribute if the manager and subordinate are the same user. |
30643 |
|
Specifying a profile ID when running the command line /sync command runs the sync for all profiles, not just the specified profile. |
33750 |
Table 13. Installation
|
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. |
14861 |
|
During an install or an uninstall of Directory Sync Pro on a Domino server, if the option "Allow installer to edit notes.ini" is selected the Notes.ini will be stripped of comments in addition to the servertasks line being updated. A backup file notes.bak.ini is stored in the same directory on the Domino server. |
14870 |
|
If the Local Security Option FIPS is enabled on the system where the Directory Sync Pro console is installed, the Directory Sync Pro 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 console machine. |
14874 |
|
A new passive node is created if Directory Sync Pro is uninstalled and re-installed and pointed to an existing SQL database. |
22826 |
|
All-in-one configurations where the Directory Sync Pro console and the AD service is running on the Domino server are not supported. (39847) If using McAfee Antivirus software, the BTPassSvc.exe file should be excluded so it is not viewed as a potential virus. |
53553 |
|
If using Symantec Antivirus software, the BTPassSvc.exe file should be added as an exception, so it is not viewed as a potential virus. |
56003 |
Table 14. Licensing
|
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. |
14651 |
Table 15. Mapping
|
Known limitation |
Issue ID |
|
The Personal Ranking and Hierarchical level fields, on the Corporate Hierarchical Information tab of the person document (in a Domino Directory) will not automatically appear in the source field mapping table drop down. To map these fields, you must manually type them into the mapping table. |
14866 |
Table 16. Matching
|
Known limitation |
Issue ID |
|
Enabled IPV6 on the Binary Tree Directory Sync Pro (DirSync) servers can cause referral matching to fail. IPV4 is the preferred version. |
14844 |
Table 17. Override
|
Known limitation |
Issue ID |
|
When you save an override, Directory Sync Pro 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. |
14871 |
Table 17. SQL
|
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. |
14838 |
|
Removing a synchronization profile by using the Remove Domain button in the Directory Sync Pro UI does not remove the information from the SQL database. |
14842 |
|
BT_Config.Description column exists in the SQL table, but is no longer used in the UI. |
14843 |
Table 17. UI
|
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. |
14850 |
|
When creating an Active Directory to Domino sync profile, the Domino Target tab auto selects the previously selected Domino Directory when creating a new profile. |
14856 |
|
If the Auto-Map blacklist is changed in the DirSync_AutoMapBlacklist SQL table, Directory Sync Pro must be closed and relaunched to pick up the changes. |
18339 |
Refer to the Binary Tree Directory Sync Pro for Notes 20.13 Requirements and Installation Guide (https://support.quest.com/technical-documents/binary-tree-directory-sync-pro-for-notes/20.13/requirements-and-installation-guide) for system requirements.
A valid license is required for Binary Tree Directory Sync Pro for Notes which will be provided as a .dlv file to be imported into the product.
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. Copy the license file provided to the server and select the file to apply the license.
To view or add a license file:
In the upper-right menu of the product console, under Settings, select Licenses.
View the existing license information including the license number and object counts.
To apply a license, copy the license file to the server and click Add License. Select the license file provided to apply it to the product.
License consumption:
The product will consume a license from the purchased count for each object synchronized for Domino to Active Directory (AD) and from Active Directory to Domino if that is used.
The license count for user objects will include Domino Person, Mail-In Database, Room and Resource objects to sync from Domino to AD along with AD User and Contact objects if sync'ing from AD to Domino.
When an object is synchronized, either as a new object created or an existing object updated, a license count is consumed and is not returned to the license count. This includes objects in Domino or Active Directory if they are deleted after they are synchronized. Consideration should be given to any expected account turnover that may occur while the Directory Sync Pro product is in use as new accounts will require a license count.
The license for group objects only applies to Domino and Active Directory groups for the license count. The group membership, including external Domino contact SMTP membership, does not use a license count and the membership can be changed and deleted without consuming license counts.
Refer to the Binary Tree Directory Sync Pro for Notes 20.13 Requirements and Installation Guide (https://support.quest.com/technical-documents/binary-tree-directory-sync-pro-for-notes/20.13/requirements-and-installation-guide) for installation instructions.
© ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center
