Remote Desktop Plus

Once upon a time in a company far, far away, I needed to find a way to have users automatically logon to a Remote Desktop session with a specific set of credentials. I searched everywhere, and although I did find some tools, none of them were exactly what I was looking for. So I decided to make one myself. With the help of a lot of information at RemkoWeijnen.nl and examples at Obviex, I managed to write my own utility, saving me tons of work. So a big thank you to all the posters at Remko’s site!

Having done that however, I saw more possibilities. Our network consists of about 500 servers. A good system administrator is a lazy system administrator and although I don’t know about the good part, at least I’ve got the lazy part nailed down. I don’t want to enter my credentials every time I connect to a server. Or save them and then have to resave them over and over again, every time I change a password.

So as a way to spend what little free time I have left, I started writing Remote Desktop Plus. It’s Remote Desktop, but with some added features. Basically it allows you to launch a Remote Desktop session using a username and password entered from the command line (autologin) or imported from a saved profile. But that’s not all…

Features

• Login automatically from the command line.
• Supports launching and autologin of RemoteApps.
• Remote Desktop Plus (RDP+) is not a clone or copy of Remote Desktop. It’s just a shell for the normal Remote Desktop client (mstsc.exe) on your computer.
• Automatically trusts all local resources and the remote computer. No more annoying questions like: Do you trust the computer you are connecting to?
• Allows you to save credentials (securely) in profiles. Profiles only work for the user who saved them and only on the computer on which they were saved. Profiles can be useful when administering a large amount of computers from a single point of administration. Changed the password for Administrator? Just edit the profile and you’re done.
• Passwords entered from the command line can be encrypted for enhanced security. Useful when starting Remote Desktop from batch files or published applications (Citrix).
• Remote Desktop Plus features a special restricted kiosk mode in which only the computer, username, password, or any combination thereof can be changed. When used as a published application, this allows you to grant (internal or external) support departments remote access to a range of servers in a much safer way.
• You can also specify a range of computers the user is allowed to connect to. Any attempt to connect to computers not in the list will be denied.
• When logging on to a computer with local credentials, Remote Desktop Plus will try to determine the actual computername, so you don’t have to specify a computername in front of the username (like nldb01\sa). This is also useful when logging in to computers using an IP address instead of a computername (rdp /v:10.140.10.1 /u:administrator) or when logging on to Windows clusters.
• Supports connecting through a Remote Desktop Gateway server.
• Accepts both /console and /admin. No need to remember which version of Remote Desktop and/or which Service Pack for XP you’re running.
• Can set the working screen size to either the maximum available size (so it looks like a normal maximized application) or to a adjustable size – by setting either a margin or specifying a percentage of the screen – so you can still move it around a bit.
• When using multiple monitors, you can specify on which monitor the Remote Desktop session has to be started.
• Supports specifying a startup program (i.e. alternate shell) from the command line. You can use both local and remote environment variables in the command.
• Normally Remote Desktop times out after about 30 seconds when connecting to a non-responsive (or still booting) computer. But the age of modems is a thing of the past and time is precious, so Remote Desktop Plus times out after only 3 seconds.
• When you use a separate connection file, the normal Remote Desktop client will display the name of the connection file in front of the server name in the task bar (Support – nlprint01 – Remote Desktop). This means that as soon as you have more than a couple of programs running, the server name won’t be visible in the task bar anymore due to the text truncation. Not with Remote Desktop Plus! RDP+ will leave out the name of the connection file, so you’ll always be able to see the server name.
• You can even provide your own title text or icon if you want. This can be especially useful when using RDP+ as a gateway to start another Remote Desktop session.
• Has the ability to disable the close button in the title bar and remove the connection bar, thus forcing users to logoff gracefully instead of just disconnecting and leaving their remote sessions open.
• Allows you to specify in the command line which drives or drive types to redirect and/or which drive(s) to exclude from redirection.
• Ever had to login to multiple servers at once? Just enter those servers separated by commas and off you go.
• Remote Desktop Plus also has a load balancing and failover feature. Specify multiple servers and RDP+ will randomly pick one of the servers to connect to. If this server is unreachable, RDP+ will skip it and cycle trough the other servers in the list, until it finds a responsive one. You can use this for example for RemoteApps which are hosted on multiple servers.
• Has the ability to log all connections in a log file.
• Still missing some command line parameters? RDP+ supports every option supported by the Remote Desktop .rdp file, using a special command line parameter. This gives you an unprecedented control over every aspect of the session, straight from the command line and without the need for specific RDP+ command line switches.
• Some settings and options can be controlled through Group Policies. Group Policy templates for these settings are available for download on the site.

