Migrated Database - same 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 the same IP address as the old ESMC Server, and the database of the old ESMC Server will be imported to the new server machine prior to installation.

migration_of_clients_same_server

Click here to view the image larger

validation-status-icon-warning IMPORTANT

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.Export a server certificate from your current ESMC Server and save it to external storage.

Export all Certification Authority Certificates from your ESMC Server and save each CA certificate as a .der file.

Export Server Certificate from your ESMC Server to a .pfx file. The exported .pfx will include a private key as well.

2.Stop the ESMC Server service.

3.Export/Backup the ESMC Database.

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

validation-status-icon-warning IMPORTANT

Do not uninstall/decommission your old ESMC Server yet.

 

On your new ESMC Server:

validation-status-icon-warning IMPORTANT

Make sure the network configuration on your new ESMC Server (IP address, FQDN, Computer name, DNS SRV record) matches that of your old 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.

5.Import all CAs exported from your old ESMC Server. To do so, follow the instructions for importing a public key.

6.Change your ESMC Server certificate in Server settings to use the previous Server certificate from your old ESMC Server (exported in step 1.). Do not stop the ESMC Server service until step 7.

7.Restart the ESMC Server service, see our Knowledgebase article for details.

Client computers should now connect to your new ESMC Server using their original ESET Management Agent certificate, which is being authenticated by the imported CA from the old ESMC Server. If clients are not connecting, see Problems after upgrade/migration of ESMC Server.

details_hoverNOTE

When adding new client computers, use a new Certification Authority to sign the Agent certificates. This is done because an imported CA cannot be used to sign new peer certificates, it can only authenticate ESET Management Agents of client computers that were migrated.

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.