Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

GUP clients not updating

Created: 02 Nov 2012 • Updated: 05 Nov 2012 | 5 comments
This issue has been solved. See solution.

I set up a remote site to pull updates from a GUP.  Those machines are not updating when in the office (the laptops appear to pull down updates from Live Update when they are not in the office).  In the event log, I see:

Event ID:  201
Source:  Symantec Endpoint Protection
Category:  Content
Desc:  Content download to the client failed
Moniker: {GUID}
Sequence:  121102020
Source:  Group Update Provider
Size:  750286

So, it looks like the client attempts to download an update from the GUP, given it has information about the update package.  But it isn't happening.  The GUP is a Windows 2003, and the clients are Windows 7.  Wrong update package?  Change to a different GUP?  Or install Live Update Administrator?

Comments 5 CommentsJump to latest comment

.Brian's picture

Any SEP client can become a GUP so OS should not matter. Ideally, you want the GUP to be on the same SEP version as the SEPM but it is not a requirement. If you can update to latest version, I would highly recommend doing that.

Have a look at this doc on GUP troubleshooting:

Troubleshooting the Group Update Provider (GUP) in Symantec Endpoint Protection (SEP)

http://www.symantec.com/business/support/index?page=content&id=TECH104539

See this thread as well:

https://www-secure.symantec.com/connect/forums/using-sep-content-distribution-monitor-troubleshoot-gups

Is the GUP reporting to the SEPM that is actually a GUP?

You can run sylink monitor and than post the logs for review.

Check this thread:

https://www-secure.symantec.com/connect/forums/problems-gup-0

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

Ian_C.'s picture

Something else to remember.

Not only do the clients need to know where the GUP is, but the potential GUP itself must know so too.

Do you have different LiveUpdate policies applied to your servers and workstations?

  • If yes. make sure that both LiveUpdate policies have got your server defined as a GUP.
  • If no, review the links posted by Brian81 above, review the SYLINK log files and test (using HTTP or telnet) if TCP port 2967 is active

Those machines are not updating when in the office

Your GUP is on the same remote site?

(the laptops appear to pull down updates from Live Update when they are not in the office)

In your LiveUpdate policy, do you have the option set to use the default Symantec LiveUpdate server? See this screen shot:

Please mark the post that best solves your problem as the answer to this thread.
SOLUTION
GSB 2's picture

Thanks Ian.  I didn't have the always on server up there as part of the managed client group.  Made it managed, and saw the sharedcontent folder appear. 

Now, since this is a server, I only installed the basic client - Just the A/V component.  Will it still update Network Threat Protection and Proactive Threat Protection on the clients? 

This is a v12.1 MP1 environment.

Thanks,
Joel

.Brian's picture

Yes, it will also update PTP and NTP content on the clients.

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

Ian_C.'s picture

Thanks Brian81, couldn't agree more.

Please mark the post that best solves your problem as the answer to this thread.