ESET Online Help

Search English
Select the category
Select the topic

ESET PROTECT Components Upgrade task

Recommendations before upgrading

We recommend using the ESET PROTECT Components Upgrade task in the ESET PROTECT Web Console to upgrade your ESET PROTECT infrastructure. Carefully review the directions here before upgrading.


If the components upgrade fails on a machine running the ESET PROTECT Server or Web Console, you may not be able to log into the Web Console remotely. We recommend that you configure physical access to the server machine before performing this upgrade. If you cannot arrange for physical access to the machine, make sure you can log onto it with administrative privileges using a remote desktop. We recommend that you back up your ESET PROTECT Server and Mobile Device Connector databases before performing this operation. To back up your Virtual Appliance, create a snapshot or clone your virtual machine.

Are you upgrading from ESMC Virtual Appliance?

arrow_down_business The ESET PROTECT Server instance is installed on a failover cluster?

arrow_down_business Important instructions before upgrading Apache HTTP Proxy on Microsoft Windows

arrow_down_business Important instructions before upgrading Apache HTTP Proxy on Virtual Appliance



You can upgrade to ESET PROTECT 9.1 only from ESMC version 7.2 and later.

ESET PROTECT 9 automatically notifies you when a new version of the ESET PROTECT Server is available.

Back up the following data before running the upgrade:

All certificates (Certificate Authority, Server Certificate and Agent Certificate)

Export your Certification Authority Certificates from an old ESET PROTECT Server to a .der file and save them to external storage.

Export your Peer Certificates (for ESET Management Agent, ESET PROTECT Server) and private key .pfx file from an old ESET PROTECT Server and save them to external storage.

Your ESMC/ESET PROTECT database. If you have an earlier unsupported database installed (MySQL 5.5 or Microsoft SQL 2008/2012), upgrade your database to a compatible database version before upgrading the ESET PROTECT Server.


Make sure that you have a supported operating system before upgrading to ESET PROTECT 9.1.

To upgrade ESET security products, run the Software Install task using the latest installer package to install the latest version over your existing product.

Recommended upgrade procedure

1.Upgrade the ESET PROTECT Server - Select only the machine with the ESET PROTECT Server as the target for the ESET PROTECT Components Upgrade task.

2.Select some client computers (as a test sample - at least one client from each operating system and bitness) and run the ESET PROTECT Components Upgrade task on them.

We recommend that you use Apache HTTP Proxy (or any other transparent web proxy with caching enabled) to limit the network load. The test client machines will trigger the download/caching of the installers. When the task runs again, the installers will be distributed to client computers directly from the cache.

3.After the computers with upgraded ESET Management Agent are successfully connecting to the ESET PROTECT Server, proceed with upgrading the rest of the clients.


To upgrade ESET Management Agents on all managed computers in the network, select the Static Group All as the target for the ESET PROTECT Components Upgrade task. The task will skip computers that already run the latest ESET Management Agent.

ESET PROTECT 9.1 supports the automatic upgrade of ESET Management Agents on managed computers.

Components upgraded automatically:


ESET Management Agent

ESET PROTECT Web Console - only applies when Apache Tomcat was installed to its default installation folder in both Windows and Linux distributions, including ESET PROTECT Virtual Appliance (for example: /var/lib/tomcat8/webapps/, /var/lib/tomcat7/webapps/, /var/lib/tomcat/webapps/).


Web Console upgrade limitations

oApache Tomcat is not upgraded during the ESET PROTECT Web Console upgrade via the Components Upgrade task.

oESET PROTECT Web Console upgrade does not work if Apache Tomcat was installed in a custom location.

oIf a custom version of Apache Tomcat is installed (manual installation of the Tomcat service), the future ESET PROTECT Web Console upgrade via the All-in-one installer or Components Upgrade Task is not supported.

ESET PROTECT Mobile Device Connector.

Components that require a manual upgrade:

ESET components

ESET Rogue Detection Sensor - Use the Software Install task for the upgrade. Alternatively, install the latest version over an earlier version (follow the installation instructions for Windows or Linux). If you installed RD Sensor with ESMC 7.2 and later, you do not need to upgrade it, as there are no new RD Sensor releases.

Third-party components

In addition to ESET components, ESET PROTECT uses third-party components that may become outdated and require a manual update.

In the ESET PROTECT Web Console, click Quick Links > Outdated Components to see the outdated third-party components.

ESET PROTECT Virtual Appliance does not report outdated third-party components.

ESET PROTECT reports versions earlier than those listed below as outdated:

Third-party component:


Microsoft SQL Server

2019 (build 15.0.4223.0)1


Operating system2

Windows Server 2016

Apache Tomcat




1 Determine your version and edition of SQL Server Database Engine and install the latest cumulative update.

2 ESET PROTECT does not report an outdated Linux operating system.

Follow the update instructions for third-party components:

Database server

Operating system

Apache Tomcat

Java Runtime Environment

Apache HTTP Proxy


Verify whether you can access the ESET PROTECT repository from an upgraded computer.

Re-running the ESET PROTECT Components Upgrade task will not work if there is at least one component already upgraded to the later version.

If the ESET PROTECT Web Console does not load or you see an error during the login, see the Web Console troubleshooting.

If there is no clear reason for the failure, you can upgrade components manually. See our instructions for Windows or Linux.

For more suggestions to resolve upgrade issues, see general troubleshooting information.