RDCMan: setup, security risks and alternatives
RDCMan (Remote Desktop Connection Manager) can hold every RDP password your team uses, so the way you set it up decides how much one phished laptop can reach.
Updated: November 2026
Every admin with more than a handful of servers ends up with a tool that remembers all the RDP connections. For a lot of Windows shops that tool is still Microsoft's own free one. Here's how RDCMan works, how to set it up so a new password means one edit, where its saved credentials put you at risk, and which alternatives teams move to.
TL;DR
- RDCMan is Microsoft's free Sysinternals manager for many RDP sessions, and it still gets regular releases.
- Set it up with inheritance and credential profiles so a password change is one edit.
- Saved passwords are only as safe as the Windows account that saved them.
- Need SSH, a shared vault or audit logs? Move to a multi-protocol manager.
What RDCMan is
RDCMan, short for Remote Desktop Connection Manager, is a free Sysinternals tool that keeps many RDP connections in one window. You build a tree of groups and servers, connect to one or a whole group, and watch every session as a live thumbnail.
Under the hood it uses the Remote Desktop ActiveX control, the same component behind mstsc. RDCMan adds the server tree, the thumbnails and a file that stores your layout and logon settings.
Microsoft's Sysinternals page (version 3.22, published October 2026) lists it for Windows 11 and later on the client side and Windows Server 2016 and later on servers. There's no installer. You download the zip or run it straight from Sysinternals Live.
The short history: retired in 2020, back in 2021
RDCMan had a bumpy few years, and it explains why some admins still treat it as abandoned.
On 10 March 2020, Microsoft published CVE-2020-0765, an information disclosure flaw. A crafted .rdg file could use an XML external entity to read files from the machine of whoever opened it. Microsoft's advisory said it wasn't planning to fix the bug, called the application deprecated, and told people to use supported Remote Desktop clients instead.
Then it came back. On 10 August 2021, Microsoft revised the same advisory: RDCMan 2.82 was out through Sysinternals and the vulnerability was addressed. It has stayed a Sysinternals tool since and keeps getting new releases. Version 3.20 in August 2026 added Azure Virtual Desktop workspace feeds and Microsoft Dev Box support, and 3.22 followed on 15 October 2026.
The takeaway for a support team is simple. Any copy older than 2.82 is the vulnerable one. If someone on the team still runs a version from the 2.7 era because "it works", that's the first thing to replace.
How to set up RDCMan properly
The part people skip is the structure. Get it right once and a password change becomes a single edit instead of forty.
Files, groups, servers. The top level is a file (an .rdg). Inside it sit groups, and inside groups sit servers. A group holds either more groups or servers, never both. When RDCMan refuses to mix servers and groups, the target group already holds subgroups: add the server to one of them, or create a new subgroup for it. A common layout is one file per client or per environment, with groups for roles like domain controllers, file servers and RDS hosts.
Inheritance. Every property page has an "Inherit from parent" box. Set logon, gateway and display settings once at the file or group level and let the servers inherit them. A server only overrides what's different about it.
Bulk adds. The Add Server dialog takes patterns. server[001-15] adds fifteen servers, and {dca,dcb}rack[1-5] expands every combination. You can also import a text file with one server name per line.
Credential profiles. Instead of typing a password into each group, create a profile once and point groups at it. When the password changes, you edit the profile. For shared .rdg files, create a profile with the same name in each admin's own global store, so the shared file carries the profile name and no password.
Gateway settings. If the servers sit behind Remote Desktop Gateway, set it on the group's Gateway Settings tab. Microsoft's FAQ adds one gotcha: gateways must be entered as a fully qualified domain name, such as rdgw.example.com rather than rdgw, or you get errors like 50331656.
URTech's walkthrough covers the groups, thumbnails and settings tabs on a current build.
Where RDCMan puts you at risk
The tool itself is small. The risk sits in what it remembers.
So is RDCMan secure? The program is maintained, and the 2020 bug is fixed from version 2.82 on, so a current copy is as safe as the passwords, accounts and files you give it. Saved RDP passwords are a standard target in credential harvesting, so start with the four points below.
Saved passwords. RDCMan encrypts stored passwords with CryptProtectData, which ties them to your Windows user, or with an X509 certificate. That stops someone copying the .rdg file to another machine and reading it. It doesn't stop code running as you. Public red-team tooling documents decrypting RDCMan.settings and .rdg passwords from an unprivileged session, as long as it runs under the user who saved them. One phishing click on an admin's laptop, and every saved server password comes with it.
Domain admin in the tree. The worst case is a group at the top of the tree that inherits a domain admin account down to every server. That turns one compromised workstation into the whole domain. The same pattern shows up in our privileged access management guide: standing admin credentials on a daily-driver machine are what attackers look for first.
Untrusted .rdg files. The 2020 bug came from opening a file someone else crafted. Treat .rdg files like scripts. Don't open ones that arrive by email or from a vendor you haven't checked.
Thumbnail focus. Microsoft's own page warns that keyboard navigation in the thumbnail view can hand focus to a connected server without it being obvious. Typing a command into the wrong production box is a less glamorous risk, but it happens.
Safer ways to run it
You can keep RDCMan and still close most of that risk.
- Save no domain admin passwords. Store a low-privilege account or nothing, and let RDCMan prompt. Use Connect As when you need elevated rights for one session.
- Use a separate admin workstation or jump host. Run RDCMan from a hardened machine that doesn't browse or read email, not from the laptop you use for everything else.
- Put RD Gateway in front. Servers shouldn't accept RDP from the internet. A gateway gives you one hardened entry point, and it can require MFA.
- Keep Network Level Authentication on. NLA makes the client authenticate before a full session starts. Leave "authentication of the remote machine is required" on in RDCMan's Security Settings too.
- Check the version. Anything older than 2.82 still has the 2020 XXE bug. Files saved by the current version won't open in older ones, and RDCMan keeps the original as a .old backup, so upgrade the whole team together.
If you can't do the first two, the credential store is the weak point. That's the moment to look at a tool built around a proper vault, and the checklist in our RMM security guide applies to it as well.
That thread from December 2025 is a fair snapshot of where admins land: RDCMan, Devolutions, Royal TS and mRemoteNG, in roughly that order of mentions.
RDCMan security settings, tab by tab
The list above maps to a handful of property tabs. Set them on the file or a top-level group and let the servers inherit them, as in the setup section.
- Security Settings. Controls whether authentication of the remote machine is required before a connection is established. Keep it required. On the servers, keep Network Level Authentication on; our RDP security guide shows how to enforce it with Group Policy.
- Encryption Settings. Found in File Settings and Default Group Settings. CryptProtectData ties stored passwords to your Windows account. A certificate lets the file move to another machine, but only after you export the certificate with its private key, and anyone holding that key can read the passwords.
- Local Resources. Drive, port, printer, smart card and clipboard sharing. Each one opens a path between the server and your admin machine, so turn on only what the job needs. Smart card logons need "Redirect smart cards" here.
- Gateway Settings. You can enter separate gateway credentials or share them with the remote server. Separate credentials mean one password doesn't open both the gateway and the server.
- Display Settings. Clear "Allow thumbnail session interaction" so keyboard navigation in the thumbnail view can't pass your keystrokes to a live session.
One machine-wide policy helps too. A non-zero DWORD named DisableLogOff under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\RDCMan removes the log off command everywhere in RDCMan, so a misclick can't end a session someone is still working in.
RDCMan alternatives
RDCMan is Windows-only, RDP-only and single-user by design. Teams usually move on for one of four reasons: they need SSH and other protocols in the same tree, a shared vault for several admins, macOS support, or audit logs of who connected where.
| Tool | Protocols | Credential storage | Good fit |
|---|---|---|---|
| RDCMan | RDP | Encrypted per user or by certificate, in the .rdg | Solo admin, Windows servers, free |
| mRemoteNG | RDP, SSH, VNC, Telnet and more | Local connection file, optionally password-protected | Free multi-protocol, one admin |
| Royal TS | RDP, SSH, VNC, web and more | Document-based, can be shared | Small teams, Windows and macOS |
| Devolutions Remote Desktop Manager | Very broad protocol list | Local or shared vault, integrates with password managers | Teams needing a shared vault and audit trail |
| Windows App | RDP | Work account for cloud services, no sign-in for remote PCs | Azure Virtual Desktop, Windows 365 and remote PCs |
Windows App needs a note of its own. Microsoft positions it as the replacement for the Remote Desktop client. Its overview page, updated July 2026, lists remote PC connections on Windows as supported but not Remote Desktop Services, and says to keep using the Remote Desktop app for those. Its documented features include favorites and search but no group tree with inherited settings, so for a room full of on-premises servers, mstsc or a manager like the ones above is still the practical choice.
In that October 2025 thread, the top reply points at Devolutions for its free solo tier and vault integrations. Another answer settles a common worry: mRemoteNG runs fine on current .NET, not only the older runtime its original poster was worried about.
Is RDCMan a VNC alternative?
Only for Windows machines that accept RDP. VNC uses the RFB protocol, which works at the framebuffer level, so the RFB specification applies it to X11, Windows and Mac systems alike. Clients connect on TCP port 5900 by default. VNC also mirrors the screen the person at the machine sees, while an RDP connection to a Windows desktop locks the local screen.
RDCMan only speaks RDP, so it can't open a VNC host. If your tree mixes both, mRemoteNG, Royal TS and Devolutions handle VNC next to RDP. For machines no connection manager can reach, read on.
When a connection manager isn't the right tool
A connection manager assumes you reach every machine over RDP from a network that can see it. That holds for a server room. It breaks for laptops at home, clients behind other firewalls, and anything you'd rather not expose on port 3389.
That's where agent-based remote access takes over, which our remote access software roundup covers.
OpenFrame, the open, AI-native infrastructure for IT and security that we build, takes that route. Its agent gives you remote access to a client's devices or your own fleet, and it can run a script across them and collect the output in one place, so a quick check doesn't need an RDP session at all. It costs $1 per device a month with 10 million AI tokens included, and there's a 14-day free trial.
RDCMan, in short
RDCMan is still a solid free way to manage RDP sessions to Windows servers, as long as you run version 2.82 or later. Set it up with inheritance and credential profiles, keep domain admin passwords out of it, and run it from a hardened machine behind RD Gateway. When you need a shared vault, other protocols or audit logs, move to a multi-protocol manager.
Next, see how the same thinking applies to standing admin rights in our guide to privileged access management.

Aliaska Varieva
VP of Engineering
Hi! I’m Aliaska, and I’ve been working as a software engineer (mostly Java + a bit Kotlin) for over 8 years now. I mostly spend my time building backend services, integrating systems, fixing bugs (the fun part 🙃), and making sure things don’t fall apart behind the scenes.
Related Content
Frequently Asked Questions
/blog/rdcman
Still deciding?
Ask Mingo answers from our docs and customer stories.