Return
-
Title
Group Memberships do not get migrated in the first pass when migrating by selecting Group Members -
Description
When migrating users in Quest Migration Manager (QMM) using the Group Membership method, group membership does not get updated at the first migration for the users (member of) or group's (members) attributes.
However, when you migrate another User that belongs to the previously migrated Group, then the Membership is updated so that the first batch of Users now have updated Group Membership, but the latest batch are still missing. -
Cause
QMM tries to create the User and Group on the preferred Domain Controller (DC)as a first action, and then modify the membership on the preferred GC (Global Catalog); however, the GC does not have the group object because of replication delays. -
Resolution
There is a link resolved that is dropped back into the queue for the Directory Synchronization Agent to process at a later time. The next time a migration is ran with the second batch of Users, replication has occured and the Group is now on the GC, and the unresolved link in the queue gets resolved, and the membership is updated correctly.
Set the values of the preferred Global Catalog and preferred Domain Controller to the same Server to eliminate replication delays. This allows the group to be created and membership to be updated correctly.
Refer to Solution 14630 - "Specifying preferred Domain Controllers for the Directory Synchronization Agent" for information on how to specify preferred DC and GC: -
Additional Information