mRemoteNG vs. N-able Take Control

mRemote is well suited if you need to manage multiple types of servers and/or network devices. Instead of opening a dedicated Putty session and having to manage all of the windows, mRemote can handle all of this with different tabs. If you only have a few devices (less than 10), mRemote could be overwhelming for the need and not quite match up with what you are needing.

Incentivized

It is phenomenal as a remote service tool, as well as a Teamviewer alternative for end users. But its per device interface is lacking, as well as how technicians are set-up. Once you learn the ins and outs its quite easy to use from both sides. However, it can be a little quirky when initially set-up.

Incentivized

• Tabbed Views. Each server remote desktop is viewed in its own separate tab, similar to a web browser. This makes it much quicker and easier to switch between them than using separate windows.
• Storing credentials. You can configure it with log on credentials for each system, saving time on accessing as you don't need to enter a password each time.
• Multiple connection types. I use the traditional RDP the most, but mRemoteNG allows many different connection types, similar to Putty.

Incentivized

• Take Control is really good at accessing a device with no end-user involvement. The user doesn't have to click on permissions or visit a particular site. We simply can take control of their device from the RMM dashboard.
• If Microsoft issues a patch/update, I can schedule a release of a mass install to all client sites at the click of a mouse from within my office.

Incentivized

• Sadly not seeing much in the way of active development these days.
• Have had a few issues where the config file has been messed up (so learnging to back that up was key).
• Interface is functional but not pretty and can be a bit clunky at times.

Incentivized

• Performance on low-end machines.
• Verbosity when changing stream quality.
• File manager needs improving, dragging files causes graphical issues.
• Connection time needs to be reduced.
• Ability to adjust re-connection time.
• Integration with more password-storage applications.
• Screen blanking is buggy in some instances and makes the session unusable.

Incentivized

It's very easy to setup and use. The tree structure organizes the multiple connections in a hierarchical manner which makes it easy to browse and the tabbed browsing make it simple to switch between multiple ongoing connections You can even export the list of connections and import it to another setup.

Incentivized

The interface needs a lot of updating. It's just too "busy."

Incentivized

Never actually needed to use support so have no idea - honestly it's simple enough to use I'd be surprised if anyone really needs support with it.

Incentivized

mRemoteNG is far more useful than LogMeIn when on the same network, or VPN as the servers, as it allows multiple server screens open in multiple tabs. LogMeIn is much more useful when working out of the office for its ability to connect anywhere, but each system accessed is in a separate window making navigation a little tricky. Sometimes I use them in tandem however, LogMeIn to access a machine in my network, then mRemoteNG to access multiple machines from there!

Incentivized

Bad experiences with ConnectWise platforms in general ruled it out for us at this point in time. To be fair this was not really ConnectWise's fault more the team that set things up poorly leading to significant issues across the system. TeamViewer had long been our go to, but pricing increases, the inclusion of ads (in a not inexpensive product) is infuriating for some. and ongoing poor business behavior reports in the industry lead us to look elsewhere

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

Incentivized

• We we're able to bundle Take Control into our RMM pricing removing the need to pay for a separate system and maintain its intergration
• Remote access is only a click away saving our techs time
• Reliable connection mean issues are resolved without having to 'fix' the remote access first