ESET Online Help

Search English
Select the category
Select the topic

Use the ESET PROTECT 9.0 All-in-one installer to upgrade

Use the ESET PROTECT 9.0 All-in-one installer to upgrade ESMC 7.x or an older ESET PROTECT version to the latest ESET PROTECT 9.0.

All-in-one installer is the recommended upgrade option if the existing installation was performed via the All-in-one installer (you have default installations of the MS SQL database and Apache Tomcat).

The ESET PROTECT 9.0 All-in-one installer installs Microsoft SQL Server Express 2019 by default.

oIf you use an older Windows edition (Server 2012 or SBS 2011), Microsoft SQL Server Express 2014 will be installed by default.

oThe installer automatically generates a random password for database authentication (stored in %PROGRAMDATA%\ESET\RemoteAdministrator\Server\EraServerApplicationData\Configuration\startupconfiguration.ini).


Microsoft SQL Server Express has a 10 GB size limit for each relational database. We do not recommend using Microsoft SQL Server Express:

In enterprise environments or large networks.

If you want to use ESET PROTECT with ESET Enterprise Inspector.



You can upgrade to ESET PROTECT 9.0 only from ESMC version 7.0 and later.

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 older unsupported database installed (MySQL 5.5 or MS 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.0.

ESET PROTECT Server component version 9.0 is not compatible with 32-bit machines (x86 architecture). Upgrading a 32-bit Server machine from version 7.0 to 9.0 will fail.

If you have already run the upgrade and your system is not working, reinstall manually all ESET PROTECT components to the original version.

Before the upgrade, migrate your current ESET PROTECT to a 64-bit machine, and after successful migration, you can run the upgrade task.

ESET PROTECT 9.0 uses LDAPS as the default protocol for Active Directory synchronization. If you upgraded from versions 7.0-7.1 on a Windows machine to ESET PROTECT 9.0 and used the Active Directory synchronization, synchronization tasks will fail in ESET PROTECT 9.0.

1.Run Setup.exe.

2.Select the language and click Next.

3.Select Upgrade all components and click Next.


4.Read the End-user license agreement, accept it and click Next.

5.In Components, review ESET PROTECT components that can be upgraded and click Next.


Apache Tomcat and Web Console upgrade limitations

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

Apache Tomcat upgrade will delete the era folder located in C:\Program Files\Apache Software Foundation\[ Tomcat folder ]\webapps\. If you use the era folder to store additional data, make sure to back up the data before upgrading.

If C:\Program Files\Apache Software Foundation\[ Tomcat folder ]\webapps\ contains additional data (other than the era and ROOT folders), the Apache Tomcat upgrade will not take place and only the Web Console will be upgraded.

The Web Console and Apache Tomcat upgrade clears the Offline help files. If you used Offline help with ESMC or an older ESET PROTECT version, re-create it for ESET PROTECT 9.0 after upgrading to ensure that you have the latest Offline help matching your ESET PROTECT version.


Apache HTTP Proxy upgrade limitations

The All-in-one installer overwrites httpd.conf and saves the original configuration to httpd.conf.old. To keep the custom Apache HTTP Proxy configuration, back up the configuration and reuse it.


6.Follow the Pre-installation checkup to make sure your system meets all prerequisites.

7.Click Upgrade to start the ESET PROTECT upgrade. The upgrade may take some time, depending on your system and network configuration.

8.When the upgrade completes, click Finish.

9.After upgrading ESET PROTECT, upgrade ESET Management Agent on managed computers using the Components Upgrade task. ESET PROTECT 9.0 supports the automatic upgrade of ESET Management Agent on managed computers.