admt 2.0 user migration / conflict detection

[Graham Turner]

can anyone confirm how ADMT 2.0 handles the conflict of accounts that have
already been migrated from a source domain to a target domain.

it is required that accounts that have been migrated on an individual basis
for testing are not overwritten during a subsequent "mass migration" process

it would seem that the ADMT either does it by checking its database or by
checking the presence of an object in the target domain ??

Thanks

GT

 

[Mark Oluper [MSFT]]

ADMT simply attempts to create the account in the target domain. If an
account already exists with the same user logon name (pre-Windows 2000) or
distinguished name (CN=name,OU=out,DC=... form) then the creation fails. In
other words ADMT relies on the directory server to detect theconflict and
return the error 'the object already exists'.

If the 'ignore' option is chosen then ADMT will not replace (merge) any
accounts which conflict.