Terminal Services - RDP Client

[WalleyeGuy]

Using Win2K3 Server with Terminal Services.
Clients are of Windows 2000 on up (mostly WinXP).

I've been trying to search all over the web and especially in here hoping to find a solution, so I figured I'd simply ask after searching for so long.

Anyway....
Have a login script that of course maps network drives.
I have to keep that available, as the people that access the Terminal Server are both on the LAN and ohhh I guess could be Starbucks. I also have that login script mapping a drive to the "\\TSCLIENT\C" path. I need that C: drive redirection.

Now, we're using a 3rd Party Terminal Server Add-On similar to Citrix (2X ApplicationServer), so I cannot simply use straight Windows client side mstsc.exe settings to control which drives get redirected.

I'm sure there's a way; however, I just cannot come up with it. Is there a way to remove all of the redirected drive mappings with VBScript?? With this application (2X) it seems that it's an all or nothing type of drive redirection option. I'd like to remove all of the "\\TSCLIENT\%" drives, except C

 

[MITPRO]

In your script, try using \d \y swithces. This will remove all mapped drives except C: D:.

Do not pray to have an easier life, pray to be a stronger man!!!

B.S. Computer Information Systems
Masters of Information Technology in Network Security
CompTIA A+, Net+, Security+,
MCP, MCSA: 2003
70-298 (In-Progress)
70-299 (In-Progress)
MCTS: Exchange Server 2007 (In Progress)
MCTS: Server 2008 (In Progress)
MCTS: Windows Vista (In P

 

[MITPRO]

Let me add, when i use those swithces, i am using net use in command prompt. I would assume the same thing would apply in your script.

Do not pray to have an easier life, pray to be a stronger man!!!

B.S. Computer Information Systems
Masters of Information Technology in Network Security
CompTIA A+, Net+, Security+,
MCP, MCSA: 2003
70-298 (In-Progress)
70-299 (In-Progress)
MCTS: Exchange Server 2007 (In Progress)
MCTS: Server 2008 (In Progress)
MCTS: Windows Vista (In P

 

[WalleyeGuy]

No, I'm not using "Net Use" in my script.
Also, I actually tried net use * /d /y just to see if it would remove the redirected drives and it did not. It did remove all mapped drives, just not the ones that show as C on <computername>

 

[Roadki11]

On the server get into the Terminal Services Configuration snapin. Get into the rdp-tcp connection properties and look at the client settings tab. Deselect Connect client drives at login.



RoadKi11

"This apparent fear reaction is typical, rather than try to solve technical problems technically, policy solutions are often chosen." - Fred Cohen

 

[WalleyeGuy]

Roadki11, I was hoping not to do that, as I wanted to keep the C: drive redirection in place. However, I think I resolved my issue. I did stop the drive reconnection, then in the script I'm mapping drive letter to \\%CLIENTNAME%\C$ (I just hate mapping client drives to computer admin shares is all).

Thanks for the ideas guys

 

[Roadki11]

Maybe i misunderstood your original post?

I also have that login script mapping a drive to the "\\TSCLIENT\C" path.

Thought you already were mapping the c drive in your script and the rdp-tcp connection settings was creating a 2nd c drive map that you didnt want.



RoadKi11

"This apparent fear reaction is typical, rather than try to solve technical problems technically, policy solutions are often chosen." - Fred Cohen

 

[WalleyeGuy]

Nope, you got that right. However, if I remove the "connect client drives at logon" within either the client or server side, then I cannot map to \\TSCLIENT\C, as it's not available then.

I was hoping to find a way to keep the drive mapped to
\\TSCLIENT\C. I don't mind keeping the rdp drive C on blabla

I did more or less find a workaround. Did what you suggested and removed the ability to connect to client drives via the rdp-tcp connection then just map a drive to \\%CLIENTNAME%\C$

 

[WalleyeGuy]

DOH! I just realized, I cannot map the drives the way I am within my script anyway (\\%CLIENTNAME%\C$) as it then limits the client to only connect with computers that they have the same credentials with (meaning, at home in order to get to their local C: drive the script will try to connect to it via the Domain\UserID).

Going back to original, here's what I have..

"Network Drives" (from login script)
C on 'TSClient'(E
Groups on 'Servername'(G
Bla1
Bla2
Bla3

"Other"
C on TSCLIENT
D on TSCLIENT
G on TSCLIENT
Bla1 on TSCLIENT
Bla2 on TSCLEINT
Bla3 on TSCLIENT


What I trying to find a way to do, is to have my login script remove all of those "Other" drives. With the MS RDC Client, I can set what drives I want pushed over; however, with this third party thing we're using (2X ApplicationServer), there's no setting available to do that.

If I totally turn off drive redirection, there's no way for the client to get to their local C: drive (as then TSCLIENT\C is no longer available to script to either). If I script a drive mapping to \\%CLIENTNAME%\C$ then the end user is limited to only connecting via computers that their Domain\UserID has rights to the local C: drive (good for say 75% of connections; however, home computers (which oh of course I have to allow to connect grrrr) would error out.

Can anyone think of a way, I can change my script to remove those "Other" drives?

Thanks and sorry for the long post