Jump to content

ERA module update task fails


HHS-ADMIN
 Share

Recommended Posts

Situation:

  • ERA Appliance is up to date on Version 6.5.417.0
  • The Win7Pro clients are on ERA 6.4.283.0; Endpoint AV 6.4.2014.0

Triggering an "Modules Update" task either via context menu or via an new created task including "clear update cache" fails.

How to get the new versions running?

Link to comment
Share on other sites

  • Administrators

Does update fail even if you run update locally on a client? If so, what error do you get?

Link to comment
Share on other sites

2 hours ago, Marcos said:

Does update fail even if you run update locally on a client? If so, what error do you get?

Hi Marcos,

(all wordings translated from German to English :wub:)

1. Local update activity:

  1. Advanced Setting / Clear Update cache
  2. Update: "No update needed" / Signature database is up to date. See attachement local.png

it seams in Version 6.4 no local update to 6.5xx possible.

2. Remote

  1. See Task Executions on attachement "remote"
  2. Result see §status.png

By the way: documentation states, that in V6.5 ALL modules will be update whereas in V6.4 only virus database is touched ???

Klaus

 

 

local.PNG

remote.PNG

status.PNG

Link to comment
Share on other sites

As test I just started a "Remote Administrator Components Upgrade" task on all clients.

... still in status "running". I'll report on result.

Link to comment
Share on other sites

Solved!

One has first to start a "Remote Administrator Components Upgrade" task and after this a separate "AV Software install". The combined "modules updates task" at least in this situation isn't functional.

Link to comment
Share on other sites

  • ESET Staff

Hello. That task (module updates) updates only the protection modules of the software, not the software version itself. 

Link to comment
Share on other sites

  • Administrators
Quote

By the way: documentation states, that in V6.5 ALL modules will be update whereas in V6.4 only virus database is touched ???

This is just a change in wording. As of ERA v6.5, "Virus signature updates" was renamed to "Modules update" but the task has always served to download all module updates, not just the engine itself.

Link to comment
Share on other sites

  • ESET Staff

We are trying to more correctly communicate what the task actually does (calling the task previously as "Virus Signature Database Update" was not correct, as it updates far more components, than just the VSDB module). 

There are as of now 3 individual tasks, that are somehow touching the software installed on the machine:

  1. Remote Administrator Components Upgrade task - this one is intended to upgrade only the components of the ERA infrastructure (ERA Server, Webconsole, Agents, Mobile Device Connector), and always to the newest version, linked to a particular version of the server. This one should be used, to upgrade ERA for example from versions 6.3 / 6.4 to the latest 6.5
  2. Software Install Task - this one is intended to install the corresponding security software (Endpoint Antivirus, Endpoint Security) from ESET Repositories. You have to choose the version / language and execute the task on the clients. Recommended way would be to start in the "dashboard" element "Outdated Applications" choose all listings of a corresponding software, open them in "computers pane" and then select all, and initiate a software installation task.
  3. Update Modules Task - this one is intended to initiate updating of core internal product modules (Detection engine (formerly known as Virus Signature Database), but also all others (as listed in "about / installed components"). So this one updates the internals of both Security products, but also the modules of ERA agent (updater / loader / configuration support module).
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...