Remote Desktop File Format

轉自：http://engrmosaic.uncc.edu/mosaic-anywhere/remote-desktop-file-format

The new Terminal Services client (version 2600 and newer, 5.1.2600.x) introduces quite a few new capabilities.  A major client-side convenience is that connection settings can be saved in an RDP file which can then be easily edited, copied, and distributed.

Unfortunately, the parameters are not nearly as well documented as the ActiveX control parameters yet; this will presumably change before the .NET server release.

Which Terminal Services/Remote Desktop Client?

The newest ones, versions 5.1.2600.x and up.  The client can be downloaded from the Remote Desktop Connection page - and despite the header, it is the client to use for connecting to either Terminal Services or XP Remote Desktop.

You can install it on any true 32-bit Windows OS except Windows XP and .NET - they already come with their own version.

Making an RDP File

You can create an RDP connection file using a text editor; there is nothing special about its structure to prevent this; in fact, the Terminal Services people appear to have been assiduous about making it simple and easy to use; the order in which parameters are placed doesn't even matter.

The simplest way to do it initially, though, is to run the mstsc client, configure basic settings you want, then choose "Save As..." on the General tab.  You can then open the resulting file in Notepad and work with it.

RDP File Structure

The file structure is relatively simple. The standard file consists of several lines; each has parameter name, type, and value, separated by a ":".  Any colons after the second one appear to be ignored (necessary so that file paths can be embedded).  MSTSC also appears to silently ignore anything it cannot parse, so you can insert freeform comments into the file.

For example, here are two lines which tell MSTSC to establish a 1024x768 desktop when it connects:

desktopheight:i:768
desktopwidth:i:1024

The first element in each line is the parameter name.  Immediately following it, after the first colon, is the parameter type; as far as I can tell, there are only 3 types of values -

• i (integer) This is used for numeric values such as the desktop resolutions above.  All  of the "on-off" values are integers; this may be to allow future expansion of value types, since some - such as audio redirection and keyboard hooking - actually have multiple values.
• s (string) Almost everything which is not a pure integer.  This includes paths and server names
• b (binary) apparently only used for hashed password storage

RDP File Parameters

Below is a table listing all of the parameters I have encountered so far.  I list the parameter name, type, an example value, and then include notes on usage where possible.

Example RDP File

This is an example RDP connection file. It starts maximized for its desktop size (800x600); color depth is 16-bit; it will attempt to automatically start connecting to 192.168.1.12 on launch; and so on...

screen mode id:i:1
desktopwidth:i:800
desktopheight:i:600
session bpp:i:16
auto connect:i:1
full address:s:192.168.1.12
compression:i:1
keyboardhook:i:2
audiomode:i:2
redirectdrives:i:0
redirectprinters:i:0
redirectcomports:i:0
redirectsmartcards:i:0
displayconnectionbar:i:1
username:s:Administrator
domain:s:AKA
alternate shell:s:
shell working directory:s:
disable wallpaper:i:1
disable full window drag:i:1
disable menu anims:i:1
disable themes:i:1
bitmapcachepersistenable:i:1