Clients no longer updating - Windows complains about out of date AV definitions

Avast Business Avast Distributed Network Manager
1

ADNM version: 4.8.995
VPS version: 100416-0
Avast client: 4.8.1061

Recently my Windows clients have started complaining about AV definitions being out of date - “Your computer might be at risk”.

I’ve tried updating my server, but it says I’m at the latest version.

I’ve tried pushing updates to my clients from ADNM, but I don’t have anything more recent to push. I see all the 5.0 announcements, but as an ADNM user they don’t apply.

Are there more recent updates that I should install/push? Should I start telling my users to ignore the warning?

2

I don’t know if this is the same for ADNM but in the client versions 4.8.1368 (which is the latest avast 4.8 version), a Repair of avast resolved the out of sync issue. So if you can find the equivalent in the ADNM installation that might do the same.

Example for a client/stand alone 4.8 version:
Try a repair of avast. Add Remove programs, select ‘avast! Anti-Virus,’ click the Change/Remove button and scroll down to Repair, click next and follow. This has in the past resolved this out of sync issue between reported and actual virus definitions version.

3

David,

Thanks for the suggestion, but after doing the repair, the client is still claiming an error. Pushing updates from the server, and/or pulling from the client, did not change anything - even with a reboot.

4

Sorry that didn’t work, not using ADNM, it was a bit of a roll of the dice. Hopefully someone with experience of the ADNM version can help.

5

Definetely no, you should repair your problem, not ignore it. See mirror log from ADNM console - view AMS mirror state. It should be like my is:

=========================================
avast! Distributed Network Manager Mirror

Mirror folder: C:\Program Files\ADNM\MgmTools\Mirror\mirror
Mirroring products: av_mgm,av_net,av_pro,av_srv

Current versions in mirror:
avast! Distributed Network Manager: 4.8.995 (Feb 19, 2010)
avast! Network Client (managed): 4.8.1061 (Feb 19, 2010)
avast! Home/Professional Edition: 4.8.1368 (Nov 27, 2009)
avast! Server Edition: 4.8.1110 (Feb 19, 2010)
Virus database: 100505-1 (May 05, 2010)

Pay attention on last item - version of virus database (VPS). When VPS has old date (the same as on your clients), you should solve problem with mirror. See mirror log and if “avast! Management Server” service is running.
If VPS in mirror is current, you should suppose that problem is on clients. See logs on client or try uninstall agent on clients, using ASWCleaner tool. And than install new client via installation task or other way (deployment via MSI package generated by ADNM)

6

Believe me, telling my users to ignore the warning was not high on my list of desirable things to do. Logs? Silly me, should have looked there sooner.

The key thing I noticed in the logs was

general scr: Another instance of mirror.exe is already running.,

I’m not sure how that happened, but (taking a typical Unix admin view of Windows) a reboot seems to have fixed it. I’ve pushed updates out to the clients, and they now seem happy again.