Appendix E: Directory Sync Pro Fields with Special
Processing
Binary Tree Documentation
AD Directory Sync Pro Fields with Special Processing
The below tables include fields with some kind of special processing in Directory Sync Pro. Fields can have the following characteristics:
Cannot be mapped
Can be mapped and have an override
May be explicitly ignored or changed by Directory Sync Pro if object meets certain conditions, even if mapping and override exists
Actual attribute may be set via config file
Additional notes are available below for field marked with a *.
Writing Users to AD
Attributes that may be set by Directory Sync Pro regardless of mapping:
Field
distinguishedName objectClass userPassword unicodePwd userAccountControl msExchRecipientDisplayType msExchRecipientTypeDetails msExchResourceDisplay msExchResourceSearchProperties msExchResourceMetaData
Cannot be mapped
•
• showInAddressBook* msExchMasterAccountSid msExchPoliciesExcluded msExchPoliciesIncluded userAccountControl pwdLastSet adminDescription
•
•
•
•
•
•
•
Can be mapped / have override
•
•
•
•
•
•
•
•
•
•
•
•
•
May be explicitly ignored
May be set with config file
•
•
•
Directory Sync Pro 5.1 User Guide for Domino-Active Directory Synchronization
78
Special processing if mapped:
Field Cannot be mapped
mail assistant* manager* managedBy* altRecipient* authoring unauthOrig dLMemSubmitPerms dLMemRejectPerms sAMAccountName legacyExchangeDN* mailNickname
Binary Tree Documentation
Can be mapped / have override
•
•
•
•
•
•
•
•
•
•
•
•
May be explicitly ignored
•
•
•
•
May be set with config file
Never set:
Field Cannot be mapped
objectGUID objectSid whenCreated whenChanged uSNChanged name cn
Writing Groups to AD
•
•
•
•
•
•
•
Can be mapped / have override
Attributes that may be set by Directory Sync Pro regardless of mapping:
May be explicitly ignored
Field
objectClass msExchRecipientDisplayType msExchVersion
Cannot be mapped
•
Can be mapped / have override
•
•
May be explicitly ignored
•
May be set with config file
May be set with config file
Directory Sync Pro 5.1 User Guide for Domino-Active Directory Synchronization
79
Field
showInAddressBook* msExchPoliciesExcluded msExchPoliciesIncluded adminDescription
Binary Tree Documentation
Cannot be mapped
•
•
•
Can be mapped / have override
May be explicitly ignored
•
•
•
May be set with config file
•
Special processing if mapped:
Field Cannot be mapped
mail assistant* manager* managedBy* altRecipient* authOring unauthOrig dLMemSubmitPerms dLMemRejectPerms sAMAccountName legacyExchangeDN* groupType mailNickname
Never set:
Field
objectGUID objectSid whenCreated whenChanged uSNChanged name
Cannot be mapped
•
•
•
•
•
•
Can be mapped / have override
Can be mapped / have override
•
•
•
•
•
•
•
•
•
•
•
•
•
May be explicitly ignored
May be explicitly ignored
•
•
•
•
May be set with config file
May be set with config file
Directory Sync Pro 5.1 User Guide for Domino-Active Directory Synchronization
80
Field
cn
Cannot be mapped
•
Can be mapped / have override
May be explicitly ignored
Binary Tree Documentation
May be set with config file
Special processing by Internal Field Name:
Field
DisplayName
PrimaryAlias
SAMAccountName
InternetAddress
Name
CommonName
Additional Notes
Cannot be mapped
Can be mapped / have override
•
•
•
•
•
•
May be explicitly ignored
May be set with config file
If this internal field name is mapped and value is empty, actual value comes from different internal field
•
•
•
•
•
•
1. TargetDN – this column contains the distinguishedName of the target object to be created or the existing distinguishedName of a matched target object. If the object is created, the following values are used: a. Non-group objects from Domino sources use the following columns (or override values if specified) in order until a non-NULL value is found: i. CommonName ii. DisplayName iii. PrimaryAlias iv. FullName v. PrimaryFullName b. Groups from Domino sources use the following columns (or override values if specified) in order until a non-NULL value is found: i. DisplayName ii. Name iii. CommonName iv. PrimaryAlias c. Non-group objects from AD sources use the DN column (or override value if specified) to compute a target object DN. This preserves the sub-OU hierarchy the object may be in from the source. d. Groups from AD sources, use the OU column (or override value if specified) to compute a target object DN. This preserves the sub-OU hierarchy the object may be in from the source.
Directory Sync Pro 5.1 User Guide for Domino-Active Directory Synchronization
81
Binary Tree Documentation
2. LegacyExchangeDN – the legacyExchangeDN of the target object is computed by constructing a value relative to the target Exchange organization.
3. ShowInAddressBook – unless hiding from GAL is enabled. No override column is available for this field. a. Rooms are added to the All Rooms address book, except for Exchange 2003 which doesn't have rooms or the All Rooms address book. b. Users are added to the All Users address book. c. Groups are added to the All Groups address book. d. All objects are added to the All Global Address Lists (GAL) address book.
4. Manager – all objects except Groups a. Uses the Manager column (or override value if specified) for the source object. b. Locates the referenced Manager in the target. c. If not found and a pending sync is available for the Manager, Directory Sync Pro will immediately sync it to the target. d. If the referenced Manager is a reference to itself, the Manager on the target object will be set on the next sync.
5. ManagedBy – group objects only a. Uses the ManagedBy column (or override value if specified) for the source object. b. Follows the same process as Manager above.
6. Assistant – all objects a. Uses the Assistant column (or override value if specified) for the source object. b. Follows the same process as Manager above.
7. AltRecipient – This is not automatically reconciled by Directory Sync Pro.
Domino Directory Sync Pro Fields with Special Processing
The below tables include Domino fields with some kind of special processing in Directory Sync Pro. Fields can have the following characteristic:
On the “reserved” list, meaning any mappings for them will be ignored and overrides cannot be used.
Directory Sync Pro 5.1 User Guide for Domino-Active Directory Synchronization
82
Explicitly set, even without mapping:
Field
$BTAction
$BTSourceDirectoryID
Form - when Directory Sync Pro created
Type - when Directory Sync Pro created
AvailableForDirSync - explicitly set to 0, when Directory Sync Pro created
MailSystem - explicitly set to 3
MailDomain - set to Foreign Domain given in profile, when Directory Sync Pro created
CalendarDomain - groups only, set to Foreign Domain given in profile, when Directory
Sync Pro created
GroupType - groups only, explicitly set to 1, set for Directory Sync Pro created
$Grouptype_Help - groups only, explicitly set to 1, set for Directory Sync Pro created
GroupTitle - groups only, explicitly set to 1, set for Directory Sync Pro created
Never set:
Binary Tree Documentation
On the Reserved List
•
•
•
•
•
•
•
•
Field On the Reserved List
ResourceType •
Can be mapped, but will use the given values if they exist (and ignores overrides in that case):
Field
DisplayName – groups only, set to TargetDisplayName if it has a value
PrimaryAlias – groups only, set to TargetPrimaryAlias if it has a value
SAMAccountName – groups only, set to TargetSAMAccountName if it has a value
InternetAddress – groups only, set to TargetInternetAddress if it has a value
Name – groups only, set to TargetName if it has a value
CommonName – groups only, set to TargetCommonName if it has a value
On the Reserved List
Directory Sync Pro 5.1 User Guide for Domino-Active Directory Synchronization
83
