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. Ensure you review the directions in detail before upgrading.
|
•If the components upgrade fails on a machine running the ESET PROTECT Server or Web Console, you might not be able to log in to the Web Console remotely. We recommend that you ensure physical access to the server machine before performing this upgrade. If physical access to the machine is not possible, ensure you can access it with administrative privileges using a remote desktop. •If you have installed ESET PROTECT database with a dedicated database user with Windows authentication, the ESET PROTECT Components Upgrade task cannot upgrade the ESET PROTECT Server in the future. |
Are you upgrading from an earlier ESET PROTECT Virtual Appliance?
The ESET PROTECT Server instance is installed on a failover cluster?
|
You can upgrade to ESET PROTECT On-Prem 11.1 from ESET PROTECT On-Prem 9.0 and later. A direct upgrade from the End of Life versions 7.2–8.x has not been tested and is not supported. ESET PROTECT On-Prem automatically notifies you when a new version of the ESET PROTECT Server is available. Back up the following data before the upgrade: •Your ESET PROTECT database. oIf 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. oTo back up your Virtual Appliance, create a snapshot or clone the virtual machine. •All certificates (Certification Authority, Server Certificate and Agent Certificate): oExport your Certification Authority Certificates from an old ESET PROTECT Server to a .der file and save them to external storage. oExport 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. Ensure you have a supported operating system before upgrading to ESET PROTECT On-Prem 11.1. Upgrade ESET security products by running the Software Install task using the latest installer package to install the latest version over your existing product. |
|
ESET PROTECT Mobile Device Management/Connector (MDM/MDC) component (on-premises only) reached End of Life in January 2024. ESET PROTECT On-Prem versions 11.1 and later do not support mobile device management. |
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 ESET Bridge 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 from the cache.
3.After the computers with upgraded ESET Management Agent successfully connect 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 On-Prem supports the automatic upgrade of ESET Management Agents on managed computers. |
Components upgraded automatically:
•ESET PROTECT Server
•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 is 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. |
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 an earlier ESET PROTECT On-Prem version, 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 On-Prem uses third-party components that require a manual upgrade.
In the ESET PROTECT Web Console, click Quick Links > Server Components to see third-party components with a later version available.
|
•We recommend installing the latest version of third-party components. The latest available version may vary based on the operating system running the ESET PROTECT Server. •ESET PROTECT Virtual Appliance does not report available upgrades for third-party components. |
ESET PROTECT Web Console recommends an upgrade for versions earlier than those listed below:
Third-party component: |
Version: |
Notes: |
Upgrade instructions |
|||
|---|---|---|---|---|---|---|
Microsoft SQL Server |
2019 (build 15.0.4365.2) |
Determine your version and edition of SQL Server Database Engine and install the latest cumulative update. |
||||
MySQL |
8.0.0.0 |
Click Help > About in the ESET PROTECT Web Console to see the installed database version. |
||||
Operating system |
Windows Server 2016 |
ESET PROTECT On-Prem does not report available updates for Linux. |
||||
Apache Tomcat |
9.0.89 |
Determine the installed Apache Tomcat version: •Windows—Navigate to C:\Program Files\Apache Software Foundation\[ Tomcat folder ]\ and open the RELEASE-NOTES file in a text editor to check the version number. •Linux—Run the Terminal command: tomcat version |
||||
Java |
17.0 |
Determine the installed Java version: •Windows—Open the Command Prompt and run: java -version •Linux—Run the Terminal command: java -version |
||||
Apache HTTP Proxy |
- |
|
|
ESET PROTECT Mobile Device Management/Connector (MDM/MDC) component (on-premises only) reached End of Life in January 2024. ESET PROTECT On-Prem versions 11.1 and later do not support mobile device management. |
Troubleshooting
•Verify if you can access the ESET PROTECT On-Prem repository from an upgraded computer.
•Re-running the ESET PROTECT Components Upgrade task will not work if at least one component is 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 upgrade failure, upgrade components manually. See our instructions for Windows or Linux.
•For more suggestions to resolve upgrade issues, see general troubleshooting information.