I just rolled out a new domain controller. I want to join all the PCS to this new domein (the PCs were never on a domain just a regular workgroup). When I join a PC to the new domain it creates a new profile. How can I migrate (or whats an easy way) the local profile to this new domain profile?
Can I keep all settings, desktop layout, outlook 2003 settings etc while doing this?
\Documents and Settings\
(XP), or\Users\
(Vista/7) to something else (keep a note of what it was though, you'll need it in a minute)Another alternative way is to do steps 1->4, but use a
mklink
to link the Domain and the Local profile folders to eachother so that if you ever remove the machine from the domain the local profile is still up to date.If you're using roaming profiles, your milage may vary.
I hate to disagree with Farseeker on this one but the proper method (which will account for permissiones, etc) is to follow Farseeker's steps 1, 2, and 3 but in step 4 you're going to want to access the User Profiles through the system properties, select the old profile (listed as the old username) and click the Copy To button, then browse to the new domain profile folder and select it, then click the Change permissions button, and add the domain user (or alternately the Everyone group) to the permissions. When you log back on as the domain user the profile should be an exact duplicate of the old profile.
You might want to do what Microsoft says and try MoveUser.exe (XP) or the Win32_Userpofile WMI class (so script or batch solution in Windows 7). They have a KB article about it and everything.
Disclaimer: I have not tried this myself. I know the ghetto way from Farseeker works, but MSFT made this for a reason.
going off of Evan Anderson comment on my similar question and alharaka answer in this thread, I went looking for a way to use Win32_Userprofile to migrate local user to domain user.
I found a Visual Basic script at Vista’s MoveUser.exe replacement
When ran from a third account with both local admin and domain admin rights, and before logging in with the new domain user account, the script worked great.