I started this in a different thread (
http://forum.avast.com/index.php?topic=118805.0) but that one was going nowhere and the topic has changed slightly so here we are...
I am running avast! SOA 1.2.2.28 - Database Ver. 1450
Clients: 7.0.1455
Every time I manually run a Deploy Job or allow a scheduled deploy to occur, it disables the client's firewall and places an exclamation mark on the client's avast! tray icon. If I open avast! on the client, it tells me it is expired and shows the start date of our current license as the expiration date.
If I log on to avast! SOA and edit the group settings to disable the Firewall and then later go back and re-enable the firewall, then the firewall is enabled on the client and the exclamation mark goes away but the client still shows as expired and requests a restart. Everything reports as good in SOA (all green checkmarks) and no indication as to any problems on the server.
When the client reboots, the avast! console shows the correct expiration date and has no problems until the next deploy.
I have found that if I disable then re-enable the firewall through SOA before opening the console on the client, it does not mark the client as expired and does not request a reboot.
I have tried creating new deploy jobs and all have the same problem. These are the typical settings I use:
Details:
Domain: We only have 1 domain and it is selected
Force reinstall (existing) - normally unchecked but does not alter results
Reboot client computer after installation: Never
Username: Domain\Administrator
Schedule:
Changing the schedule time/frequency appears to have no affect
Target:
Selecting group(s) or individual computers only affects which computer(s) get affected
Note: The servers appear completely unaffected by this as the server clients do not have a firewall. The workstations are all Windows 7 (some x32 but most x64).
Any ideas what could be causing this? I've done everything I can think of short of reinstalling SOA.
