4.0.437 - Undocumented Fixes?

So far, I've noticed at least 1 un-documented fix:

- Tasks scheduler no longer repeats tasks that have completed already.
( I had a weekly scan setup that would repeat every reboot, either either 'weekly' set or time-in-hours) - it's not doing this since 4.0.437

 

-- Nevermind -- It just repeated the task after I restarted just now, and it had already done it less than 24 hours ago.. oh well.

 

Hello SalC,

How is this task set up? Is it part of a push install package or set in a policy? If it is from a policy, then everytime the client checks in it will reset the time it was last run. You should only set tasks in the push install package or in a configuration task that you push out.

 

I've had this problem for years with eSet, starting with 3.0. Tech support just says to set up the task differently - do not run if can not run at scheduled time. One of many work arounds but refusal to fix a defect. Since my scan runs on Sunday, and 150 PCs were powered off, they NEVER run the weekly scan with all the heuristics and zip scanning turned on. I do find viruses this way, which the realtime does not find. Things that slipped in on 0 day.

I came here hoping to see this fixed This is one of several reason why we have began migrating away from eSet.

 

Support already said this was a known issue and would be fixed in an upcoming build -- hopefully it will, because yes -- I have that task enabled and disabled on some clients via the Policy Manager..

 

SalC,

The post below has more information on what I mentioned before:

https://www.wilderssecurity.com/showpost.php?p=1467420&postcount=2

There is an issue that edwin3333 is referring to that is something different. If you tell the software to run a task if it has never been run, then it will always think it has never been run. The solution to your issue is to set the task using a configuration instead of Policy Manager.

This is not a problem with the ESET software, it is just how it works. The Policy Manager is not the place to set scheduled tasks, push installs should have these set up. If they need to be changed later, a configuration task should be pushed out. Policies by default will reset any settings that have been changed, including the time a scan was last run.

 

The problem I have with tasks re-occurring has existed before eSet RA had policies as an option in the RA. And Long before I used Policies. It affects tasks setup through the GUI, from the RA set by configuration, etc. I agree with what you say about policies as the link and all, but there is more to it than I'm simply doing something improperly.

For example, I had a configuration I pushed to do run an external command one time at a scheduled date and time and never again. I pushed that config to my laptops. They didn't run it one time, they ran it hourly for months before I realized it. This was RA version 1, and no policies, and I wasn't pushing the config hourly.

This still isn't fixed either. In any event, I'm with Nod32 until my license expires later this year. I've put 4.0.437 on about 400 PC's today and no problems yet, knock on wood.