ADMT 3.0 Renames CN and DisplayName of Existing IDs
Posted on 2006-07-10
I'm using ADMT v3.0 to do an inter-forest merge of existing accounts from an old domain (US) and corresponding, already-existing accounts in the newer domain (ENT) that we are consolodating all user accounts into.
I've got the process down pretty nicely through the use of an include file that specifies the original ID and newer ID. I have ADMT put the SID of the old ID in the SIDHistory of the newer ID. Users will begin logging in with newer ID when process completes. All works great, except for three things:
1. The CN name off the already existing target ID changes to match the logon name and I don't want it to. For example. If the user's CN in the target domain is "Doe, John", it changes to "Jdoe"
2. The display name does the same thing as above. If the user's display name is "John Doe", it changes to "JDoe"
3. In a random fashion, ADMT changes the UPN of the target ID by appending a zero to the end of it. This does not happen all the time and I've done the same exact test over and over again in an attempt to reproduce.
Very weird. Has anyone experienced the behavior above when merging accounts using ADMT 3.0?