Drive connections through TS

  • Thread starter Thread starter Joseph P. Maenza
  • Start date Start date
J

Joseph P. Maenza

I am running an application off one of our network servers. All users
connect to a specific driver letters with the same script, For
example:

net use p: \\alpha\public
net use u: \\bravo\username$
net use w: \\alpha\work
net use t: \\delta\application

The application is accessed through the "T" drive connection, but for
security reasons I need to remove the drive connection from all users
scripts. I will allow all users to access the application through a
Terminal Server.

How do I then provide a drive connection to the applicaiton share ONLY
in the Terminal Server session. I am having a hard time setting this
up. I want the users when they connect via Remote Desktop, to connect
to the application Drive "T" and then automatically run the executable
for the applicaiton. When they exit the application, they then SHOULD
NOT have access to the share in their normal windows session.

Can someone please explain this process in detail or point me in the
right direction. I am not sure which group policy, if any, will help
me in this instance.

Thanks in advance.

JoeM
 
To get rid of the T: drive for all users, add the following line
to your domain-wide logon script:

net use T: /delete

To provide users with a T: drive only during their TS session, put
the line

net use t: \\delta\application

in a TS-specific login script, which you call from the standard TS
logon script C:\winnt\system32\usrlogon.cmd, or start directly
through a registry entry.
To start the application automatically when users open a TS
session, use TS Connection Configuration - Initial Program.
For more info, check:

195461 - How to Set Up a Logon Script Only for Terminal Server
Users
http://support.microsoft.com/?kbid=195461

186566 - Connection Configuration in Terminal Server
http://support.microsoft.com/?kbid=186566
 
Vera

Q195461 worked just great. Was able to remove old connection from
Network based script and only allowed connection to the app share via
the termlogon.cmd script.

THANKS

JoeM
 
Back
Top