Jump to content
Nono

Client Tasks - Invoke ASAP If Event Missed doesn't work as expected

Recommended Posts

I've currently an issue with a Client task which aren't execute on computer not restarted for few days.

What I want to achieve: Execute a Batch script every week day at 10AM on our endpoints and execute ASAP the script if the endpoint wasn't reachable/on at 10AM.

My issue: Endpoint which aren't restart doesn't get the batch script executed.

How I setup (probably wrongly?) the task :

image.thumb.png.31a3a50694dc29f9f64cf647fc104a5c.png  

 

 

image.png.0d71b5173f55b913f2641fce3c7b642b.png

This seems to NOT work when the computer goes in hibernation/sleep mode. (no matter if the computer is on at 10 AM, or later).

 

Would this be a bug or an configuration issue ?

 

Many thanks for your help !

Share this post


Link to post
Share on other sites

Could you please provide version of AGENT installed on those machines? Is it latest available version? Asking because we had a bug in first 7.0 release with the same symptoms. Issue was triggered by time shift (time synchronization), which is normal for long running system, and only way to recover from it was to reboost (= restart AGENT service). This issue has been resolved in AGENTs distributed with release 7.0.72.0 (November 2018).

Share this post


Link to post
Share on other sites

It's actually a mix of two :

7.0.2073.0 & 7.0.2073.1

 

is 7.0.2073 > 7.0.72 ?

Share this post


Link to post
Share on other sites
1 hour ago, Nono said:

It's actually a mix of two :

7.0.2073.0 & 7.0.2073.1

 

is 7.0.2073 > 7.0.72 ?

This seems to be more version of ESET Endpoint Security, but we will need version of "ESET Management Agent" installed on client machines.

Share this post


Link to post
Share on other sites

Oh, my bad.

It's then 7.0.553.0 for everyone

 

Share this post


Link to post
Share on other sites
35 minutes ago, Nono said:

Oh, my bad.

It's then 7.0.553.0 for everyone

 

Thanks for confirmation -> you are indeed using AGENT from original ESMC release that contained this issue, which has been resolved in subsequent service release, where ESET Management Agent for Windows has version 7.0.577.0. I would recommend to try to update AGENT on affected system manually and monitor behavior. Update should not require reboot, so it should be possible even on server-based system. Also it is not required to upgrade any other part of ESMC infrastructure, it not already on latest versions.

Share this post


Link to post
Share on other sites

@MartinK I usually use the "ESMCAgentInstaller.bat" to install the agent on my endpoint.

By editing the script, I've notice this part :

set url=hxxp://repository.eset.com/xxx/v7/7.0.553.0/agent_x64.msi
set checksum=yyyyyy
if defined IsArch_x86 (
  set url=hxxp://repository.eset.com/xxx/v7/7.0.553.0/agent_x86.msi
  set checksum=yyyyy
)

if you could provide me the url + checksum for the version 7.0.577.0 I could probably reuse the script with the credentials/cert/IP I already have, isn't it ?

Share this post


Link to post
Share on other sites

It turns out that I still had the "prerelease" link as repository server (due to early access ESMC)

Change it to "AUTOSELECT" on Server settings + Agent Policy settings, show me that I should be able to update my version which should solve the issue.

I've currently an issue to update both client + agent remotely (aka from ESMC), but I guess I'll have to contact my ESET Representative for that.

Current behavior : Updating remotely remove the AGENT, and leave (only) the client out-dated.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×