Re: RDP Security - Preventing clients from mapping drives
- From: "Jeff Pitsch [MVP]" <jeff@xxxxxxxxxxxxxxxxx>
- Date: Wed, 1 Mar 2006 18:10:44 -0500
There is no way of controlling it on the client.
Jeff Pitsch
Microsoft MVP - Terminal Services
http://www.sbcgatekeeper.com
Your Terminal Services Security Website
"The Gesus" <TheGesus@xxxxxxxxx> wrote in message
news:%23Ybg7VTPGHA.456@xxxxxxxxxxxxxxxxxxxxxxx
I have a vendor who wants our users to connect to a Windows 2003 Terminal
Server (outside of our corporate control) in order to run a medical
database application.
A requirement of this process is that our users (and other users in other
health care companies all over the country) have to connect their drives
to this foreign system. This raised a red flag immediately. The vendor
is willing to work out other ways of file transfer, but in the meantime
this is such a severe security hole we would like to globally disable this
"feature" of the RDP client.
Unless I'm missing something, there appears to be no way to restrict this
on the client side (Windows XP). There is an AD (Computer) Group Policy
for "Do not allow drive redirection" but this appears to be a server-side
policy. Since the server is outside our control, this policy is not going
to work.
Has anyone run across this and has anyone found a way to prevent users
from opening up this HUGE, GAPING security hole?
.
- Follow-Ups:
- Re: RDP Security - Preventing clients from mapping drives
- From: The Gesus
- Re: RDP Security - Preventing clients from mapping drives
- References:
- RDP Security - Preventing clients from mapping drives
- From: The Gesus
- RDP Security - Preventing clients from mapping drives
- Prev by Date: Re: Run App on Startup But Allow Admin Access
- Next by Date: Re: TS will not install on Windows 2003 Server
- Previous by thread: RDP Security - Preventing clients from mapping drives
- Next by thread: Re: RDP Security - Preventing clients from mapping drives
- Index(es):
Relevant Pages
|