How can I move IPNetwork Monitor from one server to another?

How can I move IPNetwork Monitor from one server to another? Q: I need to move my IPNetwork Monitor installation onto another computer. I would like to keep monitoring database intact. How can I do that? A: If you need to move registered copy of the IPNetwork Monitor from one system to another, please choose the corresponding transfer path from the sections below: moving to the same version and build, upgrading or downgrading:

1. Transfer IPNetwork Monitor to another system keeping the same version and build

1.1.Important: create the full backup of IPNetwork Monitor program data on old (source) installation:

• run IPNetwork Monitor GUI client and stop monitoring service from Tools menu
• run Task manager and make sure there’s no fbserver.exe process running; if it is, terminate it
• copy the entire C:\ProgramData\IPNetwork Monitor folder elsewhere
• run IPNetwork Monitor GUI client and start monitoring service from Tools menu

1.2. Install exactly the same version and build of IPNetwork Monitor on target (new) system. To learn which version you are using, run IPNetwork Monitor GUI client on source system and proceed to “Help > About IPNetwork Monitor”. To find and download the corresponding IPNetwork Monitor installer, please visit IPNetwork Monitor archived versions page. 1.3. Run the IPNetwork Monitor client on your source (old) installation and select “Enter Your Registration Key…” from the Help menu. Click the “Unregister” button:

IPNetwork Monitor old installation will be converted to a 2-week trial. 1.4. Stop the IP Network monitoring service on old installation (“Tools > Stop monitoring service”).

Moving monitoring configuration and data

You might also want to move the monitoring database with all the monitoring settings, results, etc. Monitoring database files (NMS.FDB and all files with names starting with “nms.gbak”) are located at

"C:\ProgramData\IPNetwork Monitor\data"

if you use Windows Vista or above, or in

"C:\Documents and Settings\All Users\Application Data\IPNetwork Monitor\data"

if you use Windows 2003 or XP. Actual database location can be seen at any moment by running IPNetwork Monitor GUI client and selecting “Settings > System”. Value of “Path to nms.fdb file” is the actual database file location. To move the database, please do the following:

1. Stop IPNetwork monitoring service via GUI client’s “Tools > Stop monitoring service”.
2. Exit the IPNetwork Monitor GUI client via the “File > Exit” or by pressing Alt-X
3. Backup NMS.FDB and nms.gbak files located in the folders specified above.
4. Install IPNetwork Monitor on a new server.
5. Stop both IPNetwork Monitor service and IPNetwork Monitor GUI client on new server.
6. Copy the database files (NMS.FDB and nms.gbak*) you backed up at step 3 above to the corresponding directory on the new server.
7. Start IPNetwork Monitor GUI client on the new server, select “Help > Enter Your Registration Key…”, insert your license key and click “Register” (use the same license key you used on old installation).
8. Start IPNetwork Monitor service on new server.

Now IPNetwork Monitor should start monitoring from the new server using the same configuration as on the old server. 1.5.Important: if you loaded MIB files, used SSH keys and/or custom changes to Web interface pages on old installation, make sure you have copied them all to the same location on new server.

2. Transfer IPNetwork Monitor to another system on the newer version and build (upgrade)

2.1. Transfer IPNetwork Monitor to exactly the same version, following the steps mentioned in section 1. above. 2.2. Download the installer of the new version of IPNetwork Monitor (say, from Download page), run it and follow the on-screen instructions.

3. Transfer IPNetwork Monitor to another system on the lower version and build (downgrade)

IPNetwork Monitor doesn’t support downgrading; if you absolutely need to use the older IPNetwork Monitor version, you would need to install it from scratch and re-create the monitoring setup manually. Important: we strongly discourage you from using older (unsupported) IPNetwork Monitor version, as that can result in security and performance issues. Related Topics: How to prevent monitoring database corruption? Backup server monitoring