Article ID: 230165
Article Last Modified on 11/1/2006
APPLIES TO
- Microsoft Windows NT Server 4.0, Terminal Server Edition
This article was previously published under Q230165
SYMPTOMS
Home directories are not mapped correctly for users with existing profiles. Their home directory and root drive point to the default path of %SystemRoot%\Profiles\%Username%. The drive letter set in the home directory connect box does appear in My Computer in the Terminal Server session. No error messages are displayed to the user.
CAUSE
This problem occurs because the user's profile already contains a drive mapped to the same drive letter that was specified for the user's home directory. After the system finds that the drive letter is already in use, it does not map the drive and does not correctly set the homepath or homedrive variables. The user retains the default settings pointing to:
Home Directory Path: %SystemRoot%\Profiles\%Username%
HOMEDRIVE=C:
HOMEPATH=\Wtsrv\Profiles\%Username%
This also affects the root drive because it is set through the Usrlogon.cmd script when the user logs on. Listed below is the portion of Usrlogon.cmd that connects rootdrive:
Rem
Rem Map the User's Home Directory to a Drive Letter
Rem
Net Use %RootDrive% /D >NUL: 2>&1
Subst %RootDrive% /d >NUL: 2>&1
Subst %RootDrive% %HomeDrive%%HomePath%
RESOLUTION
To resolve this issue, delete the mapped drive from the user's profile or set the home directory to another drive letter.
MORE INFORMATION
For more detailed information on how Rootdrive is used in Terminal Server, please see the following Microsoft Knowledge Base article:
195950 How and Why ROOTDRIVE Is Used on Windows Terminal Server
Keywords: kbprb KB230165
