Remote Desktop Connection Manager descargar
Sign in to add and modify your software Show
By joining Download.com, you agree to our Terms of Use and acknowledge the data practices in our Privacy Policy.
Finally we have good news for all fans of the Remote Desktop Connection Manager (RDCMan) tool! It has risen from the ashes, and is now part of Sysinternals. Over the years RDCMan built up a strong user base as it was a simple but powerful utility to manage connections to multiple machines. Sure, if you have three or four servers to manage you can get by with saved .rdp files or use the Universal Microsoft Store Remote Desktop app. Have a few dozen? That does not scale and you need a tool to help manage this. Download LinksHere are a few options for downloading the current RDCMan builds. Main page with related documentationRemote Desktop Connection Manager - Windows Sysinternals | Microsoft Docs Sysinternals Live Site with direct download linkhttps://live.sysinternals.com/RDCMan.exe Microsoft AKA Vanity linkaka.ms/RDCMan DocumentationThe main Sysinternals download page has a lot of good content to review. For those that are already familiar with RDCMan you can jump right in. Just note that the current .RDG files will be upgraded automatically. RDCMan HistoryI'll park this here for a bit of context and history for those that are interested. RDCMan was initially an internal tool developed by Julian Burger and was stored on the internal toolbox site. Word of mouth quickly grew and it became very popular internally. Then customers noticed it being used for demos etc. and asked for a copy. The work to release it externally started. Legal, trademark, compliance and security all had to be reviewed as part of the release. This was done by Julian and David Zazzo who was an Exchange consultant at the time. That is why you see the initial announcement on the EHLO blog. Version 2.2 was the initial public release back in May 2010. Julian continued to work on RDCMan, adding features and fixing issues. There were many internal releases, again to the internal toolbox site, but not on the public download centre. Customers again noticed that the build information was different, and started to ask about a newer version. This went on for a couple of years. RDCMan 2.7 was released in November 2014. Many features were added such as support for Windows 8 and Server 2012. Julian continued to make improvements via some additional internal releases. The release frequency slowed due to competing priorities, and then unfortunately Julian left Microsoft. Development ceased on RDCMan. Time went on and RDCMan really started to show its age with changes to display resolution amongst other issues. No changes could be made. Many, many people pinged me asking if I knew who was maintaining the tool and how it was moving forward. There were some attempts to do so, but ultimately they did not bear fruit. March 2020 hammered in the final coffin nail for the 2.7 version of RDCMan via the announcement of a security issue in CVE 2020 0765. "An information disclosure vulnerability exists in the Remote Desktop Connection Manager (RDCMan) application when it improperly parses XML input containing a reference to an external entity. An attacker who successfully exploited this vulnerability could read arbitrary files via an XML external entity (XXE) declaration. To exploit the vulnerability, an attacker could create an RDG file containing specially crafted XML content and convince an authenticated user to open the file." Since there was no support for RDCMan, the download was removed. The world was sad. As part of the removal, other tools were promoted. You may have seen the page stating to use standard RDP of the Windows 10 Universal Client. While those are supported clients, neither had the features that administrators wanted. That was why RDCMan became so popular in the first place. Some folks continued to use RDCMan and not open anyone else's configuration file, and others turned to 3rd party solutions with a range of results. Some good. Some not so much. All seemed lost until Mark Russinovich tweeted this back in February 2021. At this point RDCMan has celebrated its 10th birthday! With Mark's support let's hope it has many more celebrations in the years ahead! Cheers, Remote Desktop Connection Manager (RDCMan) manages multiple remote desktop connections. It is useful for managing server labs or large server farms where you need regular access to each machine such as automated check-in systems and data centers. It is similar to the built-in MMC Remote Desktops snap-in, but more flexible. The RDCMan 2.7 version is a major feature release. New features include:
Supported Operating Systems: Windows 10 Tech Preview , Windows 7, Windows 8, Windows 8.1, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server. Tech Preview:Users using Windows XP or Windows Server 2003 will need to obtain version 6 or newer of the Remote Desktop Connection client software.
https://www.microsoft.com/ SHA-1:87fbd2bcb0353dad176464bb8300a6ff4df5fbe1Filename:rdcman.msiWe don't have any change log information yet for version 2.7.1406.0 of Remote Desktop Connection Manager. Sometimes publishers take a little while to make this information available, so please check back in a few days to see if it has been updated. Can you help?If you have any changelog info you can share with us, we'd love to hear from you! Head over to ourContact pageand let us know.
By Julian Burger Published: January 27, 2022 Download Remote Desktop Connection Manager (519 KB)Run now from Sysinternals Live. IntroductionRDCMan manages multiple remote desktop connections. It is useful for managing server labs where you need regular access to each machine such as automated checkin systems and data centers. Servers are organized into named groups. You can connect or disconnect to all servers in a group with a single command. You can view all the servers in a group as a set of thumbnails, showing live action in each session. Servers can inherit their logon settings from a parent group or a credential store. Thus when you change your lab account password, you only need to change the password stored by RDCMan in one place. Passwords are stored securely by encrypting with either CryptProtectData using the (locally) logged on user's authority or an X509 certificate. User with OS versions prior to Win7/Vista will need to get version 6 of the Terminal Services Client. You can obtain this from the Microsoft Download Center: XP; Win2003 Upgrade note: RDG files with this version of RDCMan are not compatible with older program versions. Any legacy RDG file opened and saved with this version will be backed up as filename.old The DisplayThe Remote Desktop Connection Manager display consists of the menu, a tree with groups of servers, a splitter bar, and a client area. There are several top-level menus in RDCMan:
The TreeMost work, such as adding, removing, and editing servers and groups, can be accomplished via right-clicking on a tree node. Servers and groups can be moved using drag-and-drop. Keyboard shortcuts:
Use the [View.Server tree location] menu option to locate the tree at the left or right edge of the window. The server tree can be docked, auto-hidden, or always hidden via the [View.Server tree visibility] menu option. When the server tree is not displayed, servers can still be accessed through the Remote Desktops menu. When the tree is auto-hidden, the splitter bar remains visible at the left side of the window. Hovering over it will bring the server tree back into view. The Client AreaThe client area display depends on the node selected in the tree. If a server is selected, the client area shows the remote desktop client for that server. If a group is selected, the client area shows a thumbnail of the servers within that group. The size of the client area can be specified via the View menu, as well as resizing the RDCMan window. Use [View.Lock window size] to prevent the window from being resized by dragging the frame. Caution: Connected servers can receive focus from keyboard navigation of the thumbnail view. It is not always obvious which server has focus, so be careful. There is a setting to control this: [Display Settings.Allow thumbnail session interaction]. Full Screen ModeTo work with a server in full screen mode, select the server to give it focus and press Ctrl+Alt+Break (this key is configurable, see Shortcut Keys.) To leave full screen mode, press Ctrl+Alt+Break again or use the minimize/restore buttons in the connection title bar. Multiple monitors can be spanned if enabled by the monitor spanning option. Shortcut KeysYou can find the full list of Terminal Services shortcut keys here. Some of these can be configured from the Hot Keys tab. FilesThe top-level unit of organization in RDCMan is a remote desktop file group. File groups are collections of groups and/or servers that are stored in a single physical file. Servers can't live outside of a group and groups can't live outside of a file. A file has all the characteristics of a server group other than being able to change its parent. GroupsA group contains a list of servers and configuration information such as logon credentials. Configuration settings can be inherited from another group or the application defaults. Groups can be nested but are homogenous: a group may either contain groups or servers, but not both. All the servers in a group can be connected or disconnected at once. When a group is selected in the tree view, the servers underneath it are displayed in a thumbnail view. The thumbnails can show the actual server windows or simply the connection status. Global thumbnail view properties can be adjusted via the [Tools.Options.Client Area] tab while group/server-specific settings are in Display Settings. Smart GroupsSmart groups are populated dynamically based on a set of rules. All ancestors of sibiling groups of the smart group are eligible for inclusion. The Connected Virtual GroupWhen a server is in the connected state, it is automatically added the to Connected virtual group. Servers cannot be explicitly added or removed from the Connected group. The Connected group can be toggled on/off via the View menu. The Reconnect Virtual GroupThere are sometimes situations where a server disconnects and will be intentionally offline for an unspecified length of time, e.g. when rebooting after an OS update. When this is the case, drag the server in question to the Reconnect group. RDCMan will continually attempt to connect to the server until it is successful. The Reconnect group can be toggled on/off via the View menu. The Favorites Virtual GroupThe Favorites virtual group is a flat file of your favorite servers. You can add any server from the server tree. This is helpful when you have many servers in the tree and often work with a handful of servers from different groups. The Favorites group can be toggled on/off via the View menu. The Connect To Virtual GroupThe Connect To Virtual Group contains the servers that are not members of user-created groups. See Ad Hoc Connections for details. The Connect To group is visible while ad hoc connections exist and disappears when there are none. The Recent Virtual GroupThe Recent Virtual Group contains the servers that have been recently accessed. The Recent group can be toggled on/off via the View menu. ServersA server has a server name (the computer's network name or IP address), an optional display name, and logon information. The logon information may be inherited from another group. Adding Servers ManuallyServers names following a pattern can be bulk added to a group. There are two pattern classes:
Examples:
Importing Servers from a Text FileServers can be imported into a group from a text file. The file format is simply one server name per line: Server1 SecondServer YANSServer names may also be explicitly specified in the dialog. All servers are imported into the same group with the same preferences. If a server is imported that has the same name as an existing server, the existing server's preferences are updated to the new ones. Ad Hoc ConnectionsAd hoc server connections can be created via the [Session.Connect to] feature. These servers will be added to the Connect To Virtual Group. From there they can be converted into real servers by moving them to a user-created group. Servers remaining in the Connect To group are not persisted when RDCMan exits. Windows AzureIn the [Connection Settings] tab, enter the role name and role instance name into Load balance config as described here e.g. Cookie: mstshash=MyServiceWebRole#MyServiceWebRole_IN_0#Microsoft.WindowsAzure.Plugins.RemoteAccess.Rdp Session ActionsWhile in a session, the focus can be released to another session or the server tree.
Certain key combinations and Windows actions can be tricky to perform over the remote session--particularly when RDCMan itself is started within a remote session--e.g. Ctrl+Alt+Del. These are available from the [Session.Send keys] and [Session.Remote actions] menu items. Global OptionsThe [Tool.Options] menu item brings up the Options Dialog. Global settings, e.g. the client area size, are modifiable from here. Most server-related options, e.g. hot keys and those on the experience page, will not take effect until the next time that server is connected. GeneralHide main menu until ALT pressed Auto save interval Prompt to reconnect connected servers on startup Default group settings TreeClick to select gives focus to remote client Dim nodes when the tree control is inactive Client AreaClient Area Size Thumbnail Unit Size Hot KeysMany of the remote desktop hot keys are configurable. There is a limited mapping, however. For example if the default key is ALT-something, the replacement must also be ALT-something. To change a hot key, navigate to the text box for the hot key and press the new "something" key. ExperienceDepending on the bandwidth available from your machine, you will want to limit Windows UI features to improve performance. The connection speed drop down can be used to set all options together, or they can be individually customized. The features are: desktop backgrounds, showing full window contents when dragging, menu and window animation, and windows themes. Full ScreenShow full screen connection bar Full screen window is always on top Use multiple monitors when necessary Local OptionsGroups and Servers have a number of tabbed property pages with various customization options. Many of these pages are common to groups and servers. When the "Inherit from parent" check box is checked, the settings that follow are inherited from the parent container. Most server-related changes, e.g. remote desktop size, will not take effect until the next time that server is connected. File SettingsThis page only appears for the properties of a file. It contains options for the file's group name, shows the full path to the file (which can't be edited), and has a comment field. Group SettingsThis page only appears for the properties of a group. It contains options for the group name, parent nesting, and a comment. Server SettingsThis page only appears for the properties of a server. It contains options for the server name, its display name, parent nesting, and a comment. SCVMM virtual machines can be connected to via RDP into the host using the VM console connect option. Use the PowerShell command: get-vm | ft ElementName,Name,Idto determine the id corresponding to the VM. Logon CredentialsThe Logon Credentials property page contains options pertaining to remote login. The user name, password, and domain are set on this page. The domain and user name can be specified together by using the domain\user format. When logging in to a machine "domain" rather than a Windows domain, you can specify [server] or [display]. This former will be substituted with the server name, the latter with the display name, at logon time. It is useful when you have a group of machines which require logging in as administrator. The Logon Settings entered in the properties pages are used by default for new connections. If you want to temporarily customize these settings for a new connection, connect using the Connect As menu item. Gateway SettingsThe Gateway Settings property page has options for using a TS Gateway Server. The Gateway name, authentication method, and local address bypass options are on this page. Users of operating systems starting from Vista SP1 and Longhorn server will have additional options regarding logon credentials: Explicit entry of Gateway user name and password Ability to share the Gateway credentials with the remote server Connection SettingsThe Connection Settings tab includes settings to customize how a session is connected and what happens upon logon. You can specify whether the console session should be connected to as well as the remote desktop connection port. There are also settings that allow you to run a program upon connection. Enter the program name and, optionally, the working directory for that program. Note that these only have an effect if you are connecting to the console session for the first time. That is, reconnecting to a session or connecting to a session other than the console session will not run the program. (At least, this is how Terminal Services appears to work based on empirical observation.) Remote Desktop SettingsThe size of the remote desktop is specified on this page. This is the logical desktop size, not the physical client view of it. For example, if the remote desktop size is 1280 x 1024 and client size is 1024 x 768, you would see a 1024 x 768 view of the remote desktop with scroll bars. If the client size were 1600 x 1200, the entire remote desktop would be visible, offset by a gray border. Specifying "Same as client area" will make the remote desktop the same size as the RDCMan client panel, i.e. the RDCMan window client area excluding the server tree. Specifying "Full screen" will make the remote desktop the same size as the screen that the server is viewed on. Note that the remote desktop size is determined upon connecting to a server. Changing this setting for a connected server will have no effect. The maximum size of the remote desktop is determined by the version of the remote desktop activeX control. Version 5 (pre-Vista) had a maximum of 1600 x 1200; Version 6 (Vista) has a maximum of 4096 x 2048. This limit is enforced at connection time, not during data entry. This is in case the same RDCMan file is shared by multiple computers. Local ResourcesVarious resources of the remote server may be delivered to the client. The remote computer sound can be played locally, played remotely, or disabled entirely. Windows key combinations (for example, those involving the actual Windows key as well as other specials like Alt+Tab) can be applied always to the client machine, always to the remote machine, or to the client when windowed and the remote machine when in full screen mode. Client drive, port, printer, smart card, and clipboard resources can be automatically shared to the remote machine. Security SettingsYou can specify whether authentication of the remote machine is required before a connection is established. Display SettingsThumbnail display settings are customizable from this page. The first option is: thumbnail scale. This specifies how many thumbnail units to allocate to the display of a given server. All servers default to a scale of 1. You can change this to increase the display of important servers. For example, a server could be scaled by 3 or 5 making the remote session quite usable in the thumbnail display while still permitting a view of many other servers. This is the only option for servers. There are three additional options for groups: preview session in thumbnail, allow thumbnail session interaction, and show disconnected thumbnails. The first whether or not the thumbnail view shows the actual live connection, continually updated. The second, dependent on the first, specifies whether the thumbnail session is usable. The final option controls whether disconnected servers appear in the thumbnail view. Encryption SettingsRDCMan can encrypt the passwords stored in files either with the local user's credentials via CryptProtectData or an X509 certificate. The Encryption Settings tab is available in the Default Group Settings and File Settings dialogs. Personal certificates of the current user which have a private key are available for encryption. You can create such a certificate in the following manner: New-SelfSignedCertificate -KeySpec KeyExchange -KeyExportPolicy Exportable -HashAlgorithm SHA1 -KeyLength 2048 -CertStoreLocation "cert:\CurrentUser\My" -Subject "CN=MyRDCManCert"This will create a certificate called "MyRDCManCert" in the Personal Certificates store of the current user. To install this cert on another computer, you must export it with the private key. Profile ManagementCredential profiles can be added, edited, and removed from this tab. List Remote SessionsRDCMan has limited support for managing remote sessions other than those connected from it. The [Session.List Sessions] menu item invokes the feature. Note that the account running RDCMan must have Query Information permissions on the remote server to list the sessions. Furthermore, the remote session must be directly reachable rather than via a gateway server. Disconnect and Logoff permissions must be granted to perform those operations. See msdn for more information on remote desktop permissions. Command LineBy default, RDCMan will open the files that were loaded at the time of the last program shutdown. You can override this by specifying a file (or files) explicitly on the RDCMan command line. Additionally, the following switches are accepted:
Find ServersThere is a dialog for finding servers accessed via Ctrl+F or the Edit.Find (servers) command. All servers matching a regular expression pattern are displayed in the dialog and can be acted on via a context menu. The pattern is matched against the full name (group\server). Credential ProfilesCredential profiles store logon credentials globally to RDCMan or in a file. This allows for using the same stored credentials across groups that do not have a common ancestor. One use scenario is to store credentials used for logging into servers and gateways in a single place. When a password changes, it can be edited once. Another scenario is when sharing RDG files across a group. Instead of storing passwords in the file (which would have issues due to the user-specific nature of the encryption RDCMan uses), a profile is created such as "Me" which each user defines in their Global store. You can update the settings for a credential profile in two ways. The first is to edit from a credentials dialog and then save the exact same profile name/domain to the same store (file or global). That will ask if you want to update. The other way is to go to the group properties for the credential store (again, file or global) and use the Profile Management tab. File scope credential profile passwords are encrypted according to the containing file's Encryption Settings. Global credential profiles use the Default Group Settings. PoliciesRDCMan retrieves policy information from the HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\RDCMan registry key.
FAQ
DownloadDownload Remote Desktop Connection Manager (519 KB)Run now from Sysinternals Live. Runs on:
|