Geeks With Blogs

News Clicky Web Analytics

web stats View David Caddick ('s profile on LinkedIn

Search this Site!

Locations of visitors to this page
View My Stats eXTReMe Tracker
This posting is provided "AS IS" with no warranties, and confers no rights. The opinions expressed within are my own and should not be attributed to any other Individual, Company or the one I work for. I just happen to be a classic techie who is passionate about getting things to work as they should do (and are sometimes advertised and marketed as being able to?) and when I can I drop notes here to help others falling in to the same traps that I have fallen in to. If this has helped then please pass it on - if you feel that I have commented in error or disagree then please feel free to discuss with me either publically or privately? Cheers, Dave
Thin Clients, VDI and Linux integration from the front lines.... Raw and sometimes unedited notes based on my experiences with VMware, Thin Clients, Linux etc.

So if you have a look at the MSTSC.EXE file that starts the RDP session and use the /? to call further info from the component you get something very much like this:


But if you dig a just a touch deeper you will find that the MS Terminal Services Client or RDP Client as it is more commonly known draws the config information for most of its settings from the simple DEFAULT.RDP file that will typically be saved in the Users profile. (see example below)

So if you want to make changes to the way it behaves then it is fairly straightforward to make the changes in the GUI of the Client and then use the “Save As…” command from within the GUI – but what happens if you’d like to replicate this as standard behavior across multiple devices?

Search in the target computer to find the default.rdp file? (they should be hiding in each users profile) This is the settings that are used when the RDP Client is used – so open default.rdp in notepad or similar and you will find it is pretty straightforward to read?

Here in this example I have set the local C,D and E drives to be visible:

But at the same time some of these settings are pretty easy to guess at and start modifying with a reasonable degree of being able to accurately guess what they will change? I’ve highlighted some of the pretty obvious ones?

screen mode id:i:2
session bpp:i:32     <<< Colour depth
full address:s:
keyboardhook:i:2    <<<Keyboard Shortcuts
audiomode:i:0   <<<Sound
redirectprinters:i:1   <<<attach local printers? 1 is on
autoreconnection enabled:i:1
authentication level:i:0
prompt for credentials:i:0
negotiate security layer:i:1
alternate shell:s:
shell working directory:s:
disable wallpaper:i:1    <<<part of controlling “the experience”
disable full window drag:i:1
allow desktop composition:i:0
allow font smoothing:i:0
disable menu anims:i:1
disable themes:i:0
disable cursor setting:i:0
gatewayhostname:s:      <<<Part of the TS Gateway from here down

If this is the case then make the changes to the user's default.rdp – then use the “save as”... then test Test, and then replicate to the same location on all devices?

Posted on Friday, June 20, 2008 11:24 PM IT Management , Microsoft Tips , Security | Back to top

Comments on this post: Modifying RDP5 & 6 to always connect local drives as well as USB devices…

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © Dave Caddick | Powered by: