Clean Installation - different IP address

The objective of this procedure is to install an entirely new instance of ESMC Server that does not use the previous database, but retains records for client computers. The new ESMC Server will have a different IP address/Hostname, but will not use the database from the old ESMC Server.


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.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.

3.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).

4.Stop the ESMC Server service.

5.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:

1.Install ESMC Server/MDM using the All-in-one package installer (Windows) or choose another installation method (Windows manual installation, Linux or Virtual Appliance).

2.Connect to ESMC Web Console.

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

4.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 6.

5.Import all required ESET licenses to ESMC.

6.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.


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.