How do I upgrade to the latest version of ESET Remote Administrator 6.x?

Проблема

  • Upgrade ESET Remote Administrator (ERA) 6.x to the latest version
     
  • Run the Component Upgrade task
     
  • Upgrade individual ERA components (Agent, Server, Proxy) to the latest version
     
  • Resolve CReplectionModule errors by upgrading to the latest version

Решение

 Linux usersUpgrade ERA to the latest version on a Linux Operating System.

Prerequisites

Perform a full backup of the ESET Remote Administrator before proceeding

  • Database: Please see specific instructions from the software publisher on how to perform a back up operation for your supported database type and version.
     
  • Configuration: Make a copy of the file Startupconfiguration.ini located at C:\ProgramData\ESET\RemoteAdministrator\Server\EraServerApplicationData\ by default.
     
  • Mobile Device Connector: If this component is used, make a copy of the file Startupconfiguration.ini located at C:\ProgramData\ESET\RemoteAdministrator\MDMCore\Configuration.

 

  • You can only use the component-based upgrade task from the following versions of ESET Remote Administrator:

    • 6.2.171.0
    • 6.1.444.0
    • 6.1.365.0
    • 6.1.265.0

If you are not running one of the versions listed above (or having issues using the component-based upgrade task), perform the steps in the section Perform a manual component-based upgrade of ERA Server and Web Console.

  • ERA 6.1 and ERA 6.2 Component Upgrade Task is not supported on certain Linux operating systems.
    • ERA running on SLES (SUSE Linux Enterprise Server) does not support Component Upgrade Task when upgrading from ERA 6.1 or from ERA 6.2. The latest ERA versions (6.3.x and later) support Component Upgrade Task on SLES.

Skip to manual component-based upgrade instructions:

Perform the component upgrade from ERA Web Console

Components and policies

These steps will upgrade both the ERA components (ERA Server, ERA Console) and the ESET Remote Administrator Agent(s) (ERA Agent). When upgrading from 6.1.28 to the latest version, your policies will be preserved.

Special characters may cause upgrade to fail

If you have met the requirements for upgrading and your upgrade to the latest version of ESET Remote Administrator (ERA) fails, it could be due to the use of special characters in your ERA password. To resolve this issue, change your ERA password and attempt the upgrade again.

  1. Open ESET Remote Administrator Web Console (ERA Web Console) in your web browser and log in. How do I open ERA Web Console?
     
  2. Click Admin Client Tasks, expand ESET Remote Administrator, click Remote Administrator Components Upgrade and then click New.

Figure 1-1
Click the image to view larger in new window

  1. Type a name for your task in the Name field and ensure that Remote Administrator Components Upgrade is selected from the Task drop-down menu.

    Figure 1-2
    Click the image to view larger in new window

  1. Expand the Settings section, select the check box next to I agree with application End User Licnese Agreement and then click Choose server.

    ESET Remote Administrator version 6.2.11 and earlier: 

    Adding targets is done during task creation (for example, after adding a new task and giving it a Name, click Target to add groups or clients to the task).

     

    Figure 1-3
    Click the image to view larger in new window

  2. Select the ERA Server version that will be used and click OK.

    Figure 1-4
    Click the image to view larger in new window

  3. Click Finish when you are finished making changes to your task.

  4. Click Create Trigger when you are asked whether you want to add a trigger for the client task. For instructions to assign a trigger to a Client Task, see the following ESET Knowledgebase article:


 

Perform a manual component-based upgrade of ERA Server and Web Console

You can only use the component-based upgrade task from the following versions of ESET Remote Administrator:

  • 6.2.171.0
  • 6.1.444.0
  • 6.1.365.0
  • 6.1.265.0

If you are upgrading from a minor version of ERA (a version not listed above) or having issues using the component-based upgrade task, follow the instructions below:

I. Upgrade ERA Server and Web Console

  1. Download the necessary ERA 6 component installers (Server, Agent, RDSensor and Web Console are required. Download other installers as needed).

