How do you setup a Group Update Provider (GUP)? Client machines at remote locations are overwhelming network bandwidth to obtain updates.
High and/or Excessive Network Traffic.
Many clients get content updates from the Symantec Endpoint Protection Manager (SEPM) at the same time. Bandwidth required for content updates is greater than the available bandwidth.
How To: Setup a GUP:
On the console, click Policies.
In the View Policies pane, click LiveUpdate.
In the LiveUpdate Policies pane, on the LiveUpdate Settings tab, under Name, select the policy to edit.
In the Tasks pane, click Edit the Policy.
In the LiveUpdate Settings Policy window, click Server Settings.
In Server Settings, check the box 'Use a Group Update Provider'.
Click the 'Group Update Provider' button.
In the Group Update Provider dialog box, type an IP address or a host name.
Set Maximum disk cache size allowed for downloading updates to 2048 MB.
Click OK to close the Group Update Provider editor window.
Click OK to close and save the Policy.
Review the other settings, accept or change the defaults, and then click OK.
Note: The computer that you select as the GUP must have a LiveUpdate policy that defines it as a GUP. The Clients a GUP serves must have a policy that points to their GUP. Note: If the Group Update Provider runs a Firewall, you must modify the Firewall policy to receive communications on TCP port 2967.
GUP Update: GUP functionality was greatly improved in 11.0.5 and will continue to be developed. There are many options for GUPs including: throttling, failover, content revision limits and much more. Please refer to the Help buttons in the SEPM Console and our Administration_Guide.PDF for additional information.
Network with a low bandwidth.
Multiple remote sites that aren't large enough to justify their own SEPM.
Rate this Article
This is machine translated content
Login to Subscribe
Please login to set up your subscription.
Didn't find the article you were looking for? Try these resources.