How to Backup Host Entry Settings

The procedure to backup & restore your MRC Host List really depends on what version of the software you are currently running, and also what version of the software is running on the new machine.

How To backup & restore your Mini Remote Control saved host list

http://www.dameware.com/support/kb/article.aspx?ID=201065

For Versions prior to 4.4 (including all 3.x versions):

Once you have created your host list, you can export the following DameWare registry key to save your settings:

[HKEY_CURRENT_USER\Software\DameWare Development\NT Utilities\DNTU\DWRCC Settings]

Once the .REG file has been created, it can be imported on any machine to duplicate the Host List and associated settings.

A note of caution: If you use the Windows 2000/XP/2003 Regedit program to export the file it will read REGEDIT5 at the top of the .REG file, which will be incompatible with NT4 and DNTU. If you use DNTU to export the .REG file it will read REGEDIT4 which is compatible with Windows NT4/2000/XP/2003 and DNTU.

For version 4.4 and above:

When version 4.4 or above is run for the first time it will convert the existing Saved Host List information from the Registry to a DMRC database file. The MRC.db (v4.4) or MRC.dbf (v4.5 and above) will then contain all your DMRC Saved Host List entries & settings.

The path for the database files is determined by using the CSIDL_APPDATA internal system variable and appending "\DameWare Development" to the end. For Example: On Windows 2000/XP/2003 this translates to C:\Documents and Settings\{UserName}\Application Data\DameWare Development. On NT4 it would be under the Profiles Directory. If for some reason the O/S does not support this System Variable, then the Application Path is used (i.e. the DameWare Installation folder). But, you can also just search for the file(s).

Beginning with version 4.4, to transfer the Saved Host List you only need to backup the DMRC database files in the DameWare Development installation folder and then restore them to the proper path on the remote machine. If you do not restore the database files to the proper directory on the remote machine then this will trigger the software to rebuild those entries from the information left over in the Registry instead.

** However, please also keep in mind for security reasons, beginning in version 4.0 and above we are now using Microsoft's Security APIs (CryptoAPIs) to Encrypt and store the credentials associated with each individual Host Entry. These credentials are no longer stored along with the rest of the Host Entry information, and therefore will not be included within either method of exporting (i.e. Registry Key or Database). Unfortunately, any credentials associated with your Host Entries must be manually retyped into the software, even when importing/exporting to alternate profiles on the exact same machine.