[KB7733] Manual component-based upgrade from ESET Remote Administrator 6.5 or ESET Security Management Center 7.x for Linux to ESET PROTECT 8

0
(0)

Details

  • The ESET Security Management Center (ESMC) is rebranded to ESET PROTECT in version 8
  • Direct upgrade is supported from ESET Remote Administrator 6.5 (ERA) and all versions of ESMC

Solution

  1. Upgrade Server component
  2. Upgrade ESET Management Agent
  3. Upgrade ERA Proxy (for Linux and ERA Virtual Appliance users)

I. Upgrade ERA / ESMC Server to ESET PROTECT

Only ERA 6.5 and later can upgrade to ESET PROTECT 8.1 directly.

  • If you use ERA 6.1 – 6.4, upgrade to ERA 6.5 and then continue with upgrade to ESET PROTECT.
Upgrade type Installed from Use when Link to instructions
Components Upgrade Client task ESMC Web Console
  • Recommended procedure
Run Command Client task Web Console
  • Use if Components Upgrade task fails
  • The installer is downloaded separately
Upgrade the components manually Linux terminal
  • For advanced users only
  • Requires knowledge of Linux terminal
Step by step guide (this article)
Database pull from an older ERA/ESMC VA VA terminal
  • If you have been using ESMC Virtual Appliance (for example VMWare or Virtual Box) you can perform database pull to to upgrade both, appliance operating system and ESMC/ERA

Upgrade ESMC Server, Tomcat and Web Console manually
Upgrade ESET PROTECT Server
ESET PROTECT Server does not support Linux 32-bit architecture

All steps in this article are to be run in the Linux terminal. If you use 32-bit Linux system, do not upgrade. ESET PROTECT Server does not support 32-bit architecture.

  1. Download the ESET PROTECT Server installer: 

    wget https://download.eset.com/com/eset/apps/business/era/server/linux/latest/server-linux-x86_64.sh
  2. Change the permission of file to executable: 

    sudo chmod +x server-linux-x86_64.sh
  3. Execute the installer file: 

    sudo ./server-linux-x86_64.sh
  4. During the installation, you will be asked if you accept the EULA and Privacy Policy and if you want to join the Product improvement program. Click Enter to confirm your answer.
If you receive an error related to insufficient rights when upgrading:

See the error log first:

cat /var/log/eset/RemoteAdministrator/EraServerInstaller.log

and complete the following steps:

  • Temporarily add the SUPER right for “era” user
  • Locate the actual user name and server connection in: /etc/opt/eset/RemoteAdministrator/Server/StartupConfiguration.ini
  • For a database server on localhost, use: 
    mysql -u root -p

    and type:

    grant SUPER on *.* to era@'localhost';

  • For a database server running on another machine, use: 
    mysql -u root -p --host=

    and type:

    grant SUPER on *.* to 'era'@'%';

    Make sure to remove the SUPER right after the upgrade is complete:

  • For a database server on localhost, use: 
    mysql -u root -p

    and type:

    revoke SUPER on *.* from 'era'@'localhost';

  • For a database server on another machine, use: 
    mysql -u root -p --host=

    and type:

    revoke SUPER on *.* from 'era'@'%';

  1. The installation will continue. When it is finished, follow the next steps below.
Upgrade Tomcat

ESET PROTECT 8.1 requires Tomcat 9 or later and 64-bit Java. Many Linux systems do a regular upgrade in the background, or there may not be a newer version available. Some Linux distributions use different versioning of Tomcat. Modify the addresses in the steps in part II and III according to your system.

  1. Before upgrading the Tomcat, backup your server.xml file, which stores the configuration for Tomcat. The file is located at /etc/tomcat/server.xml or a similar location. You can find it using the following command: 

    sudo find / -name server.xml

  2. To back up the server.xml file, copy it to your home folder. For example:

    sudo cp /etc/tomcat/server.xml /home/user/backup.server.xml