Screenshots

Note: The GUI only appears when no remote computer has been specified or when the command line option /gui is used.

Command line parameters

Remote Desktop Plus supports the following command line parameters:

Examples

rdp /v:nlmail01 /u:administrator /p:P@ssw0rd! /max

rdp /i:”Domain Admin” /fit /drives /noprinters /mon:2

rdp “G:\RDP\Support.rdp” /v:nlprint01 /u:helpdesk@donkz.local /drives:fixed,-c:,p: 

rdp /i:”Backup User” /kiosk /w:1024 /h:768 /allowed:10.10.*.*,nlfps*.donkz.local /domain:donkz

rdp /v:nlapp01 /i:”Control Center” /noclose /o:”redirectcomports:i:1, redirectsmartcards:i:1″”

rdp /v:nldmz01 /u:donkz\dmz /p:P@ssw0rd! /start:”mstsc \\nlfps01\config$\RDP\DMZ.rdp /f” /title:”Standby Support” /icon:”%WINDIR%\System32\shell32.dll,43″

rdp /v:nldc05,nldc06 /i /console /fit:35

rdp /v:nlts03 /remoteapp:”||FileZilla” /u:donkz\ftp /p:Tr@ns1t

rdp /v:nlapp02 /u:donkz\internetkiosk /pe:356zm6vRajBcS3mnnudOOh43bZKSWewQ /noprinters /nodrives /start:”C:\Program Files\Internet Explorer\iexplore.exe -k http://www.microsoft.com”

rdp /v:nlts01,nlts02,nlts03,nlts04 /lb /remoteapp:”||e-Help Client 3.0″ /u:donkz\helpdesk /pe:dixYA/m8pOHVVkQLAI9ifQ==

rdp /v:nlfps02 @options.txt /kiosk:011 /gui /log

rdp /u:%USERDOMAIN%\%USERNAME% /kiosk:101 /gui /fit:95%

Myself, I use the second example the most. Just create a shortcut in your Quick Launch toolbar and you only have to enter the desired server name.

Notes

Startup program

If you need to use double quotes in the /start startup program, you have to put a backslash (\) in front of each quote. You can also use environment variables in your command, both local and from the remote computer. To use remote environment variables, you must precede the percent signs with a backslash.

Combined example:
rdp /v:nlapp03 /u:donkzdomain\helpdesk /start:”\”C:\Program Files\Remote Control\rc.exe\” \”\\nlfps01\Config$\RC\\%COMPUTERNAME\%\%USERNAME%.cfg\”"

If Remote Desktop Plus is started by user JohnDoe, the last part of the command will be expanded to “\\nlfps01\Config$\RC\NLAPP03\JohnDoe.cfg”.

Title

You can set a user defined text as your title bar by using the option /title. You can use local environment variables in your title plus these two special variables:
%s: Will be expanded to the server name you’ve connected to.
%u: Will be expanded to the username used to login to the remote computer.

Example:
rdp /i:”Domain Admin” /fit /title:”%s (%u) – Remote Desktop”

When connecting to the server nlfps01, this would result in the title bar text nlfps01 (DONKZDOMAIN\Administrator) – Remote Desktop.

Icon

You can also use your own icon for the session by using the option /icon. This can be either a normal icon file (G:\Icons\Remote.ico) or an executable or .dll file (%ProgramFiles%\Internet Explorer\iexplore.exe). For files containing multiple icons, you can specify the desired icon using its index (%WINDIR%\System32\shell32.dll,43).

Please note that using /icon will also force an implied /wait, due to the way Windows retains (or does not retain) dynamically changed icons when the program which requested the changes is closed.

RemoteApps

You can start a RemoteApp with Remote Desktop Plus, either from the command line or specified in the .rdp file. You can enter the RemoteApp using either its name (“||FileZilla”) or the full path to the executable (C:\Windows\System32\Notepad.exe). When using the name, always enclose it between double quotes, otherwise your system may confuse the double pipe signs with the double pipes used in batch scripting.
All options concerning the screen (like /fit and /mon) are ignored when using RemoteApps. The same goes for /title and /icon. Due to the way the Remote Desktop client launches all RemoteApps in a general, embedded instance of mstsc.exe, the option /wait is also not supported.

Remote Desktop Gateway

