Windows Forum

Ask something
Discussion Locked

Win2K Terminal Services - Usrlogon.cmd h

0 helpful
1 reply

by jeff.watts 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

am implementing two W2k Terminal Servers with Metaframe XP. I am using a RootDrive on the TS boxes and specifing user profiles & home directories on the Terminal Services Profile tab in Active Directory (test environment).

When I logon with a Domain test user account, Usrlogon.cmd hangs when the RootDrive and home drive letters are the same drive letter.

According to tech books (i.e. Admin911: W2k Terminal Services) this is a must to allow Apps to function properly in a multi-User environment.

I do not have the same issue in a WinNT 4 TSE environment.

Do anyone have any idea's.

Thanks

Jeff C. Watts

1 reply

by timthetoolman

Hi,

It looks like you cant have the RootDrive and home drive letters the same... Here is an extract from a microsoft article on TS describing setting up the RootDrive.

"The installer is required to select a drive letter. Any drive letter may be chosen, but it is important that it not be the drive letter specified in User Manager for either the Home Directory or Terminal Server Home Directory (in this example, X was used for UserA's home directory). Furthermore, the installer should not choose a drive letter that is used in a logon script. In this scenario, the person installing ApplicationA decides to use the suggested drive letter W:."

For the full article - which is definitely worth a read, look at...

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q195950

(remove spaces from the above URL)

Cheers,
Tim.

This discussion is closed to new replies.