Windows users: Click here for instructions to upgrade ESET Remote Administrator 6.x to the latest version.

ERA Virtual Appliance: Click here for instructions to upgrade your existiing ERA VA to the latest version,or to perform a migration ERA VA.
I. Manual upgrade for Linux ESET Remote Administrator Server using MySQL (applies to ERA Server Appliance)

II. Upgrade ERA Agent

III. Upgrade ERA Proxy (applies to Linux and ERA virtual appliance)

I. Manual upgrade for Linux ESET Remote Administrator Server using MySQL (applies to ERA Server Appliance)

1. Download the ERA component installers including:
   • ESET Remote Administrator Server (Server)
   • ESET Remote Administrator Agent (Agent)
   • Rogue Detection Sensor (RDSensor)
   • Web Console (era.war)
   • Other installers as needed
2. Stop the Apache Tomcat service. For example:

   service tomcat7 stop (CentOS)

3. Back up the following folder and all of its contents:

   /var/lib/tomcat7/webapps/era

4. Make a copy of the following configuration file:

   /var/lib/tomcat7/webapps/era/WEB-INF/classes/sk/eset/era/g2webconsole/server/modules/config/EraWebServerConfig.properties

5. Delete the existing Web Console folder and all of its contents:

   /var/lib/tomcat7/webapps/era  

6. Delete the existing era.war file if it is on the system.
7. Unzip the new era.war file (that was downloaded in step 1) to the following folder:

   /var/lib/tomcat7/webapps/era/
   Examples (use yum or apt-get to install “unzip” if command is not available):

   mkdir /var/lib/tomcat7/webapps/era/
unzip era.war -d /var/lib/tomcat7/webapps/era/
(jar xvf era.war)

8. Move the EraWebServerConfig.properties configuration file that you copied in step 4 to the following directory:

   /var/lib/tomcat7/webapps/era/WEB-INF/classes/sk/eset/era/g2webconsole/server/modules/config/EraWebServerConfig.properties 

9. Run the ERA Server installer:

   sudo ./server-linux-x86_64.sh --skip-licenseThe --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 ERA Server.

   For ERA Server Appliance

   The DB root password is identical to the ERA password in ERA Web Console.

   If you receive an error related to insufficient rights when upgrading (Server bug 6.1.GA), go to the log:

   /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

Use the following scripts (substitute the actual user name for “era”):

• For a database server on localhost, usemysql -u root -p

  and type:grant SUPER on *.* to era@'localhost';

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

  and type:grant SUPER on *.* to 'era'@'%';


Complete the upgrade and make sure to remove the SUPER right after the upgrade is complete:

• For a database server on localhost, usemysql -u root -p

  and type:revoke SUPER on *.* from 'era'@'localhost';

• For a database server on another machine, usemysql -u root -p --host=

  and type:revoke SUPER on *.* from 'era'@'%';

10. Start the Apache Tomcat service. Typically, it takes some time for the Apache to start and for the ERA Web Console to become functional.
11. Log into your ERA Web Console at the following URL: https:///era

    for example https://192.168.10.12:8443/era

12. To upgrade RD Sensor, run the installer as follows: sudo ./rdsensor-linx-x86_64.sh --skip-licenseThe --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 ERA Agent

It is recommended to use ERA Administrator’s account for the following steps.

When upgrading the Agent, you have two options:

1. Run the Agent installer from the shell locally on each client computer.
2. Create a Run Command Client task from the ERA Web Console (steps included below).

ERA Agent upgrade using the Run Command Client task

1. Create new Dynamic groups which identify the operating system on the client machine—one group for 32-bit and other for 64-bit:
   1. Create a Dynamic group template for 32-bit systems with following parameters:
      • Operation “AND”
      • Add rule OS edition > OS platform = (equal) 32-bit
      • Add rule OS edition > OS type contains Linux
   2. Create a Dynamic group template for 64-bit systems with following parameters:
      • Operation “AND”
      • Add rule OS edition > OS platform = (equal) 64-bit
      • Add rule OS edition > OS type contains Linux
   3. Create a Dynamic group based on the 32-bit template you’ve just created.
   4. Create Dynamic group based on the 64-bit template you’ve just created.
2.  Create a new Client task for 32-bit systems:
   1. In the Basic section, select Run Command from the Task drop down menu.
   2. In the Targets section, select the Dynamic group you created for 32-bit operating systems.
   3. In the Settings section, enter one of the following commands into the Command line to run field (replace SERVER with actual server name and share with share name):
      HTTP Local Share command: wget -q http://SERVER/share/agent-linux-i386.sh -O /tmp/agent-linux-i386.sh && chmod a+x /tmp/agent-linux-i386.sh && /tmp/agent-linux-i386.sh --skip-license &> /tmp/era-agent-upgrade.txt

      Request from online command: wget -q http://download.eset.com/download/ra/v6/standalone-installers/agent/agent-linux-i386.sh -O /tmp/agent-linux-i386.sh && chmod a+x /tmp/agent-linux-i386.sh && /tmp/agent-linux-i386.sh --skip-license &> /tmp/era-agent-upgrade.txt

3. Create a new Client task for 64-bit systems:
   1. In the Basic section, select Run Command from the Task drop down menu.
   2. In the Targets section, select Dynamic group you created for 64-bit operating systems.
   3. In the Settings section, enter one of the following commands into the Command line to run field (replace server with your actual server name and readonlyshare with share name):HTTP Local Share command: wget -q http://SERVER/share/agent-linux-x86_64.sh -O /tmp/agent-linux-x86_64.sh && chmod a+x /tmp/agent-linux-x86_64.sh && /tmp/agent-linux-x86_64.sh --skip-license &> /tmp/era-agent-upgrade.txt

      Request from online command: wget -q http://download.eset.com/download/ra/v6/standalone-installers/agent/agent-linux-x86_64.sh -O /tmp/agent-linux-x86_64.sh && chmod a+x /tmp/agent-linux-x86_64.sh && /tmp/agent-linux-x86_64.sh --skip-license &> /tmp/era-agent-upgrade.txt

4. Monitor the Computer details section in Installed Applications. It may happen that two Agents (one running the old version, the other running a more recent version) are running on a client machine at the same time. This is only temporary. You can also monitor the Outdated applications report in Computers section (use drill-down to show particular computers). Note that data in this report are updated once per hour.

III. Upgrade ERA Proxy (for Linux and ERA virtual appliance users)

Enter the commands shown below if the Client task fails to update these components:

1. Download ERA Proxy installer (make sure the installer version is correct):
   wget https://download.eset.com/com/eset/apps/business/era/proxy/latest/proxy-linux-x86_64.sh
2. Navigate to the folder where you downloaded ERA Server and make the installation package executable:
   chmod +x proxy-linux-x86_64.sh
3. Run the following command to install the latest ERA Proxy:
   ./proxy-linux-x86_64.sh
4. Reboot your computer.