Windows Server

James Fong · Guest

In the source domain (Domain A) global group A has twenty members, all users
from Domain A.
Use ADMT v2.0 to migrate group A and the twenty members from Domain A to
Domain Z in forest B. Fix group membership checkbox is ticked.
After migration, in the target domain only sixteen members are added to the
group A in domain Z in forest B.
Is this a known problem with ADMT? Is there a hotfix?

Rebecca Chen [MSFT] · Guest

Hi Jame,

I don't see there is any known issue will lost group memeber. I believe
ADMT log will let us know the details during the group migraiton.

Active Directory Migration Tool creates several log files in the Logs
folder under the Active Directory Migration Tools folder on the computer on
which the tool is installed. User and group migration progress is recorded
in Migration.log; dispatcher progress is recorded in Dispatcher.log.

Please uploade ADMT migration log here or send it to v-rebc@microsoft.com
for research.

Best regards,

Rebecca Chen

MCSE2000 MCDBA CCNA

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

James Fong · Guest

Rebecca,
Thanks for the advice.
We've found the problem is to do with the users primary group.
for example, if user A in Domain A is member of groups A, B and C. And the
user's primary group is set to A. Then after migration by ADMT, the user
will only be added to the groups B and C in the target domain. We then set
the user's primary group to Domain Users (the default) and perform the ADMT
migration again. This time user A is added to all the groups A, B and C.

regards,
James

"Rebecca Chen [MSFT]" wrote:

Rebecca Chen [MSFT] · Guest

Hi Peter,

Thanks for the great experience sharing!

Generally speaking, we recommned you not to migrate members when you
migrate group. The migraiton sequence goes like this:

Universal groups
Global groups
Domain Local groups
User accounts
Computer objects

Each group type has different rules for membership and serves a different
purpose. This affects the order that the groups are migrated from the
source to the target domains. Universal groups can contain members from any
domain in the forest and replicate group membership to the global catalog.
For this reason, they can be used for administrative groups. When you
restructure domains, it is recommended to migrate universal groups first.

In addition, I would like to suggest that you migrate the groups and users
separately (do not migrate the associated members when migrating groups).

During the group migration, please use the following configurations

[Group Options]

Copy group members * Not Checked
Fix membership of group * Checked

During the user migration, please use the following configurations:

[User Options]

Migrate associated user groups * Not Checked
Fix users' group memberships * Checked

If the groups have previously been migrated, choosing the above options
will update the group memberships during the user migration.

Any update, let us get in touch!

Best regards,

Rebecca Chen

MCSE2000 MCDBA CCNA

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

	Windows Server Forum Index -> Migration	All times are GMT
Page 1 of 1