Endpoint Protection

 View Only
  • 1.  Explain this

    Posted May 30, 2013 08:09 AM
    1. By default, Windows is configured to allow a maximum of 5000 TCP connections simultaneously. With this configuration, the GUP is capable of serving 40 client connections per second.
    2. Windows can be configured to allow a maximum of 65534 TCP connections simultaneously. With this configuration, the GUP is capable of serving approximately 180 client connections per second.

     

     

    is this means when ever i configured GUP on my network they will update onlty 40 clients,

     

    other client will not take update 



  • 2.  RE: Explain this

    Posted May 30, 2013 08:16 AM

    here is

    Group Update Provider: Sizing and Scaling Guidelines

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

    GUP__Sizing_and_Scaling_Guidelines

    https://www-secure.symantec.com/connect/downloads/gupsizingandscalingguidelines

     

    https://www-secure.symantec.com/connect/blogs/best-practices-and-troubleshooting-group-update-providers



  • 3.  RE: Explain this

    Posted May 30, 2013 08:25 AM
    Hi, Please follow the below article, I hope this article will help you. https://www-secure.symantec.com/connect/articles/configuring-group-update-providers-symantec-endpoint-protection-110-ru5 GUP Limits https://www-secure.symantec.com/connect/forums/gup-limits


  • 4.  RE: Explain this

    Posted May 30, 2013 08:26 AM

    Very likely much less!

    The default configuration of GUPs, is that they are set to allow a "Maximum number of simultaneous downloads to clients" of 10.  So regardless of how manay Windows can handle in general, only 10 clients are allowed to download from a GUP at any one time (consistent with the TCP limitations on Windows workstation OS's).

    This is generally not a big deal however:

    If a client is unable to connect to a GUP the first time round, it'll just try again later on (up until it hits the "Maximum time that client try to download updates from a GUP before trying the default management server" time threshold if you set one).  The limitation is only for simultaneous downloads.

    This is further mitigated by the fact that these attempted downloads are affected by the heartbeat intervals and the randomisation windows, further reducing the likelihood of loads of client updating simultaneously.

    Note: The quoted items are settings within the GUP options of the LU Policy



  • 5.  RE: Explain this

    Posted May 31, 2013 08:15 AM

    HI, 

    Maximum number of simultaneous downloads to clients

    The maximum number of simultaneous downloads that the Group Update Provider distributes to clients.

    This option concerns memory and CPU utilization on the Group Update Provider computer. The option controls how many threads are allocated to handle incoming requests. Memory utilization is associated with the threads, so more threads require more memory. Also, processing the incoming requests requires CPU cycles, so more threads require more CPU cycles.

    You should tune the value to the limitations of the Group Update Provider computer. The goal is to download content updates to clients as quickly as possible, without overwhelming the Group Update Provider computer. Set the value high enough to get reasonable concurrency, but low enough to avoid overtaxing the Group Update Provider computer.

    Regards

    Ajin