Map the Directory Server destinationindicator attribute To construct a filter from the Attributes tab on the Console: The activedirectorydomainname and user_nt_domain_name attributes make constructing these filters easy. (because each Directory Server SUL has the same base DN, ou=people,dc=example,dc=com ). The SUL filters to determine in which Windows domain to synchronize the user When you create or modify a Directory Server user, the program uses To the Directory Server in ou=people,dc=example,dc=com. Users in the Windows NT NTEXAMPLE domain will be synchronized Will be synchronized to the Directory Server in ou=people,dc=example,dc=com. This example assumes that three Windows domains (two Active Directory domainsĪnd one Windows NT domain) will be synchronized with a single Directory Server

The following example illustrates how Identity Synchronization for Windows uses these attributes. Once Identity Synchronization for Windows maps the domainĪttributes, they will be set in the Directory Server entries during synchronizationĪnd can be used in Synchronization User List (SUL) filters. Mapped to a Directory Server user attribute. These attributes do not actually appear in the Windows user entries, theyĪre available for synchronization in the Identity Synchronization for Windows Console and can be

Synchronizing the entry to the Directory Server.įor Windows NT domains, Identity Synchronization for Windows sets the user_nt_domain_name attribute to the Windows NT domain name (such as NTEXAMPLE)īefore synchronizing the entry to the Directory Server.

The activedirectorydomainname attribute to the Activeĭirectory domain name (such as ) before Windows attributes that contain domain information.įor Active Directory domains, Identity Synchronization for Windows sets Server container (such as ou=people,dc=example,dc=com), Identity Synchronization for Windows uses “synthetic” To support synchronizing multiple Windows domains to the same Directory

Windows nt server 6.3