Red Hat DIRECTORY SERVER 7.1, Administrator'S Manual, Page: 565 / 652

Using Windows Sync
Chapter 18 Windows Sync 565
Group entries that are within the scope of the sync agreement will be synchronized
in much the same way as user entries. In addition, the membership of groups is
synchronized with the constraint that only those members that are also within the
scope of the agreement are propagated. The result is that a group may contain
members that are both within and without the scope of the agreement, but only the
subset of members that are themselves within agreement scope are synchronized.
The remaining members are left unchanged on both sides.
Table 18-3 shows the attributes that are mapped between the Directory Server and
Windows servers, and Table 18-4 shows the attributes that are the same between
the Directory Server and Windows servers.
Manually Initiating Synchronization
While synchronization always occurs based on the schedule set in the
synchronization agreement, you can manually update the synchronized subtree.
A manual update synchronizes entries which have been changed since the last
synchronization process. To perform an update manually:
1.
Go to the Configuration tab in the Console.
Table 18-3 Group Entry Schema Mapping between Directory Server and Windows
Servers
Directory Server Active Directory Windows NT4 Server
cn name
ntGroupAttributes groupAttributes grpi_attributes
ntGroupId cn
name
samAccountName
grpi_name
ntGroupType groupType
uniqueMember member grpi_member
Table 18-4 Group Entry Schema that are directly mapped between Directory Server and
Windows Servers
seeAlso l
description ou