RDCMan, or Remote Desktop Connection Manager from Microsoft, is a utility for managing multiple remote desktop connections. Once shut down due to a vulnerability in version 2.7, RDCMan is now updated and part of the Sysinternals family of tools. The 2.8 release fixes CVE-2020-0765, the XML parsing vulnerability. As of May, 2025, RDCMan is in version 3.1.
$0
SecureLink Enterprise Access
Score9.1 out of 10
N/A
SecureLink is a platform for remote support in regulated industries. Enterprise software vendors use SecureLink to deliver remote support and services. Hospitals, banks, casinos and other regulated entities use SecureLink to authenticate, control and audit remote access for their vendors, business associates and other 3rd parties.
As a IT specialist we have some servers we need acces to. I like to use Remote Desktop Connection Manager because it feel like you are on the computer. Is feel very trusted. Some colleagues use the Azure remote desktop version but I always recommend the windows integrated option. We also have our primary business application running on a server so they use a remote desktop connection too to log on to the server.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
It does exactly what it needs to. The only times I've had serious issues with rolling out to a vendor is when they have a "contractual agreement" to only use their solution. Almost every vendor that I've worked with and shown this product to has been skeptical for the first 5 minutes and fully converted to liking the ease of use of the product by 10 minutes
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
When trying to connect to a server/machine, and it doesn't connect, there is a "Disconnected" message that is displayed in the thumbnail. There is no information beyond this that explains why the server/machine did/could not connect. It would be helpful to the IT Administrator to know this information, even if Microsoft Remote Desktop Connection Manager (RDCMan) kept a log somewhere where this information can be analyzed.
There doesn't seem to be an option for connecting to a server that is usually only able to be accessed from a jump server. This will not connect if the server is set up as a server/machine within RDCman. This would be a beneficial feature to have within RDCman. Maybe one of the missing options is to be able to set this in the prospects for the jump server (within the Microsoft Remote Desktop Connection Manager (RDCMan) window).
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Java based. Always an issue. I know they are working on this and it will be Javaless if we need it. I know that Java can cause issues across the board and I understand the need of it, but it does not make it any better when there are Java issues.
Stronger integration with the Active Directory. Currently its only read-only, which is good and bad.
I would love to see an App. I know they are working on this as well.
As alluded to in previous responses it is a very functional tool. It allows me to do my job quickly and efficiently every single day. There are little to no issues using the connection on a day to day basis. It handles everything you need from a remote connection perspective.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Plenty of information and support online, and with many things it's pretty straight forward for the average tech to navigate and work with. But with most things online you're not the only person that's had the issue before, and using a search engine you should be able to figure it out.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
The employees at Securelink have always been responsive and seem to be invested in the success of my company. They truly understand what their product means to us so if there is a problem, they are always willing to help. In the rare event that something is found on their end, they will be proactive and reach out to someone to help and get something on calendar for a fix
RDCMan outshines TeamViewer in every possible way. It’s fast, more reliable, and easier to use. I have had frequent crashes and issues when using TeamViewer, while none with RDCMan. Screen responsiveness also seems much better with RDCMan versus TeamViewer. I would often experience lag issues when using TeamViewer.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Securelink seems to work better than LogMein for a large enterprise group. Our company has over 10,000 different connections and securelink manages them well.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
I've found that Securelink allows me to get a vendor access to an application for support purposes much faster than a provisioned VPN account and the red tape around this. I can set up a vendor to access an application suite in a half hour and it will be more secure than regular provisioning.
The ROI is yet to be seen on this, but it certainly makes Compliance, Internal Audit, and Legal very happy, which helps everybody.
Internally, there is much more push back and it has been problematic. For a tech, to have to log in to a server and navigate to a system is considered cumbersome, when before all they had to do was open up Putty or RDP to a server to get in. The only way to combat this is to force them to use Securelink by removing rights. Near impossible for the domain admins.
