mRemoteNG Alternative with Import & Vault

NEO RDP Manager and mRemoteNG compared

As of October 2026. Information on mRemoteNG is based on publicly available sources and may differ by version.

Criterion	NEO RDP Manager	mRemoteNG
Price	free	free, open source
RDP	embedded mstsc.exe – every option of Windows' Remote Desktop Connection	embedded RDP control
SSH & Telnet	built-in terminal with host key checking	via embedded PuTTY
VNC, Rlogin, RAW, HTTP/S, external tools	yes	yes
PowerShell remoting	yes	depending on version
Password protection	always a master password: scrypt + AES-256-GCM per field	file encryption; without a custom password using a well-known default key
Auto-lock	yes, after inactivity and with Ctrl+L	–
Many connections	virtualised list, search with filters (proto:, tag:, folder:, is:fav …)	connection tree with a filter box
Inheritance	credentials across any number of folder levels	fine-grained per property
Import / export	confCons.xml, CSV, RDCMan, .rdp, PuTTY, AD, port scan / confCons.xml, CSV, .rdp	RDCMan, .rdp, PuTTY, AD, port scan / XML, CSV
Interface language	German	multilingual

Familiar from the first click

Folders, inheritance, external tools with %HOSTNAME% variables, Quick Connect, port scan, Wake-on-LAN – everything you know from mRemoteNG is there. Even the click behaviour is the same: a click shows details, a double click connects.

A real vault

Instead of a fixed default key, a master password protects your credentials. The vault locks itself when idle, and RDP passwords never end up in a file.

Fast with large inventories

1,000 connections build up in about a second; search filters within milliseconds per keystroke and connects to the first hit with Enter.

Always a way back

The export writes a confCons.xml that mRemoteNG 1.76 and later opens. So you can go back at any time – or use both tools side by side for a while.

Switching in five minutes

Close mRemoteNG – the connection file usually lives under %APPDATA%\mRemoteNG\confCons.xml.
Install NEO RDP Manager and set a master password.
Import & export → “Import mRemoteNG …” and pick the file; for a protected file, enter the mRemoteNG password.
Check in the preview whether everything should go into a folder of its own, then import.

Folders, all protocols, passwords, inherited credentials, gateways, RDP options, MAC addresses, user fields and the assignment of external tools come along. The detailed walkthrough is in the migration guide.

Frequently asked questions

Can I take over my mRemoteNG connections including passwords?

Yes. The import reads confCons.xml in all common variants – default key, custom password, fully encrypted or the older format – as well as the CSV export, and takes over the passwords too.

Will my external tools keep working?

Yes. The variables are mRemoteNG-compatible (%HOSTNAME%, %USERNAME%, %PASSWORD%, %!VAR%, %-VAR% …); you register the tools themselves once under external tools.

What can mRemoteNG do that NEO RDP Manager can't?

mRemoteNG is multilingual, open source and can also keep its connections in an SQL database for several users. NEO RDP Manager is deliberately a local tool with a German interface.

The mRemoteNG alternative with a vault and import