Baza wiedzy ESET

Upgrade ESET Remote Administrator 6.3 and later to the latest ESET Security Management Center 7 via Web Console

Issue

  • Upgrade individual ERA components (Agent, Server, Proxy) to ESMC
  • Resolve CReplectionModule errors by upgrading to the latest version

Solution

Before you start

Prerequisites

Before upgrading to ESMC 7, make sure that all ESMC 7 installation prerequisites are met.

Upgrade to ESMC 7 is possible only from ERA 6.3 and later

You must have ESET Remote Administrator (ERA) version 6.3 and later to upgrade to ESET Security Management Center 7. Check which version of ERA you have installed.

Perform a full backup of ERA:
  • Database: Follow these instructions to backup the ERA database.
  • Configuration: Copy the Startupconfiguration.ini file, located at: C:\ProgramData\ESET\RemoteAdministrator\Server\EraServerApplicationData\
  • Certificates: Export the Certification Authorities and Peer Certificates.
  • Mobile Device Connector: If this component is used, copy the Startupconfiguration.ini located at: C:\ProgramData\ESET\RemoteAdministrator\MDMCore\Configuration.

 


Perform a Components Upgrade task from the ERA Web Console

The following steps will upgrade both ERA components (Server, Console) and the ESET Remote Administrator Agent(s) (ERA Agent). When upgrading to the latest version, your policies will be preserved. Update your ERA Server first. Select a 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).

Components Upgrade task may take some time to complete

Please be patient during the Components Upgrade task process. It may take some time to complete. Do not restart your ERA Server until the task has completed.

Special characters may cause upgrade to fail

If you have met the requirements for upgrading and your upgrade to the latest version of ESET Security Management Center (ESMC) 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.

  2. Click Admin  → Client Tasks → ESET Remote Administrator →  Remote Administrator Components Upgrade and click New.

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

  1. In the Name field, type a name for your task. In the Task drop-down menu, verify that Remote Administrator Components Upgrade is selected.

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 License Agreement and then click Choose server.

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

  1. Select the ESMC Server you want to upgrade to and click OK. (The latest version of ESET Security Management Center (ESMC) is 7.0.72.0)

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

  1. Click Finish.

  2. Create a trigger and add the ERA Server computer as a target to execute the task.
    Do not add more target computers

    Add only the computer where ERA Server is installed as a target. Do not add more target computers at this point of the upgrade.

  1. Wait a few minutes until all ESMC components installed on the server machine are upgraded. Apache Tomcat service can get turned off during the update. If the Web Conosle is unavailable after the update, open the services management (run services.msc) and Start the Apache Tomcat service.

  2. When the task is finished on the ESMC Server machine, verify that it still connects and works properly. Wait an hour to see if any problems occur. Afterwards, you can upgrade the rest of the agents. If you are running a larger network, with hundreds or more client computers:

    ERA 6.x Proxy users

    If you have ERA 6.x Proxy installed, read the respective Knowledgebase articles before upgrading other clients.

    Do not upgrade clients behind Proxy, before a suitable proxy solution is set up.

    1. Choose a sample of clients for a test update (include at least one client for each operating system/bit category) and run the task.

    2. We recommend using Apache HTTP Proxy (or any other transparent web proxy with enabled caching) to limit network load. The test client machines will trigger the download/caching of the installers. When the task is ran again, the installers will be distributed to client computers directly from the cache.

    3. After a successful test update, proceed with the rest of your clients. Alternatively, target the group to All. Upgrade is not performed on computers that have already been upgraded.
       
  3. If the Components Upgrade task is not working properly, try upgrading Agents using Run Command Client task.

Alternative method: Upgrade ERA Agent(s) to ESET Management Agent(s) using Run Command Client task
Recommendations for alternative method:

This is an alternative method recommended for advanced users or if the Components Upgrade task is unsuccessful.

  1. Create a new Dynamic Group based on operating system (32-bit or 64-bit).
    • For 32-bit systems:
      • Operation "AND"
      • Add rule OS edition > OS platform = (equal) 32-bit
      • Add rule OS edition > OS type contains Windows
         
    • For 64-bit systems:
      • Operation "AND"
      • Add rule OS edition > OS platform = (equal) 64-bit
      • Add rule OS edition > OS type contains Windows
         
  2. Create a new Client Task for 32-bit systems.

    ESMC Log File location:

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

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

    1. In the Basic section, select Run Command from the Task drop-down menu.

    2. In the Settings section, in the Command line to run field, type: msiexec /qn /i "\\SERVER\readonlyshare\Agent_x86.msi" /l*v! %TEMP%\era-agent-upgrade.txt (replace server with your actual server name and readonlyshare with your share name).
      • 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/v7/7.0.577.0/agent_x86.msi" /l*v! %TEMP%\era-agent-upgrade.txt
    3. Create Trigger for this Client Task and in the Targets section, select the dynamic group for 32-bit operating systems created in Step 1.
       
  3. Create a new Client Task for 64-bit systems.

    "MainEngineThread is returning 1619" Error Message:

    The installation package is damaged and cannot be opened. Deploy ESET Management Agent with a different installation package.

    1. In the Basic section, select Run Command from the Task drop-down menu.

    2. In the Settings section, in the Command line to run field, type: msiexec /qn /i "\\server\readonlyshare\Agent_x64.msi" /l*v! %TEMP%\era-agent-upgrade.txt  (replace server with your actual server name and readonlyshare with share name).
      • 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/v7/7.0.577.0/agent_x64.msi" /l*v! %TEMP%\era-agent-upgrade.txt
    3. Create Trigger for this Client Task and in the Targets section, select the dynamic group for 64-bit operating systems created in Step 1.
       
  4. To view client task details, click Computers, select the applicable client computer, click Show Details and then click Installed Applications.

    There will be a brief period where two versions of Agent are running on a single client machine. This is only temporary. Create an Outdated applications report to monitor the status of client computers hourly.