The help file is located in a sub directory called Resources, – unsurprisingly this is called help.htm 2.7 Fixes & Featuresįrom the above help file. For example, when you get a new admin give them a copy of the RDG files and they are able to review your list of servers and get connected easily – assuming they have the permissions…. The RDG files are portable, and you can share them within your organisation.
RDG files in a subfolder of My Documents, which is a redirected folder to a file server. In addition to this, upgrading the tool will typically remove the installation folder thus removing your.
It will install into the x86 Program Files folder on a 圆4 machine:Ĭ:\Program Files (x86)\Microsoft\Remote Desktop Connection Managerĭo not save your custom RDG files in the installation folder, just in case your local workstation dies and the file is gone. There are a couple of things worth noting about the tool:
RDG file in the installation folder, back it up before you upgrade to 2.7 Installation Pointers
Update 3-2-2015: Highlighting the note below as folks are hitting the download link and not reading the notes. The tool can be obtained from the Microsoft download centre.
RDCMan 2.7 supports Windows 8, 8.1, Server 20 R2. Remote Desktop Connection Manager (RDCMan) is a great tool to consolidate multiple RDP connections into a single window to prevent desktop clutter. Please say thank you to Julian Burger for the early Christmas present. The venerable Remote Desktop Connection Manager (RDCMan) 2.2 was starting to show its age.Īfter a slight hiatus, RDCMan 2.7 is now available. Update: #Īfter I initially posted this, Jan Egil Ring, pointed me to his solution which is a bit more elaborate.Update 24-6-2021: RDCMan 2.8.1 is available. While this isn’t a fully automated solution, and I really wish RDCMan could do this for you by querying AD directly and finding new servers and removing the ones that are no longer present and so on, it is a quick way to get your current servers into RDCMan without manually creating each and every entry. The next time you need to update, delete the existing servers, re-run the PowerShell script and import again. Click on the Import Button and all your servers should now be listed in RDCMan. This brings up the Import Servers dialog box where you can browse to the file that the PowerShell script created. This file can then be imported into RDCMan by going to the Edit menu and select Import Servers. This is a simple text file with one server defined on each line. $filename = "Servers-.txt in the path you have specified. $servers = Get-ADComputer -LDAPFilter "(operatingsystem=*Windows Server*)" | select name,dnshostname GetAllServers.ps1 # Import-Module ActiveDirectory This is a very simple solution, but works great in my environment. In an attempt to bridge that gap, I’ve made a very small PowerShell script that queries your Active Directory for server objects and dumps their names into a text file that you can import into RDCMan. One of the things it’s lacking though, is some sort of Active Directory connection that allows you to import all your server objects directly, and not manually add/remove the serves as your infrastructure changes over time. Remote Desktop Connection Manager is a great tool from Microsoft which enables you to keep track of all your RDP sessions and targets in a nice GUI.