Appendix B: Additional Configuration Options. Binary Tree 5.1
Publicitate
Publicitate
Binary Tree Documentation
Appendix B: Additional Configuration Options
Changing the attribute used for "Created by Dirsync" or "Updated by Dirsync"
By default, the adminDescription attribute (for Active Directory) or $BTAction (for Domino) is stamped on objects on the Target that are created or updated by Directory Sync Pro with "Created by Dirsync" or "Updated by Dirsync" to define which objects can be s afely deleted from the Target. An app setting is available in the config file to allow you to define a different attribute/field for this purpose.
To use an attribute other than adminDescription or $BTAction, define a new DirSyncAttribute setting in the
<appSettings> section of the config file. For example, the below setting will use adminDisplayName instead of adminDescription:
Warning: This must be configured before the initial sync.
<appSettings>
<add key="DirSyncAttribute" value="adminDisplayName"/>
</appSettings>
Setting msExchRecipientDisplayType and msExchRecipientTypeDetails Exchange attributes
A configuration option to allow you to set msExchRecipientDisplayType and msExchRecipientTypeDetails Exchange attributes based on the value of a configura ble attribute is available. This option is only applied to target objects not created by Directory Sync Pro.
The configuration option must defined in the <appSettings> section of the config file, as shown below. “Value=” should be contain the attribute to be used. (proxyAddresses shown below). If the value of the target attribute is null, msExchRecipientDisplayType and msExchRecipientTypeDetails will be populated. See the list below for the values that will be populated.
<appSettings>
<add key="RecipientType_MailEnabledAttribute" value="proxyAddresses"/>
</appSettings>
Mail Enabled Users in the source:
msExchRecipientDisplayType = 6
msExchRecipientTypeDetails = 128
Room Mailbox in the source:
msExchRecipientDisplayType = 7
msExchRecipientTypeDetails = 16
Resource Mailbox in the source:
msExchRecipientDisplayType = 8
msExchRecipientTypeDetails = 32
Directory Sync Pro 5.1 User Guide for Domino-Active Directory Synchronization
61
Binary Tree Documentation
Shared Mailbox in the source:
msExchRecipientDisplayType = 0
msExchRecipientTypeDetails = 4
Allow objects with remote mailboxes to be treated as mailbox-enabled objects
A setting that allows objects with connected O365 remote mailboxes to be treated as mailbox -enabled objects is available. To enable this feature, add the RemoteMailboxAsMailboxEnabled option to the <appSettings> section of the BinaryTree.DirSync.Exchange.exe.config file as displayed below.
<appSettings>
<add key="RemoteMailboxAsMailboxEnabled" value="True"/>
</appSettings>
If this setting is set to any value other than True or if omitted from the file, objects with remote mailboxes will be treated as non-mailbox-enabled. If set to True, objects with remote mailboxes will be treated as mailbox -enabled.
Disable the caching of group members
A configuration option can be used in the appSettings section of the config file to disable the caching of group members.
This setting should be added to the BinaryTree.DirSync.Exchange.exe.config file.
<appSettings>
<add key="OptimizeGroupSyncMemoryUsage" value="true"/>
</appSettings>
Valid values are true and false. If this setting is omitted, or set to an invalid value, the value defaults to false. If set to false, group members will be cached during push and pull. If set to true, group members will not be cached during push and pull.
Disable the initialization of the sync report
A configuration option can be used in the appSettings section of the config file to disable the initialization of the sync report. If disabled, a sync report will still be recorded, but it will not be initialized between syncs. The result will be that an object will show data from the last time it was processed by Directory Sync Pro, rather than just the most recent time it was processed. In other words, if an object is inserted during a sync, it will show in the sync report as Inserted. Assuming a second sync does not touch this object, then if the sync report is initialized, a second sync will show this object as No Change, but if the sync report is not initialized, the object will still show as
Inserted.
This setting should be added to the BinaryTree.DirSync.Exchange.exe.config file.
<appSettings>
<add key="DisableSyncReportInitialization" value="true"/>
</appSettings>
Valid values are true and false. If this setting is omitted, or set to an invalid value, the value defaults to false. If set to false, the sync report will be initialized. If set to true, the sync report will not be initialized.
Directory Sync Pro 5.1 User Guide for Domino-Active Directory Synchronization
62
Binary Tree Documentation
Set the maximum number of users and groups synced simultaneously
During pull processing, Directory Sync Pro will sync multiple Active Directory user and group objects simultaneously into the target AD. The maximum number of users and groups synced simultaneously can be changed using the ThreadCount setting in the config file. If this configuration option is not specified, the
ThreadCount will be set to the same number of logical processor cores of the server on which Directory Sync Pro is running.
The configuration option is not included by default. To add, modify the BinaryTree.DirSync.Exchange.exe.config file located at C:\Program Files\Binary Tree\DirSync and add a new key to the <appSettings> section as follows:
<appSettings>
<add key="ThreadCount" value="4"/>
</appSettings>
This option should never be set to a number greater than the number of processor cores on the server. However, you may need to specify a lower number if other applications also running on the server require a specific number of cores set aside for processing. Best practice is to leave the setting at the default value and lower it only if additional processing power is needed for other applications on the server.
Multiple passes will be needed to make sure all data is synchronized to the target when multi -threading is used. An example scenario is:
User B is the Manager of User A.
User A is synchronized first.
Then, User B is synchronized.
Another sync is needed for User B to be the Manager on User A.
Set the number of objects selected when the user selects all (Ctrl+A)
A configuration option can be added to control how many objects are selected when the u ser selects all (Ctrl+A):
<appSettings>
<add key="SelectAllLimit" value="1000"/>
</appSettings>
If this configuration option is omitted, the default value is 1000. Setting this option to a high number may cause performance issues when selecting and marking objects.
Setting select all limit when marking objects as Ready to Sync
Selecting objects to mark as Ready to Sync can be done from the Objects tab within the Sync Report, which contains all object types.
A configuration option can be used in the appSettings section of the config file to control how many objects are selected when the user selects all (Ctrl+A):
This setting should be added to the BinaryTree.DirSync.Exchange.exe.config file.
<appSettings>
<add key="SelectAllLimit" value="1000"/>
Directory Sync Pro 5.1 User Guide for Domino-Active Directory Synchronization
63
</appSettings>
Binary Tree Documentation
If this configuration option is omitted, the default value is 1000. Setting this to a high number may cause performance issues when selecting and marking objects.
This option does not apply to Windows Server Migration profiles.
Set the attribute used for the linking function
A configuration option can be added to change the attribute used for the linking functionality.
This setting should be added to the BinaryTree.DirSync.Exchange.exe.config file.
<appSettings>
<add key="LinkedIDAttribute" value="adminDisplayName"/>
</appSettings>
If this configuration option is omitted, adminDisplayName is used.
Directory Sync Pro 5.1 User Guide for Domino-Active Directory Synchronization
64
Descarcă
Publicitate