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
Software/Hardware used:
terminal services, active directory
ASKED:
October 15, 2009 3:36 PM
UPDATED:
October 16, 2009 3:26 AM
Answer Wiki:
First you need to export the profile list from the old server and import it in the new by exporting the following registry keys and importing them to the new server. (Careful in the registry..blah...blah..blah.)
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionProfileGuid
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionProfileList
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 settingsAdministrator"
"\<oldTS>c$documents and settingsLocalService"
"\<oldTS>c$documents and settingsNetworkService"
"\<oldTS>c$documents and settingsDefault User"
"\<oldTS>c$documents and settingsAll 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
To see all answers submitted to the Answer Wiki: View Answer History.
RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
