Updating to RDCMan 2.8

Now that we have a new version of Remote Desktop Connection Manager (RDCMan), I wanted to list out some of my initial thoughts and upgrade experience as I did encounter  a couple of minor bumps.  Please add a comment if you are running into issues as well please.

Like many other administrators, I heavily used RDCMan 2.2 and 2.7 over the last 11 years.  This was my primary tool for managing a wide range of lab and test VMs which were running on-premises and in Azure.  So I was also unhappy to see the security issue with RDCMan 2.7 and its demise.

RDCMan 2.8 Release

RDCMan was previously installed using a MSI file - rdcman.msi which was obtained from the Microsoft Download Centre.  Since it is MSI based, it had to be installed onto the machine.

This has changed with the 2.8 release as it is a stand alone .exe which is not surprising as that is also true for many of the other Sysinternals tools.

RDCMan 2.7 would install its payload to this path:

"C:\Program Files (x86)\Microsoft\Remote Desktop Connection Manager\RDCMan.exe"

RDCMan 2.8 Interface

The below is an existing installation of RDCMan 2.7

RDCMan 2.7 Interface

After upgrading, the overall structure remains the same.  The version is updated, and Sysinternals branding can be observed in the title bar.

RDCMan 2.8 Interface

RDCMan Configuration File Upgrade

The release notes state that old RDG files will be updated to a new schema.  This happened automatically.

For example, the below was from RDCMan v2.7 build 1512.0

RDCMan 2.7 Configuration File

<?xml version="1.0" encoding="utf-8"?>

<RDCMan programVersion="2.7" schemaVersion="3">
<credentialsProfiles />

After this was opened with the 2.8.1 version, you can see that the version information was changed.

RDCMan 2.8 Configuration File

<?xml version="1.0" encoding="utf-8"?>

<RDCMan programVersion="2.81" schemaVersion="3">
<credentialsProfiles />

After opening the configuration files using RDCMan, they were saved and updated.

RDCMan 2.8 Configuration File - Updated

Uninstalling RDCMan 2.7

Prior to using the 2.8.1 version, I manually removed 2.7 from the machine.  This can be done using Add/Remove programs or command line.

Since I have to do this on multiple machines, using the command line will speed things up.  To obtain the command line uninstall string, the uninstall command was obtained from the registry as shown below:


RDCMan 2.7 Uninstall Information In Registry

MsiExec.exe /X{D86D602C-BD19-49B3-B661-2AB143CFC728}
MsiExec.exe /X{D86D602C-BD19-49B3-B661-2AB143CFC728} /Passive

Uninstalling RDCMan 2.7 Using Command Line

RDCMan 2.8 Download

RDCMan 2.8.1 was downloaded from aka.ms/RDCMan and placed into the folder where I keep the other Sysinternals tools.

Ensure that you go into the file's properties and unblock it.  Unblock-File in PowerShell could also be used.

RDCMan 2.8 Downloaded & Saved Locally

Persistent Bitmap Caching Configuration

Since this machine had an older RDCMan installed, there was an issue with  the persistent bitmap caching setting.  This is the global configuration file called RDCMan.settings and is stored in:

C:\Users\%username%\AppData\Local\Microsoft\Remote Desktop Connection Manager

RDCMan.settings File Persisted Setting - Global Configuration Has Not Loaded Completely

<?xml version="1.0" encoding="utf-8"?>
<Settings programVersion="2.7">


Renamed the RDCMan.settings file to .old

RDCMan was then able to open.

Upon closing, it save a new RDCMan.settings file with an updated schema

<?xml version="1.0" encoding="utf-8"?>
<Settings programVersion="2.81">

Blurry Remote Session

In the image below the background image is the remote RDCMan session, and the foreground is the local PC.  Note how much sharper the local image is.

Blurred Remote RDCMan Session - Changed Local DPI Scaling

Changed the scaling on local machine to 100%.  It was 125% previously.


Rhoderick Milne [MSFT]

Leave a Reply

Your email address will not be published. Required fields are marked *