Endpoint Protection Small Business Edition

 View Only

  • 1.  Computers not assigning themselves as a GUP

    Posted Apr 03, 2014 08:31 AM

    Hi.  I just installed 12.1.4 on another external site.  I set this one up as I have many others.  For the GUP option I used "multiple gups" and called out 4 pcs by HOSTNAME.  

    Today when I look on those pcs in my SEPM...right click the client and "edit properites"....3 of the 4 GUPs have "false" listed as the property for the "group update provider"

    Anyone see this before?  I did an "update content" on the GUP clients but all are still not seeing themselves as GUPs.



  • 2.  RE: Computers not assigning themselves as a GUP

    Posted Apr 03, 2014 08:40 AM

    They pulled the updated policy (and reporting into SEPM?)

    If you check the client System log, does it say anything about becoming a GUP? Does it have the SharedUpdates folder on it?



  • 3.  RE: Computers not assigning themselves as a GUP

    Posted Apr 03, 2014 10:37 AM

    All the computers have the updated policy.  Now 3 of 4 recognize themselves as GUP's.  

    The last one does not have the "shared updates folder"

    Am I able to view the "system log" for that computer from SEPM?  I am trying to find the setting in MONITORS but not having luck.



  • 4.  RE: Computers not assigning themselves as a GUP

    Posted Apr 03, 2014 10:40 AM

    See if this article helps:

    https://www-secure.symantec.com/connect/articles/sepm-121-advanced-settings-filter-options-client-activity-logs

    You may be able to use the keyword "sylink" or "smc" to find it from the SEPM