Drive mapping in Terminal services

Today a client asked how they could drag and drop files when connecting to their Windows 2003 server. I responded with the normal, “you can do this by connecting to your FTP server on a Windows server…”. They were not thrilled. When dealing with a wide variety of clients you run the gambit of skill levels and effort.

Generally, they want things to be as easy as possible with a little complication as possible. Unless of course this violates security policies. In most cases your job is to balance what benefits your client versus the potential pitfalls. In the case of the new Windows remote desktop this was easily accomdatated.

Problem: securely transfer files will as little hassle as possible
Fix: enable ‘drive mapping’ for terminal services
How to:

1. Open Terminal services configuration\connections (tscc)
2. open the ‘navigation’ folder’
3. Open the properties for ‘RDP-Tcp’
4. click on the ‘client settings’ tab
5. clear the ‘drive mapping’ option box
6. click okay
7. close tscc

The next time your client logs in they will see their local drives mapped as part of the server’s additional drives. Now they can cut-n-paste with ease and still keep the secure connection.

NOTE: there are added notes here:  Drive mapping in Terminal services part 2

About the Author

Leave a Reply

%d bloggers like this: