ESET PROTECT Components Upgrade

The ESET PROTECT Components Upgrade task is used to upgrade ESET PROTECT components (ESET Management Agent, ESET PROTECT Server, Web Console, and MDM, but not Apache Tomcat and Apache HTTP Proxy). The upgrade task can be executed only on a machine with ESET Management Agent installed. The Agent is also required on an ESET PROTECT Server.

important

Important

You can upgrade to ESET PROTECT 8.0 only from ERA version 6.5 and later. See the Installation guide for detailed instructions.

When upgrading from ERA 6.x, make sure to upgrade to the ESET PROTECT Server before upgrading the Agents. ESET Management Agents use a new communication protocol and are not able to connect to ERA 6.x Server.

To prevent installation failure, ESET PROTECT performs the following checks before installing or upgrading ESET products:

if the repository is accessible

if there is enough (1 GB) free space on the client machine (not available for Linux)

note

Note

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

See also other ways how to upgrade ESET PROTECT to the latest version.

To create the task, click Tasks > New > add_new_defaultClient Task or click the desired client device in Computers and select New Task.

Basic

In the Basic section, enter basic information about the task, such as a Name and Description (optional). Click Select tags to assign tags.
In the Task drop-down menu, select the task type you want to create and configure. If you have selected a specific task type before creating a new task, Task is pre-selected based on your previous choice. Task (see the list of all Tasks) defines the settings and the behavior for the task.

Settings

Select the check box I accept the terms of the application End User License Agreement and acknowledge the Privacy Policy. See EULA for more information.

Reference ESET PROTECT Server - Select ESET PROTECT Server version from the list. All ESET PROTECT components will be upgraded to versions compatible with the selected server.

Select the check box next to Automatically reboot when needed to force an automatic reboot of the client computer after installation. Alternatively, you can leave this option deselected and manually restart the client computer(s).

Summary

Review the summary of configured settings and click Finish. The Client Task is now created and a pop-up window will open. We recommend that you click Create Trigger to specify when this Client Task should be executed and on what Targets. If you click Close, you can create a Trigger later: click the Client Task instance and select Run on from the drop-down menu.

client_task_finish

In Tasks you can see the progress indicator bar, status icon, and details for each created task.