Here's a screen shot of an organized RDCMan configuration with the servers organized by version (Exchange 2007, Exchange 2010), region (Chicago, Redmond) and then finally by Exchange role (Client Access, Hub Transport, Mailbox, etc.)įigure 2: An organized RDCMan configuratoin Of course, with 200 servers, it becomes difficult to maintain and navigate, as seen in the following screenshot.įigure 1: Managing RDP connections in the Remote Desktops MMCĪfter I installed RDCMan, it was very clear that our customers and partners would benefit greatly from it, as it fills the gap nicely that the standalone Remote Desktop Connection application and the Remote Desktops MMC snap-in leave behind. Today, they maintain a configuration file for the Remote Desktops MMC with many of their servers. As an example - my customer manages over 200 Exchange servers worldwide. This is particularly useful for system administrators, developers, testers, and lab managers who maintain groups of computers and connect to them frequently. RDCMan is a central place where you can organize, group, and manage your various Remote Desktop connections.

Since these tools are very specific to the Microsoft environment, most of them don't get released externally.Ībout eight months ago, I came across a tool in the repository called Remote Desktop Connection Manager ('RDCMan' for short) written by Julian Burger, one of our principal developers on the Windows Live Experiences team. Many of the tools that are posted are very specific to Microsoft engineering- tools to help developers and testers better manage their project in our internal source control system, provide better visibility into our internal bug/issue tracking system, etc.

Inside Microsoft, we maintain a repository of tools written by our engineers and technical staff.

Remote desktop manager download