RDCMan, or Remote Desktop Connection Manager from Microsoft, creates a single location for IT administrators to organize, group and manage connections, allowing users to manage multiple desktops.
$199
Starting Price
mRemoteNG
Score 9.7 out of 10
N/A
mRemoteNG is a fork of mRemote, an open source, tabbed, multi-protocol, remote connections manager.
N/A
Pricing
Microsoft Remote Desktop Connection Manager (RDCMan)
mRemoteNG
Editions & Modules
1 User
$199.00
Starting Price
5 Users
$779.00
Starting Price
No answers on this topic
Offerings
Pricing Offerings
RDCMan
mRemoteNG
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Microsoft Remote Desktop Connection Manager (RDCMan)
mRemoteNG
Considered Both Products
RDCMan
No answer on this topic
mRemoteNG
Verified User
Manager
Chose mRemoteNG
Every now and then I do look to see if there is any other software that can bring together multiple remote access protocols in a single interface that can contain multiple connections to remote devices with image scaling to mage use of a windowed interface and have yet to find …
Microsoft Remote Desktop Connection Manager (RDCMan)
mRemoteNG
Likelihood to Recommend
Microsoft
The RDCMan software is highly effective at allowing me to organize and manage a large number of servers, and desktop computers. It’s quick and easy to use. It’s also highly reliable. In all the years that I have used it, I have never once experienced a crash or any other sort of error.
Well suited to environments where IT staff need to access multiple servers/systems at the same time, cutting down on time wasted opening multiple windows. Not so useful for users that only need to access one system remotely, as most of its functions are largely unused in that case.
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).
The user interface for configuration is a little basic, and not obvious for a new user to set up connections. It could be a bit clearer how to do that.
It does not seem to automatically update itself to new versions - though older ones work fine, you can miss out on some new functions if you don't check for updates manually.
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.
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.
Every now and then I do look to see if there is any other software that can bring together multiple remote access protocols in a single interface that can contain multiple connections to remote devices with image scaling to mage use of a windowed interface and have yet to find an alternative that does all that but doesn't cost a huge amount. Don't get me wrong I would happily pay for an alternative that could provide an overall better, more convenient experience, but I have yet to find one that has made me think it's worth jumping ship from mRemoteNG.
One positive impact it's had was that it has made it easier to manage servers since this could be done from a central location and through only one program. This, in effect, has helped to increase efficiency and save the time of those doing server management.
Another positive impact was that it is a product that could be deployed/installed by almost anyone, and one that fits reasonably quickly. It also doesn't use a whole lot of system resources when running, so this, in turn, helps the IT/Server Administrators still be efficient in the other work they have to do.
