Q:
Terminal Services profiles for active directory domain
We migrated our users and manually moved their terminal services profiles from the file server to a new server in the AD domain. The issue i ran into was that the stored profiles
ntuser.dat HKCU hive still has the sourcedomainuser1 and not the targetdomainuser1. I read that ADMT can't update NTUser.dat hive permissions on "terminal services profile path
Software/Hardware used:
terminal services, active directory
ntuser.dat HKCU hive still has the sourcedomainuser1 and not the targetdomainuser1. I read that ADMT can't update NTUser.dat hive permissions on "terminal services profile path
Software/Hardware used:
terminal services, active directory
ASKED:
Oct 15 2009 3:36 PM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
RELATED QUESTIONS
A:
RATE THIS ANSWER
0
Click to Vote:
0
Click to Vote:
- 0
0
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileGuid
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
Then you can copy the profiles.
Run this command from the new server:
robocopy "\\<oldTS>\c$\documents and settings" "c:\documents and settings" /COPYALL /S /XD
"\\<oldTS>\c$\documents and settings\Administrator"
"\\<oldTS>\c$\documents and settings\LocalService"
"\\<oldTS>\c$\documents and settings\NetworkService"
"\\<oldTS>\c$\documents and settings\Default User"
"\\<oldTS>\c$\documents and settings\All Users"
Where otdTS is the name of the old terminal server. Don't include the <> around the name.
I hope that helps. I successfully added a terminal server to a cluster and was able to copy profiles (roaming) from one server to a new server and users also didn't have to wait for the profile to be created.
Scott
