In Windows 2008 R2, we added a new MMC snap-in called Remote Desktop Connection Manager (SBMGR.msc on the Connection Broker machine). This Remote Desktop Connection Manager UI tool is available on a Remote Desktop Connection Broker server. It allows the administrator to easily configure and organize RemoteApp and Desktop Connections (RADC) resources. The end users can then access these resources with familiar methods such as Web Access and RADC. These resources include RemoteApp programs and virtual desktops. Virtual desktops include virtual machines in virtual desktop pools and personal virtual desktops.
Here’s a screenshot of Remote Desktop Connection Manager:
The tree view is located in the left pane. The tree view lists all the resources grouped by type (RemoteApp programs and virtual desktops).
The results pane is located in the center. The results pane shows additional information/links, based on the currently selected items in the tree view.
The action pane is located on the right. The action pane lists the actions that are available to users, based on the currently selected items in the tree view or the results pane.
When the RD Virtualization Host Servers node is selected in tree view, the results pane lists all the RD Virtualization Host Servers added to the Connection Broker as below:
When a Pool node is selected in tree view, the results pane lists all the virtual desktops added to the pool as below:
With this useful, easy-to-use UI tool, an administrator can:
The following documents provide details on how to deploy RemoteApp programs and virtual desktops. You'll also find lots of examples on how to use the Remote Desktop Connection Manager UI tool:
Please check it out and share your experience with us.
Can this tool be used with 2008 Server R1?
ctx - Visual Basic Control file / Cipher (encrypted ) file / Creativyst Table Exchange Format file / CyberTracker eXport file / file / Terminal Server .ini file backup.
v2.2 of this great tool has a bug. Trying to find the right Blog to get it noticed!
After a few days of opening and closing connections to servers, the tool crashes. I'm pretty sure it is a memory leak as at executable gets up to 1GB memory in Private Working Set.