Component upgrade task

Recommendations:

We recommend using the Component Upgrade task available in the ERA Web Console to upgrade your ERA infrastructure. The following example shows you how to set up the Remote Administrator Component Upgrade task to upgrade from ERA version 6.1.x or later to ERA version 6.5.

validation-status-icon-warning IMPORTANT: You must back up

all certificates (Certificate Authority, Server Certificate, Proxy and Agent Certificate)

your ERA database

before you start the upgrade task.

Complete the following steps to back up your certificates:

1.Export your Certification Authority Certificates from your existing ERA Server to a .der file and save it to external storage.

2.Export your Peer Certificates (for ERA Agent, ERA Server, ERA Proxy) and the private key .pfx file from your existing ERA Server and save it to external storage.

3.Update your ERA server first.

4.Select few client machines to use as a test for the update and run the task on them (use at least one client from each system / bit category).

It is recommended to use Apache HTTP Proxy (or another transparent web proxy with enabled caching) in order to limit network load. The test client machines will trigger download / caching of the installers. When the task is run next time, installers will be distributed to client computers directly from cache.

5.After the test update completes successfully, run the update task on the rest of the client machines. To re-run an existing task on a static group, follow these steps:

a.Navigate to Computers menu.

b.Click the gear icon  next to name of the static group where you want to run the task.

c.Click Run task.

d.Select the task you want to run (set up a filter to Components upgrade task).

e.Set the trigger.

f.Click Finish to save the trigger.

Alternatively, target the group All in this step. Computers that were already upgraded before will not be upgraded again.

List of upgraded components:

ERA Server

ERA Agent (task will update all computers in the network with ERA Agents installed if they are selected as targets for the task)

ERA Proxy

ERA Web Console (only applies when installed using the ERA All-in-one installer or ERA Virtual Appliance and any Linux distribution [provided in the installation folder: /var/lib/tomcat8/webapps/, /var/lib/tomcat7/webapps/, /var/lib/tomcat/webapps/])

ERA Mobile Device Connector (from version 6.2.11.0 to ERA version 6.5). It is recommended to upgrade MDM from version 6.1 to version 6.4 and then you can upgrade to version 6.5.

The following components must be upgraded manually:

Apache Tomcat (we strongly recommend that you keep Apache Tomcat up-to-date, see Upgrading Apache Tomcat)

Apache HTTP Proxy (can be achieved using All-in-one installer, see Upgrading Apache HTTP Proxy)

ERA Rogue Detection Sensor

validation-status-icon-warning IMPORTANT: To upgrade ESET Security Products use the Software Install task. Run the task using the latest installer package to install the latest version over your existing solution.

Before upgrading:

validation-status-icon-error If the component upgrade fails on a machine running an ERA Server or Web Console, you may not be able to log into the Web Console remotely. It is recommend to configure physical access to the server machine before performing this upgrade. If you cannot arrange for physical access to the machine, make sure you can log onto it with administrative privileges using a remote desktop. It is recommended to back up your ERA Server and Mobile Device Connector databases before performing this operation. To back up your Virtual Appliance, create a snapshot or clone your virtual machine.

hmtoggle_plus0Upgrading from ERA version 6.1.x?
hmtoggle_plus0ERA Server instance is installed on a failover cluster?
hmtoggle_plus0ERA Agent installed on Linux clients running with systemd in your infrastructure?
hmtoggle_plus0Important instructions before upgrading Apache HTTP Proxy on Microsoft Windows
hmtoggle_plus0Important instructions before upgrading Apache HTTP Proxy on Virtual Appliance

 

See the online help topic for the Remote Administrator Components Upgrade task procedure. For another how to upgrade ESET Remote Administrator to the latest version (6.x) guide, see our Knowledgebase article.

 

Troubleshooting:

Verify whether you can access the ERA repository from an upgraded computer.

Re-running the Remote Administrator Components Upgrade task will not work if there is at least one component already upgraded to a newer version.

If there is no clear reason for the failure, you can upgrade components manually. See our instructions for Windows or Linux.

On Linux machines utilizing systemd as a service manager, this task might not finish successfully. Linux distributions with SysV init scripts or upstart are unaffected.

See general troubleshooting information for more suggestions to resolve upgrade issues.