Im stumped. I've googled and googled (which led me to this site several times) but haven't found a solution to this. The issue itself is common enough but none of the common solutions are for me.
Heres the situation:
- Computer Migration Wizard is run from ADMTv3. It's set to translate all objects (user profiles, user rights, etc.) in Replace mode.
- After computer restarts user logs into new domain but rather than use the translated profile a new profile is created with the format user.newdomain.
Why?
Details:
1) All other aspects of the migration look to have done fine (i.e. NTFS permissons on the user's exsisting profile have been chagned from 'olddomain\user' to 'newdomain\user').
2) There are no errors or warnings in the migration log or in the agent log.
3) Each domains' 'Domain Admins' group is a member of the others' Builtin\Administrators group
4) Account running ADMT is a Domain Admin in 'newdomain' (and as a result of 3, an admin in 'olddomain') and also a local admin on the PC being migrated.
5) Both the target and source domains have 'Anonymous Logon' and 'Everyone' in the 'pre-Windows 2000 Compatible Access' group.
6) Both the target and source domains are auditing success and failure of account managment.
7) This is an inter-forest migration
8 ) Im sure I've mised some so I'll fill this in as I get replies that remind me.
To my understanding SIDHistory dosn't come into play with this but, to cover all my bases: SIDHistory is enabled and working.
Im aware of the reg hack to change the SID in the ProfileList key but I don't plan a doing that to every system in the domain.
So, what I'm trying to find out is:
1) What exactly is ADMT failing to do that is causing this to happen? Is ADMT supposed to change the SID on the ProfileList reg key?
2) Why isn't it?
Any help would be greatly appreciated!
>> Stay informed about: local profile translation with ADMTv3