Windows Server

Will S · Guest

Other than migrating profiles by hand and fixing permissions, what are
other people doing for those W2K/WXP PCs that ADMT will not migrate?

You know, the ones that result in these error strings:
"2005-01-19 07:49:33 Installing agent on 1 servers
2005-01-19 07:49:33 The Active Directory Migration Tool Agent will be
installed on \\S01543
2005-01-19 07:49:44 ERR2:7625 Unable to connect to \\S01543\ADMIN$. The
machine might be down or its Server, Netlogon service might not be
started. rc=1722 The RPC server is unavailable.
2005-01-19 07:49:44 ERR2:7014 The Active Directory Migration Tool Agent
Service on \\S01543 did not start. See the application log on \\S01543
for details.
2005-01-19 07:49:45 All agents are installed. The dispatcher is
finished."

TIA!

Rebecca Chen [MSFT] · Guest

Hi Will,

What do you mean by " Other than migrating profiles by hand and fixing
permissions, what are other people doing for those W2K/WXP PCs that ADMT
will not migrate"?

According to my experience, ADMT can help you migrate the local user
profile from the old domain to a new one. If you encounter the error
message as you have listed when migrating the local user profile, I suggest
you check the following factors on client S01543:

1. RPC service is running on S01543
2. Netlogon service has been started
2. File and printer sharing turned on
3. c:\windows folder has been shared as admin$. Use "net share" command in
CMD to make sure IPC$ and admin$ are present.

You can find a similar issue addressed from the link below:

837366 The Active Directory Migration Tool displays a "RPC server is
http://support.microsoft.com/?id=837366

In addition, please refer to my steps to migrate the user profile, a very
important point is that many issue occurs due to the account who use the
ADMT does not have the permission in the NT clients.

NOTE: The user account is v-rebc, the client XP is called RebcXP. The NT
domain called Domain, destination is Win2k3Dom.

IMPORTANT:

1) Add NT Domain Admin to Win2k3Dom Built-in administrators and Win2k3Dom
Domain admins group.
2) Add Win2k3Dom Domain admins group to NT Domain admins group and built-in
administrators group.
3) Assume the account TEST is the NT domain account, add TEST to NT
built-in administrators group and NT Domain admins group. Therefore, TEST
account will have the full control permission to NT domain every clients
and the DC, it also has the permission on Win2k3Dom DC.
4) Use TEST to logon to the Win2k3Dom DC to peroform ADMT migration.

Use v-rebc to logon to NT domain, you will find the profile is located to
c:\documents and settings\v-rebc.domain

1. Logon to the win2k3dom DC and run ADMT to migrate user account v-rebc
2. Migrate computer account RebcXP. During the migration, tick User profile
on Translate objects screen. Please refer to the screen shot.
3.Choose Replace mode.
4.Follow the wizard to migrate the computer account.
5.Go to XP client, log on to the win2k3dom. You will find the user profile
is still using c:\documents and settings\v-rebc.Win2k3Dom.

HTH!

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