ESMC VA upgrade/migration

For upgrading or migrating your VA, you can perform the following:

Upgrade - install a newer version of ESMC components.

Migration - move the ESMC Virtual Appliance to another instance of the same version.

Migration & upgrade - move the ESMC Virtual Appliance to another instance of the higher version.

Before upgrade/migration

Always backup your database and export Certification Authority and Peer Certificates from your old ERA/ESMC VA before migration or upgrade of the ESMC Server.

If you are upgrading/migrating from ERA 6.x, be aware of the following:

ERA 6.x Proxy component is deprecated. Click here to read more about the HTTP Proxy new solution.

NTLM authentication is deprecated, ESMC 7 uses Kerberos instead. You have to use the Linux login format, if you are logging in to domain on ESMC VA. This also applies to synchronization tasks.

Database pull versus the Components Upgrade

There are two principal ways of upgrading your VA:

Using the database pull - upgrades your whole Appliance (the underlying operating system), not just the ESMC Server. The process is more complicated and requires having two concurrent appliances during the transition period. The database pull is recommended for major version upgrades or as a troubleshooting method.

Upgrading via Components Upgrade task in the Web Console - the process is more simple and does not require access to the appliance, only to the Web Console. It is recommended for minor and hot fix upgrades.

Migration and upgrade process (recommended way to upgrade)

Use the following instructions to migrate and upgrade your ESMC VA.

1.Download the latest version of esmc_appliance.ova (or esmc_appliance.vhd.zip if you use Microsoft Hyper -V).

2.Deploy new ESMC VA. See ESMC Appliance deployment process for instructions. Do not configure the new ESMC VA via its web interface yet.

3.Pull database from your old ESMC VA, see Pull database from other server for a complete step-by-step guide.

important

Important

Do not uninstall/decommission your old ESMC Server yet.

4.Configure ESMC Virtual Appliance via its web interface.

5.Verify that your new ESMC VA behaves the same way as the previous one:

oIf the new ESMC VA has a different IP address:

a)Create a policy on your old ESMC VA to set a new ESMC Server IP address and assign it to all computers.

b)Wait for the policy to distribute to all ESET Management Agents.

c)Make sure all computers are connecting to the new ESMC VA.

d)Turn off and decommission the old ESMC VA.

important

Important

We strongly recommend that you do not uninstall the old ESMC VA Server using an uninstallation script. This will dissociate (remove) all licenses from the new ESMC VA Server database as well. To prevent this behavior, delete the old ESMC VA Server database (DROP DATABASE) before the uninstallation.

oIf the new ESMC VA has the same IP address:

important

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. You can also use the hostname by changing the DNS record to point to the new server.

a)Turn off the old ESMC VA.

b)Turn on the new ESMC VA.

c)Make sure all computers are connecting to the new ESMC VA.

d)Decommission the old ESMC VA.

important

Important

We strongly recommend that you do not uninstall the old ESMC VA Server using an uninstallation script. This will dissociate (remove) all licenses from the new ESMC VA Server database as well. To prevent this behavior, delete the old ESMC VA Server database (DROP DATABASE) before the uninstallation.

6.Upgrade a ESET Management Agents sample group using a Components Upgrade task.

7.If the upgrade of the sample is successful and Agents are still connecting, continue with the rest of the Agents.

Upgrade process (an alternative way to upgrade)

important

Important

Upgrading ERA or older ESMC to the latest ESMC on the same VA does not upgrade other VA software (operating system, packages needed for proper functioning of ESMC Server). We recommend that you migrate the server after the pure upgrade.

Upgrade the VA using a Components Upgrade task:

1.Upgrade the ESMC Server first.

2.Upgrade a ESET Management Agents sample group.

3.If the upgrade of the sample is successful and Agents are still connecting, continue with the rest of the Agents.