Migrated Database - different IP address

The objective of this procedure is to install an entirely new instance of ESMC Server and keep your existing ESMC database, including existing client computers. The new ESMC Server will have a different IP address from the old ESMC Server, and the database of the old ESMC Server will be imported to the new server machine prior to installation.



Migrating databases is only supported between identical database types (from MySQL to MySQL or from MSSQL to MSSQL).

When migrating a database, you must migrate between instances of the same ESET Security Management Center version. See our Knowledgebase article for instructions to determine the versions of your ESMC components. After completing database migration, you can perform an upgrade, if necessary, to get the latest version of ESET Security Management Center.


On your current (old) ESMC Server:

1.Generate a new ESMC Server certificate (with connection information for the new ESMC Server). Leave the default value (an asterisk) in the Host field to allow for distribution of this certificate with no association to a specific DNS name or IP address.

2.Create a policy to define a new ESMC Server IP address and assign it to all computers. Wait for the policy to be distributed to all client computers (computers will stop reporting in as they receive the new server information).

3.Stop the ESMC Server service.

4.Export/Backup the ESMC Database.

5.Turn off the current ESMC Server machine (optional).



Do not uninstall/decommission your old ESMC Server yet.


On your new ESMC Server:

1.Install/Launch a supported ESMC database.

2.Import/Restore the ESMC database from your old ESMC Server.

3.Install ESMC Server/MDM using the All-in-one package installer (Windows) or choose another installation method (Windows manual installation, Linux or Virtual Appliance). Specify your database connection settings during installation of ESMC Server.

4.Connect to ESMC Web Console.

Client computers should now connect to your new ESMC Server using their original ESET Management Agent certificate. If clients are not connecting, see Problems after upgrade/migration of ESMC Server.

Old ESMC Server/MDM uninstallation:

Once you have everything running correctly on your new ESMC Server, carefully decommission your old ESMC Server/MDM using our step-by-step instructions.