Do not rename downloaded msi installer files

 

  1. Stop the Apache Tomcat service. Navigate to your %TOMCAT_HOME%\bin directory (for example, C:\Program Files\Apache Tomcat\Tomcat7\bin) and double-click tomcat7w.exe.
     
  2. Back up the following folder and all of its contents:

    File location will differ on 32-bit systems:

    On 32-bit systems, the Program Files (x86) folder will be named Program files

    C:\Program Files (x86)\Apache Software Foundation\Tomcat 7.0\webapps\era
     

  3. Make a copy of the EraWebServerConfig.properties file located in the following directory:

    C:\Program Files(x86)\Apache Software Foundation\Tomcat 7.0\webapps\era\WEB-INF\classes\sk\eset\era\g2webconsole\server\modules\config\EraWebServerConfig.properties
     

  4. Delete the contents of the Web Console folder (including the era.war file if it is present) as well as the folder itself, located in the following directory:

    C:\Program Files(x86)\Apache Software Foundation\Tomcat 7.0\webapps\era
     

  5. In the extracted folder, locate the file era.war and extract it (you can rename the file to era.zip, but it is not necessary for extraction to work) to the following folder:

    C:\Program Files (x86)\Apache Software Foundation\Tomcat 7.0\webapps\era
     

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

    C:\Program Files (x86)\Apache Software Foundation\Tomcat 7.0\webapps\era\WEB-INF\classes\sk\eset\era\g2webconsole\server\modules\config
     

  7. Double-click ERA Server.msi to run the ERA Server installer.
     
  8. Specify your database connection settings:
    • If you installed using the all-in-one installer:
      Select MS SQL Server via Windows Authentication from the Database drop-down menu and click Next.
       
    • If you used an existing MS SQL Server/MySQL:
      Select the connection type you defined during installation. An administrative privileged database connection (user) is required when connecting to the ERA Server database. Click Next when you are finished.
       
  9. Start the Apache Tomcat service, depending on your system configuration, allow up to 40 seconds for the service to start.
     
  10. Log into ERA Web Console at the following URL: https://<hostname>/era (How do I open the ERA Web Console?).
     
  11. Continue to part II below to upgrade other ERA components.

 

II. Upgrade other ERA Components

ESET Rogue Detection Sensor (RD Sensor): To upgrade RD Sensor, run .msi installer (there are no parameters for this installation).

ESET Remote Administrator Agent (ERA Agent): There are two methods that can be used to upgrade the ERA Agent:

  1. Run the Agent .msi installer locally on each client.
     
  2. Create a Run Command Client task from within Web Console. 
     

Agent upgrade using Run Command Client task

  1. Create new Dynamic groups based on Operating System, one group for 32-bit and another for 64-bit. To do so:
    • Create a Dynamic group template for 32-bit systems with the following parameters:
      • Operation "AND"
      • Add rule OS edition > OS platform = (equal) 32-bit
      • Add rule OS edition > OS type contains Windows
         
    • Create a Dynamic group template for 64-bit systems with the following parameters:
      • Operation "AND"
      • Add rule OS edition > OS platform = (equal) 64-bit
      • Add rule OS edition > OS type contains Windows
         
    • Create a Dynamic group based on the 32-bit template you've just created.
       
    • Create a Dynamic group based on the 64-bit template you've just created.
       
  2.  Create a new Client task for 32-bit systems:
    • In the Basic section, select Run Command from the Task drop down menu.
       
    • In the Targets section, select the newly created Dynamic group for 32-bit operating systems.
       
    • In the Settings section, enter the following command in the Command line to run text field (replace server with your actual server name and readonlyshare with your share name), for example:

      msiexec /qn /i "\\SERVER\readonlyshare\Agent_x86.msi" /l*v! %TEMP%\era-agent-upgrade.txt

      • for example, when using the installer package via HTTP:

        msiexec /qn /i "http://SERVER/share/Agent_x86.msi" /l*v! %TEMP%\era-agent-upgrade.txt

        msiexec /qn /i "http://repository.eset.com/v1/com/eset/apps/business/era/agent/v6/6.1.365.0/Agent_x86.msi" /l*v! %TEMP%\era-agent-upgrade.txt
         

  3. Create a new Client task for 64-bit systems:
    • In the Basic section, select Run Command from Task drop down menu.
       
    • In the Targets section, select the newly created Dynamic group for 64-bit operating systems.
       
    • In the Settings section, enter the following command in the Command line to run text field (replace server with your actual server name and readonlyshare with share name), for example:

      msiexec /qn /i "\\server\readonlyshare\Agent_x64.msi" /l*v! %TEMP%\era-agent-upgrade.txt

      • example when using installer package via HTTP:

        msiexec /qn /i "http://SERVER/share/Agent_x64.msi" /l*v! %TEMP%\era-agent-upgrade.txt

        msiexec /qn /i "http://repository.eset.com/v1/com/eset/apps/business/era/agent/v6/6.1.365.0/Agent_x64.msi" /l*v! %TEMP%\era-agent-upgrade.txt
         

    ERA Log File location

    The ERA log file is accessible at: %TEMP%; for example: C:\Windows\Temp\

    See also log files location for all ERA components in ERA User Guide.

    The error message "MainEngineThread is returning 1619" indicates a damaged installation package which cannot be opened.
     
  4. Details about client tasks can be viewed under Computer detailsInstalled Applications. There will be a brief period where two versions of agent are running on a single client machine. This is only temporary. See Computers Outdated applications (drill down to show particular computers) to monitor the status of the agent on client computers. Data in this report is updated once per hour.

Пожалуйста, оцените эту статью:

Мы не сможем ответить на этот комментарий. Запросы о помощи необходимо отправлять через специальную форму.