ColdfirexAre you on KES 2.1?
bdawsonWe are having the same issue. We run around chasing outdated definition alerts even though the updates succeed. Would love to have a solution to this...
JonJohnstonSame here. Haven't bothered opening a ticket yet. I will soon if don't discover anything ourselves or read a solution on here.
1. Please review the below kb article to configure the ports. http://kb.kaseya.com/article.asp?article=296848&p=11855 2. Any machine that sources updates from the internet need to have access to download from theb following URLs (if updates are sourced from a LAN share, then the file server needs to download from these locations): - - update.avg.com - update.grisoft.com - backup.avg.cz - backup.grisoft.cz - files2.grisoft.cz - files2.avg.cz - download.grisoft.cz - download.avg.cz - akamai.grisoft.cz - akamai.grisoft.cz.edgesuite.net - akamai.avg.cz - akamai.avg.cz.edgesuite.net - akamai.grisoft.com - akamai.avg.com - akamai.grisoft.com.edgesuite.net - akamai.avg.com.edgesuite.net - *.akamai.net (there can be almost anything instead of "*", e.g. a962.g.akamai.net) You may also need to add the following AVG services: - - avgam.exe - avgemc.exe - avgiproxy.exe - avgnsx.exe - avgtray.exe - avgui.exe - avgupd.exe
alexrompFor one of my clients it was an issue with the firewall not allowing the HTTP connections. There's an article on AVG's site with a list of all of the addresses that need to be allowed. Have you tried manually running the update from the avgui.exe on the client station to see if it succeeds from there?