Manual Web Console upgrade
Tomcat installation

The Tomcat installation and service may have a different name and location on your system. Make sure to tailor the commands to your Linux environment.

  1. Download the ESET PROTECT Web Console: 
    wget https://download.eset.com/com/eset/apps/business/era/webconsole/latest/era.war
  2. Backup the Web Console configuration file, copy it to your home folder. For example: 

    cp /var/lib/tomcat/webapps/era/WEB-INF/classes/sk/eset/era/g2webconsole/server/modules/config/EraWebServerConfig.properties /home/user/backup.Era.WebServerConfig.properties
  3. Stop the Tomcat service: 

    sudo systemctl stop tomcat
  4. Remove the old Web Console files: 

    sudo rm -rf /var/lib/tomcat/webapps/era /var/lib/tomcat/webapps/era.war
  5. Copy the new era.war file: 

    sudo cp era.war /var/lib/tomcat/webapps/
  6. Start the Tomcat service: 

    sudo systemctl start tomcat
  7. Wait until the era.war is extracted by Tomcat. A new folder era appears in the /var/lib/tomcat/webapps/ folder.
  8. Restore the backed Web Console configuration file: 

    sudo cp /home/user/backup.Era.WebServerConfig.properties /var/lib/tomcat7/webapps/era/WEB-INF/classes/sk/eset/era/g2webconsole/server/modules/config/EraWebServerConfig.properties
  9. Restart the Tomcat service to apply the restored configuration.
  10. You can now log in the Web Console.
RD Sensor upgrade

To upgrade RD Sensor, run the installer as follows:

sudo ./rdsensor-linx-x86_64.sh --skip-license​

The --skip-license parameter skips the display of the ESET End-user license agreement (EULA). If you wish to view the EULA before agreeing to it, do not use this parameter when installing RD Sensor.

II. Upgrade ESET Management Agent

Beginning with version 7, the ERA Agent is named the ESET Management Agent.

Before you begin
  • Always upgrade the ERA/ESMC Server machine first.
  • The ESET Management Agent (v7 and v8) cannot connect to the ERA 6.x Server.
  • Do not upgrade the ERA Agents which are connecting via ERA Proxy before a proper proxy solution is set up.
    • ERA Version 6.5 Agent can connect to ESET PROTECT Server.
    • ESET Management Agent (version 8) cannot connect via ERA Proxy.
    • ESET Management Agent (version 8) cannot connect to ERA 6.x Server.
There are different ways how to upgrade your ERA 6.5 Agent to the latest ESET Management Agent.
Upgrade type Installed from Use when Link to documentation
Components Upgrade Client task Web Console
  • Recommended procedure
Run Command Client task Web Console
  • Use if Components Upgrade task fails
  • The installer is downloaded for each client separately
Step by step guides (Knowledgebase articles):
Manual Agent installation Linux terminal
  • For advanced users only
  • Requires knowledge of Linux terminal
Step by step guide (this article)
Manual Agent installation

III. Upgrade ERA Proxy (for Linux and ERA Virtual Appliance users)

Visit this Knowledgebase article on Migration of ERA 6 Proxy to Apache HTTP Proxy (Linux and Virtual Appliance).

Before you begin
  • Always upgrade the ESET PROTECT Server machine first.
  • The ESET Management Agent (8.x) cannot connect to the ERA 6.x Server.
  • Do not upgrade the ERA Agents which are connecting via ERA Proxy before a proper proxy solution is set up. The ESET Management Agent (8.x) cannot connect to the ESET PROTECT Server via ERA Proxy.
Languages
Last Updated: Jun 23, 2021

Related articles:

Source : Official ESET Brand
Editor by : BEST Antivirus KBS Team

How useful was this post?

Click on a star to rate it!

Average rating 0 / 5. Vote count: 0

No votes so far! Be the first to rate this post.

(Visited 50 times, 1 visits today)
Tagged: