We are running:
Avast! Endpoint Protection Suite Plus
Product type: 2
License count: 55
Subscription valid till: 1/16/2014
Program version: 7.0.1455
Lately it seems, typically once a day (around lunch time) all the clients firewalls turn off and if you open the client it tells you the license expired on 1/16/2013. However, if I go in to group settings before I open the client and disable the firewall, wait about 10 - 15 seconds and then go back and re-enable the firewall, all the clients update their license info and are fine for the next 24 hours or so.
This only seems to be affecting the the clients and not the servers as I never see yellow exclamation points on them under network indicating their firewalls have been disabled.
double click license file from any system running avast! Does it have more than 1 line item (drop down for different products, and / or different dates)?
I’m thinking it might be tied to the “Deploy/update avast! clients…” default job that hangs from time to time. Right now it is stuck at 0% since noon on 4/5/2013
Is there a good way to stop/kill this job without restarting the server?
To answer my own question here, I found you can kill the process Avast.Sbc.Service.exe and it will restart itself and in the process kill any stuck jobs.
I don’t particularly like doing this but it is a temporary workaround until you can reboot the server after-hours.
After dealing with this for a longer period of time and gathering more information, the problem definitely seems tied to the default “Deploy/Update avast!” job. This job is scheduled to run at noon every day and that is precisely when clients see the Yellow exclamation mark on their avast! icon indicating the firewall has been disabled. When checking on the server, this job is hung at 0% and will be stuck for days at a time until the server is rebooted or the process is killed.
Other deploy jobs with the same settings but targeted to individual computers succeed with no problems.
I will attempt to disable the default deploy/redeploy job and re-create it and see if this helps. In the mean time, does anyone know what could be causing the problem or at least know a way to see where the job is hanging?