When comparing Chrome Remote Desktop vs mRemoteNG, the Slant community recommends Chrome Remote Desktop for most people. In the question“What are the best Remote Desktop tools for Windows?” Chrome Remote Desktop is ranked 9th while mRemoteNG is ranked 14th. The most important reason people chose Chrome Remote Desktop is:
All you need to do is install a Chrome extension.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Simple set-up
All you need to do is install a Chrome extension.
Pro Impressively fast
Faster than most similar applications.

Pro Easy to install
Pro Completely free
There are no restrictions on how you use it.
Pro Cross-platform
Works on Windows, Mac and Linux.
Pro Keeps making sure connection is still wanted
Every few minutes the sharer gets a popup asking if they want to continue sharing the screen, while the popup is shown the viewer can't control anything. This is important in case the sharer forgets to close the connection.
Pro Allows viewer to make actions
If the user that shares their screen doesn't touch the mouse/keyboard the viewer can control them which makes it easy take actions instead of explaining by voice.
Pro It's free
Open source.
Pro Import/Export feature
Allows to share connections.
Pro Can open multiple sessions in different tabs
Pro Connection manager
Lets you organize your connections into folders with icons as well and allows nested folders as well.
Pro Supports multiple protocols
RDP (Remote Desktop/Terminal Server)
VNC (Virtual Network Computing)
ICA (Citrix Independent Computing Architecture)
SSH (Secure Shell)
Telnet (TELecommunication NETwork)
HTTP/HTTPS (Hypertext Transfer Protocol)
rlogin
Raw Socket Connections
Pro Inheritance from folder properties
Inheritance makes it possible to store properties on folder basis and let the underlying connections inherit this info.
Cons

Con Single user only
If multiple users want to connect to a device, they have to take turns.
Con Private keys needs to be managed on PuTTY
Since mRemoteNG is integrated with PuTTY (included in the installation), all private key needs to be configured on PuTTY itself and then the PuTTY session needs to be selected on mRemoteNG.
