Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Clients not updating 3

Status
Not open for further replies.

ksweeney

IS-IT--Management
Oct 5, 2006
8
0
0
US
We have about 1,000 PC on the network with Symantec 10.5.5000 Corporate Edition supplying updates. However, about 150 are not getting updates even though it can see the server. No error messages; the PC's just go on their merry way and we're not sure we are seeing all the PC's in the Syamntec console.

Any advice appreciated.
Kevin Sweeney
 
Check the ocal clients to see if they can run LiveUpdate - if they can't, something may have been corrupted on the clients.

May a;so try republishing the GRC.DAT and restarting SAVRT on the clients.

There's an older tool on he CD (maybe only on version 9) media called GRCDROP that can help.


Were any of the clients upgraded from a pre-10 version recently?
 
Most were upgraded but about 50 were imaged with 10.
Thank you for the other suggestions. We are researching them now.

Kevin Sweeney
 
One thing to check for is to make sure the log files haven't filled the hard drive on the server - I've run into that once or twice (that's what I get for not using big drives).
 
A couple of suggestions:

- Make sure that those 150 clients are showing up in the Symantec System Center
- Make sure that all the clients have a valid root certificate in the following folder:

C:\Program Files\Symantec Client Security\Symantec AntiVirus\pki\roots

(The clients generally do not show up without a valid certificate)

- If you are running any type of firewall (even the Windows firewall), please make sure that you create a FILE exclusion for the RTVSCAN.EXE binary in "C:\Program Files\Symantec Client Security\Symantec AntiVirus".

Since SAV 10.1 is TCP based, you can also do some basic connectivity troubleshooting:

- From <server> telnet to <client> "telnet <client_IP> 2967"
- From <client> telnet to <server> "telnet <server IP> 2967"

You should at least be able to 'connect' to port 2967 on the client and vice versa from the server.

Hope that gets you going.

Oggywan
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top