
The above image shows the retracted “Errors and Info” and “Screenshots” tabs on the bottom of the program’s window. Hovering the mouse over a tab causes the pane to fly out, just like Visual Studio. If you unpin a pane it retracts into the side of the mRemote console and shows itself as a tab. The Config pane displays all of the configuration information for the selected connection or folder as well as allowing you to edit the information. For instance, the Connections pane is where you manage all of your connection files and folders. MRemote uses pinable information panes for all of it’s various information consoles. Anyone who is familiar with Visual Studio or the SQL Server Management Studio will instantly be at home with mRemote. One of the best features of mRemote is it’s user interface. However, you can also use the Gecko (Firefox) rendering engine if you download the free XULrunner. HTTP and HTTPS connections can be made within mRemote using the Internet Explorer rendering engine. All mRemote packages come with PuTTY already included in the files.

Telnet, SSH, rlogin and RAW connections require the use of PuTTY as an external helper application. Citrix ICA connections require you to download the free ICA Client from. MRemote supports creating connections with the following protocols:Ĭonnections using RDP require version 6.0 of the Microsoft Terminal Services Client. However, in spite of the project having been officially halted, mRemote is quite mature and has no crippling restriction on its available features like the free version of vRD does.

The mRemote project was actively developed up until late 2008 when it was merged with a commercial, closed-source multiple remote desktop tool called vRD. One way to save both money and aid in the administration of multiple remote systems is with the free and open-source tool mRemote (released under the GPL license). You may have managed to get a copy of Windows 7 out of the budget, but not much else.


At the same time, budgets are getting smaller and smaller. It seems as if the ratio between Systems Administrators and the systems that they must manage is getting higher and higher.
