To obtain the command line uninstall string, the uninstall command was obtained from the registry as shown below: Since I have to do this on multiple machines, using the command line will speed things up. This can be done using Add/Remove programs or command line. Prior to using the 2.8.1 version, I manually removed 2.7 from the machine. This happened automatically.įor example, the below was from RDCMan v2.7 build 1512.0Īfter this was opened with the 2.8.1 version, you can see that the version information was changed.Īfter opening the configuration files using RDCMan, they were saved and updated. The release notes state that old RDG files will be updated to a new schema. The version is updated, and Sysinternals branding can be observed in the title bar. The below is an existing installation of RDCMan 2.7Īfter upgrading, the overall structure remains the same. "C:\Program Files (x86)\Microsoft\Remote Desktop Connection Manager\RDCMan.exe" RDCMan 2.8 Interface RDCMan 2.7 would install its payload to this path: exe which is not surprising as that is also true for many of the other Sysinternals tools. This has changed with the 2.8 release as it is a stand alone. Since it is MSI based, it had to be installed onto the machine. RDCMan was previously installed using a MSI file - rdcman.msi which was obtained from the Microsoft Download Centre. So I was also unhappy to see the security issue with RDCMan 2.7 and its demise. This was my primary tool for managing a wide range of lab and test VMs which were running on-premises and in Azure. Like many other administrators, I heavily used RDCMan 2.2 and 2.7 over the last 11 years. Please add a comment if you are running into issues as well please. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |