When a user makes a Microsoft Terminal Services connection to a computer that is running Microsoft Windows 2000 Server, Windows 2000 Advanced Server, Windows 2000 Datacenter Server, or Microsoft Windows Server 2003, some programs that require per-user directories may not work as expected. Also, a per-user Windows folder may not be created in the home folder for the user.

Back to the top

This issue may occur if one of the following conditions is true:

•	A user does not have permission to create files and folders in the user's home folder.
•	A user does not have permission to read the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\IniFile Times

Back to the top

To resolve this issue, verify that the user has the correct permissions on the user's home folder, and then verify that the user has correct permissions to read the registry.

Back to the top

Verify that the user has correct permissions on the user's home folder

To determine the home folder for a user on a terminal server:

1.	If the user is a member of a domain, click Start, click Run, type dsa.msc in the Open box, and then click OK. If the user is not a member of a domain, click Start, click Run, type lusrmgr.msc in the Open box, and then click OK.
2.	In the left pane, click Users.
3.	In the right pane, right-click the user, and then click Properties.
4.	Note the folder location in the Local Path box on the Terminal Services Profile tab or on the Profile tab.

Note Users can type set at a command prompt to verify the location of their home folder.

Back to the top

Verify that the user has permission to read the registry

To verify that the user has permission to read the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\IniFile subkey:

1.	Click Start, click Run, type regedit in the Open box, and then click OK.
2.	Locate the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\IniFile
3.	Right-click the subkey, and then click Permissions.
4.	Verify that the user has read permissions on the key.

Back to the top