j-gray 44 Posted March 7, 2016 Posted March 7, 2016 Most, if not all of my Windows clients display this Critical problem under 'Functionality Problems'. I have a dynamic group of Windows workstations to which I've applied the 'Security Product for Windows - Antivirus - Balanced' policy. In this policy, updates are configured and Scheduler is set for 'Regular automatic update' (every 60 minutes). All workstations that are currently online are up to date. I verified they're getting assigned to the correct dynamic group and that the policy above is applied to them, as well. What am I doing wrong, and/or why is this message showing? Thank you.
ESET Staff MichalJ 434 Posted March 9, 2016 ESET Staff Posted March 9, 2016 Hello, this is shown, in case that there is no regular update task set in the Endpoint client. Could you please verify, whether there is: - no other policy set upper in the hierarchy (not on the dynamic group, but on the parent static group or on the group all), that changes scheduler settings (removes for example the update tasks from it) - send a screenshot of the scheduler for any of the affected endpoints, that are showing this error Please note, that the policy you have listed, has not set "apply flag" next to scheduler, so whatever is configured in the scheduler for that policy, is not being applied. You can try troubleshooting by setting the scheduler part of the policy to "apply", and let us know, if it helped (but this is valid only in the case, that the scheduler is currently empty on the affected computers, or update tasks are missing). This would however overwrite any current scheduler settings.
j-gray 44 Posted March 10, 2016 Author Posted March 10, 2016 (edited) Thanks, MichalJ. No policies above that remove the scheduled event. You can see that I changed the scheduler policy for automatic updates to 30 minutes. Yet, it still appears as 60 minutes on the client scheduler and is not enabled. The client is receiving all the correct policies otherwise. Can there be only one scheduler policy? I have one for weekly scan, and one for definition updates. Thanks again for your help. 01-windows-policies.tiff 02-windows-scheduler-policy.tiff 03-client-applied-policies.tiff 04-client-critical-alert.tiff 05-client-scheduler.tiff Edited March 10, 2016 by j-gray
ESET Staff MichalJ 434 Posted March 10, 2016 ESET Staff Posted March 10, 2016 Yes, you can have only one scheduler policy, as entire scheduler window is being handled as "one setting". So if you have two, they will overwrite each other. That might be the cause of your problem. Btw, why are you not using Client Tasks instead? ERA agent is able to trigger both scan and update.
j-gray 44 Posted March 10, 2016 Author Posted March 10, 2016 Yes, you can have only one scheduler policy, as entire scheduler window is being handled as "one setting". So if you have two, they will overwrite each other. That might be the cause of your problem. Btw, why are you not using Client Tasks instead? ERA agent is able to trigger both scan and update. I followed ESET KB for setting up the scheduled scan. I couldn't find any documentation for scheduled updates for v.6, so I assumed it was a similar process as the scan. Looks like I assumed wrong I'll try the client task and see if that does the trick. Thanks again.
j-gray 44 Posted March 11, 2016 Author Posted March 11, 2016 Btw, why are you not using Client Tasks instead? ERA agent is able to trigger both scan and update. So I set up the signature update via 'Client Tasks', as you suggested. I can see by the logs that it is running on the clients (every hour, as scheduled). However, the Critical error persists; 'No regular updates scheduled' on all of the clients. That being the case, I'm not sure what the best practice is for scheduling updates and scans for multiple OS's?
ESET Staff MichalJ 434 Posted March 11, 2016 ESET Staff Posted March 11, 2016 What you have to do, is to revert the scheduler to the default state and have at least one regular update task scheduled (the automatic). Basically "enable" the regular update in the policy for the scan. What I would recommend, is to schedule also the scan, via the "Client task". if possible. This relation between scheduler and ERA agent task, is something we will have to address in future service releases.
Recommended Posts