Video Screencast Help

SEP11 not updating, green dot showing, using GUP.

Created: 13 Apr 2009 • Updated: 21 May 2010 | 4 comments

Hi there,
             We have deployed SEP11 around our estate, hundreds of servers and thousands of workstations. We're also using GUPs to reduce bandwidth requirements.

I have 1 server that isn't updating its virus definitions. It has the green dot on the SEP shield so we know it can contact SEPM (and SEPM shows it as a client) but it will not update the defs. When i go to Help and Support --> Troubleshooting it doesn't show me the server info (it's all blank).
imagebrowser image

I would have expected the green dot not to show on the shield but it does. I can telnet on port 80 to the SEPM server using its FQDN and IP, and I can telnet to port 2967 on local GUP using FQDN and IP as well.

The Sylink monitor tool doesn't appear to give me much info either. Additionally, no proxy servers are specified in IE settings,and I've remove the proxy registry settings just to be sure.
The troubleshooting data shows the following (I don't want to post all of it here as I imagine it'll just clutter up this post even more):

Engines
-------
SymEvent:  12.5.3.2
Auto-Protect Kernel Driver:  10.2.7.10
Auto-Protect User Mode Interface:  10.2.7.11
LiveUpdate:  3.3.0.69
Common Client:  106.3.7.9
Decomposer:
Tamper Protection:  3.3.7.3
Eraser:  0.0

Any help much appreciated!

Ally

Comments 4 CommentsJump to latest comment

Aniket Amdekar's picture

As you said that you can see a green dot on the client, which means that it should be able to retrieve the latest policy from SEPM. For testing purpose, you can enable/disable the liveupdate button the client interface using SEPM policies, and see if that change takes effect.

I suspect that the Sylink.xml file is corrupt. You may try to replace the file and see if the information is updated.

If its an issue with corrupt installtion, then you can run a repair install, and see if the issue gets resolved. If it dosent, then you should redeploy the client package on that server and see if the information is updated.