Definition not updated

[selinathe1]

I have 9 servers in the same primary server group. and 4 of them can't update their definition. one of them actually ahve definition as 11/17/05!!!
I only started working at this office at beginning of this month. So i'm totally sure what has happend (if any) in the past. I've tried updating it on individual servers. still doens't work.
is there any workaround?

All servers are on Win 2000, SP1.

Thx
-selina

 

[LawnBoy]

Try downloading the .xdb definition file from Symantec and updating with that instead of LiveUpdate.

 

[JOAMON]

Might also try donloading the latest version of live update and install that on the servers.

 

[selinathe1]

LawnBoy
I checked the program file on the server that doesn't have the updated defition and i fould the latest .xdb file in there. so if it exists in the NAV program file, how come it doesn't show that it's been updated to 1.29.06 definition?

i've also tried intelligent updater and still doesn't help. the primary server has other secondary servers besides this one. and 1/2 of them are updated. so i don't think it's because the definition is not passed on from the primary...

any other idea? this started to really bug me...



Thx
-selina

 

[JOAMON]

Download and install the latest version of liveupdate on those machines and then tell the primary server to update definitions and see if that helps.

 

[selinathe1]

JOAMON
That's the thing. Even if I run Live Update, Intelligent Updater or copying .xdb file to the symantec program files to those servers, it just doesn't update it.
To be more precise, when I run Liveupdate, it says all definitions are upto date. But the definition date is not updated to 01.29.06. (couple of them have it as 01.17.06...)

is there another work-around?

selina

Thx
-selina

 

[LawnBoy]

I've had this problem, and I fixed it by manually downloading the latest .XDB and manually copying it to the server.

Sometimes Symantec changes the LiveUpdate routines and they hiccup. Subsequent updates have the fix.

 

[LawnBoy]

Err, make that "copying it to the primary server".

 

[selinathe1]

Well, it still doesn't update.
I looked into it a bit closer and found out the followings:
1. In console in the primary server, this secondary server states that the last scan was 01/23/06. But when I checked the scan history on the secondary server, the daily scan has been running and completing, EXCEPT 12/22/05 scan, which still says "scanning". But the daily scan after that is running fine.
2. Ater downloading .xdb to the secondary server and copying to the primary server, in the console, the definition on the secondary remains 1/17/06, but the primary server was updated there.

Is it that the secondary server is not communication well?

Thx
-selina

 

[selinathe1]

So I checked one more thing in this server group. The primary server was swapped before I joined here and this transfer was done by the IT manager, and I suspect it wasn't done properly. Only 1 of the secondary servers has the new primary server as its primary and the rest has the old one as their primary.
I'm not sure if this is causing the communication problem with those servers' updates and scanning schedule...?
If this is a problem, how do it correct it? I've been looking around in Symantec Site but I've found nothing helpful so far. Can someone help, please?

Thx
-selina

 

[LawnBoy]

...done by the IT manager...

Yes, that's the problem. Definitions are handed from Primary to Secondaries to clients. I can't help you here because I don't use secondary servers, but you've found the problem.

 

[selinathe1]

Well, the problem seems to be inconsistant within the server group. But I guess it's just matter of time before it spreads to all other secondary servers.
I'll find a way to correct this.
Thanks for your help!


Thx
-selina