Endpoint Protection

 View Only
Expand all | Collapse all

GUP Problems clients not updating

  • 1.  GUP Problems clients not updating

    Posted Dec 31, 2009 10:08 AM

    We are currently running version 11.0.4202. I have configured a GUP via a sep policy and applied it to a group. I have made the appropriate firewall change allowing traffic on tcp port 2967 on both the clients and the GUP. I have tried to verify connection on the clients by checking the GUProxy.log. 
    This log is completely empty 0KB. What am I missing? Do you have to do anything to the GUP to tell it that it is a GUP? Doesn't the policy do that? Any help you guys can give is appreciated.  



  • 2.  RE: GUP Problems clients not updating



  • 3.  RE: GUP Problems clients not updating

    Posted Dec 31, 2009 10:49 AM

    Versions prior to RU5 require that the GUP is in the same group as the clients.  Is this the case in your scenario?  As Sandip_Sali mentioned, RU5 has a number of new improvements/features for GUPs.  I'd highly recommend upgrading if at all possible.  The caveat is that all clients must be RU5 to get that new functionality.



  • 4.  RE: GUP Problems clients not updating

    Posted Dec 31, 2009 11:11 AM
    I'm not sure that they have to be in the same group. According to the SEP11 Frequently Asked Questions File "one GUP can be assigned to multiple groups (OUs)." If I'm reading that correctly then the gup doesn't have to be in the same group.

    Thoughts?


  • 5.  RE: GUP Problems clients not updating

    Posted Dec 31, 2009 11:21 AM
    That is for RU5. Prior versions the Gup should be in the same group. At the very least the Gup needs to have the same liveupdate policy as the clients you want the GUP to serve. And usually in a gup scenerio you would have multiple groups for different sites. Therefore you would need multiple liveupdate policies. I hope this clears anything up.


  • 6.  RE: GUP Problems clients not updating

    Posted Dec 31, 2009 03:10 PM
    The GUP is in the group that I want it to update. It has the Live update policy applied to that group making it a GUP. I have verified from program files\symantec\symantec endpoint protection\shared updates that it has downloaded content throughout today. The other client computers in that group still have a blank GUProxy.log files. Am I wrong that this file should change to reflect the GUP or does this file stay empty?


  • 7.  RE: GUP Problems clients not updating

    Posted Dec 31, 2009 03:15 PM
    And the GUP and other clients are in the same subnet too?


  • 8.  RE: GUP Problems clients not updating

    Posted Dec 31, 2009 04:02 PM
    Yes, they are in the same subnet. I don't get what I'm missing here.


  • 9.  RE: GUP Problems clients not updating

    Posted Dec 31, 2009 04:36 PM

    I'm not sure about the GUProxy.log file.  You may have to start digging into the debug.log and sylink.log files.  The article below is really helpful for enabling and checking these logs, plus reg keys to see where the problem may be:

    http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/7f020ee38fbb30238825741e00701b8c?OpenDocument



  • 10.  RE: GUP Problems clients not updating

    Posted Jan 02, 2010 07:58 AM
    The GUProxy.log file wont update, I dont think.

    Clients dont need to be in the same group, asumming you are using computer names for the GUPs, they do need to share the same policies.

    If you have SharedUpdates appearing then thats half the battle as it means the GUP is requesting content from the SEPM.  Are your remote clients not updating?



  • 11.  RE: GUP Problems clients not updating

    Broadcom Employee
    Posted Jan 04, 2010 01:20 AM
    runthe sylinkmonitor logs on the client machine , which is supposed to get teh updates from the gup and post the logs.

    The logs will have information for the communication with GUP and if any failure for the updates.