AES client update frequency

We’ve recently migrated to AEA, and the Avast 7 client - it’s been relatively smooth, but I have one query.

A lot of the clients seem to be rather slow at updating themselves, and are trailing behind with VPS version 121202-0 (etc). There aren’t any errors in the log, and the AEA is set to push/pop; does anyone have any suggestions as to what I might try?

Apparently it’s not just being slow, the clients do not update at all - unless manually commanded to do so from the AEA console. Logs don’t show any connection errors, and the problem exists on machines with disabled firewalls.

are the correct ports opened on the server too ?

Hi there,

For the benefit of testing, I have since disabled the server’s firewall; alas, no change.

Hi,

same problem here. Avast closed my call without any notice. i’m quite angry now.

Further testing shows that asking clients to update (from the client PC) will update correctly from the AEA server.
Asking the clients to update from the server works.

Clients report no errors, and just don’t actually try to update on their own.

Well two machines have updated, and those are the only two machines that don’t use a proxy, and have direct internet access. The other machines periodically show such information via netstat:

a313mp.avast.com:http  SYN_SENT

Now, these clients are all configured to to use a direct connection, and not fall back on updating from the internet.
These clients all update from internal servers just fine when asked to do so manually from the client or server.

There is quite obviously a bug here, which causes clients to effectively ignore settings when periodic update attempts are made, so I’d appreciate any assistance. My support ticket is apparently uninteresting, and I’ve pretty much given up hope of getting this system working.

While a few other machines are now regularly updating, most of them are still not doing so unless manually instructed.

Well after countless messages back and forth, mostly being asked the same question several times, Avast are unable to offer any further suggestions - despite the fact that they have yet to request a single log file. I suspect this is a known issue.

We’re obviously going to have to change AV providers, although God only knows how futile a refund chase is going to be. Ye be warned.