Tools

Migrating Dameware Central Server to a New Server

This article provides steps for migrating the Dameware Central Server to a new Server.

First published date

10/7/2018 1:56 AM

Last published date

9/10/2026 3:19 PM

Overview

Previously, we used the Dameware Central Server database file (DamewareDB.sdf) for migration. 
However, this is no longer possible with the latest version of Dameware Central Server, especially when there are version differences between the old and new servers, because the database changes with each version.
To migrate the Dameware Central Server, it is best to identify the versions from which and to which the migration will occur.
When migrating from one Central Server to another host, both servers should ideally be running the same version.
For Dameware Central Server migrations from version 12.3.0 or earlier to a later version, the best approach is to perform a clean, manual migration.
For migrations from Dameware Central Server version 12.3.1 or later to the latest version, database migration is possible.
However, if the database migration fails, it is best to perform a clean, manual migration, as database files are fragile and can become corrupted during the process.

Product section

Dameware Remote Support & Mini Remote Control

Cause

NA

Resolution

Clean Migration - Dameware Central Server version 12.3.0 and below migrating to a later version

Please follow this article:
How to migrate Dameware Central Server by exporting and importing server data

Database Migration - Dameware Central Server version 12.3.1 or above migrating to a later version.

Below is an example of a database migration when migrating from Dameware version 2026.3 to the same Version 2026.3

  1. On the new server, complete the installation of the Dameware Server version 2026.3 and finish the Dameware Configuration Wizard Window.
  2. Open Windows Services.msc and stop the Dameware Server on both the old and new servers.
  3. On the server, go to the Dameware Central Server installation path, default is C:\Program Files (x86)\SolarWinds\Dameware Central Server, and create a backup of DameWareDB.sqlite and save it to a different location or rename it DameWareDB.sqlite.original.
  4. On the old server, copy the DameWareDB.sqlite located in the Dameware Central Server installation path (default: C:\Program Files (x86)\SolarWinds\Dameware Central Server), and save it somewhere on the new server first. Copy it to the Dameware Central Server installation path; the default is C:\Program Files (x86)\SolarWinds\Dameware Central Server.
  5. Start the service on the new Server, and log in using the admin account you use on the old server.
    1. If the admin account is not working, you can reset: Reset the default admin account password of the Dameware Administratiton Console 

A few more steps to complete the migration:

  • Test connectivity and make sure no issues are encountered before decommissioning your old server.
  • Direct all of the DRS and DMRC client machines to the Host Name /IP Address of the new Server by updating the Dameware Central Server IP/Hostname as shown below:
    • dameware client login advance settings.png
  • The following prompt is expected as the new server has a new certificate unknown to the client. Once accepted, it should work as expected:
    • Server Certificate error 1.png
  • Migrate the Dameware Server License by deactivating the old server's license in SolarWinds License Manager.
    • Deactivate the Old Server's License:
      • Open SolarWinds License Manager from the Windows Start > SolarWinds License Manager > Run "SolarWinds License Manager" as an admin
        • If there is no SolarWinds License Manager yet, Go to Start > SolarWinds > Run "Install (Remove) License Manager" as an admin
      • Select DRSC or DMRC and click Deactivate
    • Activate your New Server using your License Key
      • Windows Start > SolarWinds > Run "License Activation(2nd one)" as an admin
      • Activate License Online if the machines have internet, or offline if none.
  • If the Server has no internet connection, refer to these articles for Offline Deactivation and Activation: