Hi,
Been using Avast! and ADNM for some months now and very pleased with it (have a 35 seat license that we are only using about half of at present), however I’ve just noticed an odd problem.
I added a couple of new machines to the network (remote deployed seemingly successfully) and assumed all was well (they appeared in the catalogue and were/are green and I can see the last contact time changing throughout the day) however a couple of days later I noticed they had not picked up all their settings from the AMS, and no amount of settings fiddling and ‘applying to group’ or ‘applying to computer’ on the AMS seems to make them do it. I also tried deleting all the computers from the catalogue and getting AMS to re-discover them, and that made no difference either.
Out of curiosity I removed the client (with aswclear) from one of the existing machines that appeared to be working and re-deployed, that machine is now also not picking up all it’s settings any more.
The REALLY strange thing is that certain things DO seem to be propagating, the scheduled scan ran as expected on Friday (on all machines including the stubborn ones). I changed the poll-rate to once a minute as an experiment and ALL the machines picked up the new poll-rate but the stubborn machines still didn’t change their other settings (such as password to access client settings, remote access to chest, check cds and floppies in drive when logging off, ask for update when new program available, only pause scheduled scan not stop etc. etc.)
My ADNM version is 4.7.608 running on MS SQL Server Express (on a W2KPro machine that is not running anything else, except the avast managed client)
All managed clients are at v4.7.652.0
One of the stubborn clients is on Windows 2000 Professional SP4 (fully updated)
The other is on Windows XP Proffesional SP2 (fully updated)
Nothing is in the ‘emergency’, ‘alert’, ‘critical’, ‘warning’ or ‘notice’ AMS logs,
There is general start-up info in the ‘info’ AMS log along with the ‘error’ entries below in other places, but I’m pretty sure that’s just to do with a re-boot of the AMS machine I did around that time.
AMS error log once:
30/04/2007 12:24:20 1177932260 SYSTEM 328 Database command failed [CClient::OnPop, 80004005]: [DBNETLIB][ConnectionWrite (WrapperWrite()).]General network error. Check your network documentation.
30/04/2007 12:24:20 1177932260 SYSTEM 328 Database command failed [CClient::AppendEngGroupProperty, 80004005]: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
XP Client error log once (but not on the W2K client):
30/04/2007 12:23:54 1177932234 SYSTEM 1776 Third server conn attempt (last good: 192.168.1.6:16111) failed. (error 0000274D).
30/04/2007 12:24:03 1177932243 SYSTEM 1776 Cannot connect Server lookup didn’t find any AMS’! socket, WinSock error 0x00000000 has occurred.
I’ll carry on digging myself but if anyone else out there has any suggestions please point me in the right direction! I’m sure I must just be missing something stupid as everything had been working fine!
Thanks.
Dammon.