RDCMan vs mRemoteNG

• Quick
• Easy
• Minimal work on user end

Read full review

• Easy to organize and group servers.
• Many different protocols for remote access.
• The ability to make use of external applications for non-directly supported protocols.
• Servers can inherit settings from nodes above so you can set up properties once making adding new servers/devices very quick.
• Easy to export and share config with new team members (be mindful of what you do with passwords though).

Read full review

• 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).

Read full review

• 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.

Read full review

• 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.

Read full review

• Very easy to hand over connections to new starters.
• Having multiple remote protocols in one place is a massive time saver.

Read full review