Windows

Use RDCMan to keep track of remote desktop connections

Microsoft's Remote Desktop Connection Manager aggregates Windows server remote desktop connections so admins can connect to a server with a point and a click rather than hunting around for a connection.

There are days when I look down at my taskbar and see way too many open connections to servers and I can't remember what's what. In our small IT shop, my staff and I wear many hats, and we all have varying needs to jump on different servers to accomplish a necessary task. It can be a challenge to keep track of our 15 physical servers and our 40 - 45 virtual servers, particularly when it comes to connecting to multiple servers that house related servers. For example, is it the server named SQL04 or is it the server named SQL08 that houses the SharePoint database? As you move into larger environments, it gets even worse as the number of servers grows exponentially.

Microsoft's Remote Desktop Connection Manager (RDCMan) makes our administrative task of keeping track of remote desktop connections much easier. RDCMan aggregates Windows server remote desktop connections so administrators can connect to server with a point and a click rather than hunting around for a connection. Here are configuration tips for getting the most out of RDCMan.

Note: My default is Windows 7, but if you intend to use RDCMan with Windows XP, you may need to install version 6 or higher of the Remote Desktop Connection client software. I also included a link to RDCMan 7 for Windows Vista below.

This blog post is also available as a TechRepublic gallery.

Installation

Installation is a breeze; you just double-click it and then click Next a couple of times (Figure A). Figure A

Installation of RDCMan

General RDCMan options

When RDCMan is installed and you start the program, you're presented with a pretty barren landscape that you need to populate with a top level group, servers, and service groups. Before you begin, you can provide some general parameters that will inform the way the program operates. To set these options, from the Tools menu, choose Options. The Options dialog box contains four tabs: Tree, Client Area, Experience, and Full Screen.

The Tree tab (Figure B) provides you with general options; the most important item on the screen is the Default Group Settings button, which I'll discuss in more detail later in the article. Figure B

The Tree tab
In Figure C, you see the Client Area tab; this is the main part of the RDCMan window and is where server desktops will appear. On the Client Area tab, you can choose the default client area size you'd like to use, as well as the thumbnail size you'd like for minimized connections. Figure C

The Client Area tab
On the Experience tab (Figure D), you can decide how much additional bandwidth you're willing to sacrifice to get closer to a more desktop-like experience. Figure D

The Experience tab
In the Full Screen tab (Figure E), you can specify how you want Full Screen mode to operate. For example, do you want to show the full screen connection bar at the top of the screen? Figure E

Choose Full Screen options
Now, let's go back to the Tree tab's Default Group Settings button. When you click this button, it opens a dialog box that allows you to establish a number of default settings for the group, including Logon Credentials, Access To Local Sources such as sound, and whether or not a Terminal Services gateway server needs to be used for the connections. Figure F shows the Logon Credentials tab, and Figures G and H show the Local Resources and Gateway Settings tabs, respectively. Figure F

Group Properties - Logon Credentials tab
Figure G

Group Properties - Local Resources tab
Figure H

Group Properties - Gateway Settings tab

You are able to override these settings in the individual server connections, if necessary.

The top level group

RDCMan can manage server access in a number of ways. For smaller organizations like mine, it makes the most sense to create a single top level file/group into which individual servers and service groups will be deployed. I'll talk about service groups in a bit, but for now, let's focus on individual servers.

Creating a new top level group is as easy as going to the File menu and choosing New and providing a file name for the top level group. The new file will appear as the top level group in your navigation hierarchy (Figure I). Figure I

The RDCMan top level group

The newly created top level group contains a number of properties that you can set as the default for all of your remote desktop connections. To open the Properties page, right-click the top level group and, from the shortcut menu, choose Properties.

Creating service groups

One of the beauties of RDCMan is its ability to handle server groupings; so now you can create groups of servers that support similar services. For example, I could create a group that includes all of my SharePoint servers so I don't need to hunt around for the right SQL server.

In Figure J, you'll see the Add Group dialog box; I call this a service group since I group like services together. You'll note that the tabs in Figure I are much like the ones shown when you created the top level group and chose default settings for RDCMan. This is one spot where you can override the settings you created in higher level groups. Figure J

Add a new sub group

Add servers

Now you can add individual servers wherever you like -- either in the new service group or in the parent group. To add a server, right-click a group and choose Add server; this opens up the Add Server dialog box that looks a lot like the windows we've seen earlier in this article. It's time to provide the name of the server you'd like to add. You can override the connection settings at this level if necessary. For example, suppose that this server is not a part of the domain and uses different credentials. Figure K shows you the Add Server window. Figure K

Add a new server
When a server is added, it will appear minimized and in a Disconnected state in the client area as shown in Figure L. Figure L

The new server has been added
To establish a connection to the server, just double-click the server's name (Figure M). The client area will house the server desktop and provide you with a single window in which to handle server work from a client desktop. Figure M

Connect to and manage any server

Summary

When you use RDCMan, you can ditch all of your taskbar icons and no longer have to remember dozens of server names. RDCMan also allows administrators to create service groups, preload the utility with server connections, and, ultimately, focus on getting the job done rather than knowing the mechanics behind establishing the connection.

Want to keep up with Scott Lowe's posts on TechRepublic?

About

Since 1994, Scott Lowe has been providing technology solutions to a variety of organizations. After spending 10 years in multiple CIO roles, Scott is now an independent consultant, blogger, author, owner of The 1610 Group, and a Senior IT Executive w...

9 comments
MariaJones
MariaJones

If you are serious about remote access, try the RHUB (http://www.rhubcom.com) appliance which has good remote desktop control & server manager capabilities.

AnnaR2010
AnnaR2010

Thanks for the tip, Scott! Will also be checking out mRemote.

Thierry Frutieaux
Thierry Frutieaux

I'm in charge of RDS farm and i would like to know where i can insert the /admin after the computername. Without this parameter i can't connect directly to my server. But this tools looks good Thank for sharing

merlinpr
merlinpr

Not bad. Personally I use mRemote which can not only handle RDP but also VNC, SSH, Telnet, HTTP/S, etc. It's made my life a lot easier as I use it to manage all of my remote connections to servers and network gear. Unfortunately it's not being actively supported any longer but I just found a fork called mRemoteNG which sounds promising. mRemote: http://www.mremote.org/wiki/MainPage.ashx mRemoteNG: http://www.mremoteng.org/

gointern
gointern

There are also other managers that will let you add VNC connections and other types. Some of them are portable applications which are great on usb flash drive. Which makes them a better choice than RDPMan. mRemote is one of them http://www.google.com/search?q=mRemote

Stalemate
Stalemate

I have been using a simpler method of creating a MMC with the "tools of the trade" such as Users and Computers, DNS, etc. and adding in RDP connectors to the main servers. I will definitely have to try this method.

nigel.bowen
nigel.bowen

This is a great tool with fantastic features, however it fails to take control of a Windows 2000 server console. It creates a new session insted. Yes, I know that Windows 2000 is old and we should move on, but we still have a couple of instances that still need supporting with old legacy apps running on them.

angeld
angeld

With the RDP client I can set the Experience individually for each connection, RDCman only allows a global experience setting, so cannot set different settings for computers on the LAN vs the WAN. Also, with the RDP client, you can select which drives to map, but RDPman is all or nothing, either map all local drives or none. Shame, very nice tool.

Editor's Picks