ADMT 2.0 and User SID

[Fred Yarbrough]

We are having a problem with using the ADMT 2.0 utility and migrating user
accounts with the SID attached. The ADMT wizard steps us through selecting
the options and then simply hangs upon submitting the screen when you must
enter the account information for the source domain username, password, and
domain. This has worked perfectly in the past and we are using the correct
usernames and passwords. They are the same with only the domain names being
different. All other aspects work fine, just this SID history part hangs up
the ADMT. I am not seeing any errors or log file entries. We are running
the ADMT 2.0 utility on one of our Native AD domain DC's and the actual
account exists on our Windows NT 4.0 SP6a domain. If I run the User
Migration wizard without selecting the Migrate user SID option, it works
just fine.

Any Ideas?


Thanks,
Fred

 

[Yong Liang [MSFT]]

What's the different for the domain names you use before and now?
Do the migration invlove third domain?

Regards,
Yong

 

[Fred Yarbrough]

Yong,
Thanks for the reply. There has been no change except for upgrading our
AD servers to SP4. Previously this user migration has worked fine and now
it just hangs and sometimes will come back with a message that "There are no
more endpoints available from the endpoint mapper". I am preplexed to say
the least!



Thanks,
Fred

 

[Fred Yarbrough]

I found the following posting that describes the exact error although there
was no answer. It just started working for him. Evidently SP4 is not the
culprit as his problem was back in February '03. See below!


_______________________________________________________________
I can't explain it.
I came in this morning and decided to try the Migration Wizard again. You
know, just to get my bearings straight, so to speak. The fool thing decided
to work! Now the first time this morning, it got past the point where I got
the "endpoint mapper" error before, but the actual migration process stopped
prematurely because (according to the log file) a previous relationship
existed between the servers other than <Domain>\Administrator.
I don't know how that could be, but I restarted the Target server just to be
sure. Re-ran the ADMT User Migration Wizard, and it worked with nary a
complaint!

I'm not knocking the results, mind you, but it always leaves me wanting when
I can't explain away a problem like this.

Thanks again for the assist, Caleb.

Mike Finn
=================================

An extra config check is run when sidHistory is migrated, it looks like this
is failing. By not migrating sidHistory you skip the config check.

You could try the migration from the command line in case it is just a
problem in the wizard, but I doubt it.
admt user /sd:<src> /td:<trg> /mss:yes /to:users /testmigration:yes
/n:<userName>

also you can try sidhist.vbs from the win2000 reskit to try just a
sidHistory migration. It will call the same underlying api that admt does
to migrate the sidHistory, so I would expect the same result, but it would
confirm if it is an ADMT problem or a problem that the underlying api is
encountering.

thanks

--

Caleb Baker
Microsoft

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


____________________________

__________________________________________________________________