Remote Desktop Plus can login to remote servers through a Remote Desktop Gateway. There are no command line switches, so all options must be configured from the normal Remote Desktop client and saved in a .rdp file, or entered through the /o option. When you select the option Use my RD Gateway credentials for the remote computer, RDP+ will also automatically login to the RD Gateway. If not, you will be prompted for credentials.

Kiosk mode

With the kiosk mode, you can set the GUI to a special restricted mode, in which only the fields for the target computer, username and password are shown. Using a 3-character ‘mask’, you can enable or disable any of the three fields. Each character in the mask stands for one of the three fields (computername, username, password). A 1 will enable the field, a 0 will disable it. For example, /kiosk:011 will disable the computername field and only allow the user to enter the username and password.
The kiosk mode will default to 100 when a mask has not been specified.

Allowed targets list

Using the /allowed command line option, you can restrict users to only a selected range of computers. If the user tries to connect to a computer which is not in the allowed target list, the connection will be denied. This can especially useful for publishing RDP+ to ‘untrusted’ users.

You can use wildcards in the list, and RDP+ will also try to translate hostnames to IP addresses and vice versa for its matching. So for example, when using /kiosk:100 /allowed:127.0.0.*, a target computer of localhost will be considered valid.

Drive redirection

You can specify the drives you want to redirect to the remote computer by using the /drives option. Drives can be specified either by name or by drive type (Fixed, Removable, Network, CD-ROM). To redirect drives that get plugged in later, you can use the drive type Dynamic.
You can also exclude certain drives by preceding them with the minus sign. For example, /drives:fixed,-c:,p: will redirect drive P: and all fixed drives except C:.

If you don’t specify any drive or type, /drives will default to all drives, including the ones plugged in later.

Extended .rdp options

By using the /o switch, you can specify every option supported by the .rdp file. Options should be given in the exact same syntax as used in .rdp files. You can specify multiple options by separating them by commas.

Example:
rdp /start:terminal.exe /o:”shell working directory:s:H:\My Documents, redirectcomports:i:1″

The native RDP+ command line switches always take precedence over the /o options. So if you use rdp /printers /o:”redirectprinters:i:0″, then /printers will win.

For an overview of (most of) the possible settings, you may find this page useful.

Log file

You can log all started sessions to a semicolon-delimited log file using the /log option. If you don’t specify the name of the log file, it will default to the file rdp.log in the directory containing rdp.exe.
If you do specify a filename, the name can be further customized through both local environment variables (like %COMPUTERNAME%), and some special variables:
%s: Will be expanded to the server name you’re connecting to.
%u: Will be expanded to the username used to login to the remote computer.
%c: Will be expanded to the name of the local client computer. When starting RDP+ locally, this will be the same as %COMPUTERNAME%. When starting RDP+ from within a Terminal Server or Citrix session, %c will contain the computername of the originating client computer (i.e. %CLIENTNAME%).
%y: The 4-digit representation of the current year.
%m: The 2-digit representation of the current month.
%d: The 2-digit representation of the current day.

Example:
rdp /log:%y%m%d-%s.log

When connecting to the server nlfps01 on the 31st of December, 2011, this would result in the log file 20111231-nlfps01.log being used.

The log file contains all kinds information about the computer and user which started the session, and information about the target computer and how the session was started. When RDP+ is launched from within a Terminal Server or Citrix session, it will also log the computername and IP address of the originating client. This can also be useful when using thinclients.

A typical log file could look like this:

