Endpoint Protection Small Business Edition

 View Only
  • 1.  GUP support

    Posted Jun 26, 2015 11:49 AM

    Hi,

     

    I have one computer with Windows Server 2008 with SEP client installed => name: GUP01

    I have one computer with Windows Server 2008 with SEPM installed => name: XPTO

     

    - I created one policy in SEPM and I configured to use GUP (GUP01)

    - I created one group and moved some computers to this group. In this group I associated the policy that I created to use GUP

     

    The update from GUP01 is not working, in the monitors logs in SEPM: 

    SYLINK - Failed to connect to all GUPs, now trying to connect SEPM 

     

    In computer GUP01 my netstat -an I can't see the post 2967

     

    In the policy in "Configure Group Update Provider List" at SEPM I tried:

    XPTO

    XPTO.com

    IP address

     

    I don't know what I have to do to work my GUP.

    In the file globallist in C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\data\outbox\agent\gup does not have the ip address that I configured in the policy.

     



  • 2.  RE: GUP support

    Posted Jun 26, 2015 11:51 AM


  • 3.  RE: GUP support

    Posted Jun 26, 2015 11:58 AM
    Seems like your gup01 did not receive the policy.. Is your gap talking to sepm? Do you see the shared folder being created on GUp01


  • 4.  RE: GUP support

    Posted Jun 26, 2015 01:04 PM

    2967 is not allowed.

    Windows firewall on GUP: OFF

    GUP computer is clean and I installed only SEP client



  • 5.  RE: GUP support

    Posted Jun 26, 2015 01:06 PM

    I can see in clients in SEPM the GUP computer.

     

    "Do you see the shared folder being created on GUp01"

    How I can see this?



  • 6.  RE: GUP support

    Posted Jun 26, 2015 01:10 PM

    Clients need to be able to talk to the GUP over 2967



  • 7.  RE: GUP support
    Best Answer

    Posted Jun 26, 2015 01:16 PM

    The reason is that the GUP01 should be assigned as a GUP for itself. If the GUP01 is configured to get updates only from SEPM, it won't become a GUP at all.

     

    Solution: Either move the "GUP01" machine to the group in which you have configured the clients to user "GUP01" as GUP. OR . Assign the same police (in which you have the set "GUP01" as GUP) to the group in which the "GUP01" machine is reporting to SEPM.



  • 8.  RE: GUP support

    Posted Jun 26, 2015 01:50 PM

    I moved GUP01 to the same group that I applicated the policy and now its ok...2967 is allowed and now I can access http://gup01:2967/content/contentinfo.txt from SEP client.

    How can I test the SEP update?



  • 9.  RE: GUP support

    Posted Jun 26, 2015 02:06 PM

    Wait for some time and then check the system log on a client which is supposed to download the update from GUP01. The log should say that the new definitions are downloaded from "Group Update provider".