Date-Time;Local-Computer;Local-IP-Address;Windows-Version;Local-User;TS-Client;TS-IP-Address;Remote-Computer;Remote-Port;Remote-User;RDP-Version;RDC-Version;Password-Mode;Session-Type;Application
2011-12-31 11:11:40;LTP0235;10.0.1.163;Microsoft Windows 7 Professional;DONKZ\PeteL;-;-;nlfps01;3389;DONKZ\Administrator;3.11.1;7.1;Profile;Normal;-
2011-12-31 11:14:46;LTP0235;10.0.1.163;Microsoft Windows 7 Professional;DONKZ\PeteL;-;-;nlsql01;3389;sql-sa;3.11.1;7.1;Password;Normal;-
2011-12-31 11:17:35;DTP0019;10.0.1.157;Microsoft Windows XP Professional;DONKZ\JohnB;-;-;nlts01;3389;DONKZ\JohnB;3.11.1;6.1;Profile;Normal;-
2011-12-31 11:19:51;NLTS01;10.10.1.110;Microsoft Windows Server 2003 Enterprise;DONKZ\JohnB;DTP0019;10.0.1.157;nlapp01.donkz.local;3389;DONKZ\Helpdesk;3.11.1;5.2;Encrypted Password;Alternate Shell;mmc dsa.msc
2011-12-31 11:21:42;LTP0382;10.0.1.146;Microsoft Windows 7 Professional;LTP0382\Administrator;-;-;nldc01;3389;DONKZ\Install;3.11.1;7.1;Password;Normal;-
2011-12-31 11:23:16;NLTS02;10.10.1.111;Microsoft Windows Server 2008 R2 Standard;DONKZ\CharlesV;DTP0124;10.0.1.150;10.10.2.191;3390;Support;3.11.1;7.1;Encrypted Password;Normal;-
2011-12-31 11:26:07;NLTS02;10.10.1.111;Microsoft Windows Server 2008 R2 Standard;DONKZ\Security02;WS_013184;192.168.200.15;nlapp04;3389;DONKZ\Security;3.11.1;7.1;Kiosk;Normal;-
2011-12-31 11:28:13;DTP0024;10.10.1.129;Microsoft Windows 7 Professional;DONKZ\TessaM;-;-;nlts01;3389;DONKZ\TimeManager;3.11.1;7.1;Encrypted Password;RemoteApp;||TimeManager
2011-12-31 11:34:54;LTP0235;10.0.1.163;Microsoft Windows 7 Professional;DONKZ\PeteL;-;-;nlpos82;3389;-;3.11.1;7.1;Password;Administrative/Console;-

Or, for better readability:

Exit Codes

When starting Remote Desktop Plus from a script, you can use the option /batch to prevent RDP+ from displaying error messages. Instead you can catch potential errors through the exit codes (errorlevels) RDP+ which raises. These are the possible exit codes which can be raised:

0: No errors.
1: General undefined error.
2: Specified connection file not found.
5: Target computer not in the list of allowed targets.
29: Cannot write to the log file.
30: Profile not found.
87: Invalid command line parameter or combination of command line parameters.
161: The format of the specified path is invalid (filename of the connection file, log file or command options file).
259: No responsive server found in the list (when using /lb).
2382: Invalid notation of the specified host name or IP address.
10060: Connection timed out to the specified server.
11001: Remote hostname not found.

Setting default options

You can set some of the command line options as the default option for Remote Desktop Plus by setting the user environment variable RDP. Currently supported are the following options: /w, /h, /fit, /f, /fullscreen, /max, /mon, /[no]printers, /[no]drives, /[no]sound. [no]wallpaper and /log .
For example, you can set RDP to /fit /mon:2 /noprinters /drives:fixed.

When you set /mon to a number higher than the number of monitors attached to your computer, RDP+ will automatically fall back to monitor 1. This means you can safely set it to 2 if you always want your session to start in the second monitor if it is available.

The default options can of course be overruled by entering the option you want in the command line.
To override the display size with the fixed dimensions from the .rdp file, you can enter either specify /w or /h in the command line, without a dimension.

Group Policies and registry

Some of the behavior of Remote Desktop Plus can be controlled through Group Policies or registry settings. More information about this can be found on this page.

System requirements

• Windows XP/2003/Vista/2008/7
• Microsoft .NET Framework 2.0 or higher

Note: If you intend to launch Remote Desktop Plus from a local network share and you’re running a version of .NET Framework prior to 3.5 SP1, you’ll need to execute the following command once from the command prompt:

%windir%\Microsoft.NET\Framework\v2.0.50727\caspol -q -m -ag LocalIntranet_Zone -zone Intranet FullTrust -n “Network shares” -d “Full rights in Local Intranet zone.”

If you only have .NET 4.0 installed and no previous version of .NET, Remote Desktop Plus (or any other program targeted for previous versions of .NET Framework for that matter) will fail to launch with an error Unable to find a version of the runtime to run this application. You don’t necessarily have to install an older version of .NET to fix this however.
Just create a file named rdp.exe.config with the following content and place it in the same directory as rdp.exe:

Alternatively, you can download a ready-made rdp.exe.config from the download page.

License

Remote Desktop Plus is free to use for home, personal or corporate use. You may use and distribute the program free of charge for both commercial and non-commercial purposes, as long as end users are not charged a fee of any kind for its use.

Download

Current version: 3.12.2
Release date: May 18, 2012

Remote Desktop Plus 3.12.2 (downloaded 22 times)

Click here for the complete change log.

Remote Desktop Plus consists of a single executable. No installation required.

Please feel free to leave your comments, bug reports or suggestions…