Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Multiple and Explicit GUP

Created: 25 Mar 2013 • Updated: 25 Mar 2013 | 4 comments
This issue has been solved. See solution.

Hi - 

Our environment is operating at SEP 11. We have several branch offices having 500 to 600 workstations over  20 subnets in each branch office. We will be upgrading to SEP 12.1 RU2 very soon and are planning to have a GUP at the branch office to reduce the load on the WAN which connects our head office with the branch office. Due to infrastructure limitations, we will be able to use only one server as a GUP at each branch office. 

My idea is to create one group with a LiveUpdate Policy. The Policy will have Multiple GUP and Explicit GUP option enabled. Multiple GUP option will have rule sets that will define the IPs of all the GUPs at the branch offices. 

The Explicit GUP list will map all 20 subnets in each branch office with the GUP available in that location. This way , my guess is the clients at the branch office will be able to communicate across subnet  in the same branch office and still conserve the bandwidth over WAN. 

Kindly help me my letting me know if this idea would work and suggest any alternatives if this wouldn't work or if there is any better way of achieving this.

Operating Systems:

Comments 4 CommentsJump to latest comment

Brɨan's picture

An explicit Group Update Providers list does not turn clients into Group Update Providers. You use an explicit Group Update Provider list to map the client subnet network addresses to the Group Update Providers. With that being said, it looks like you are doing it the right way.

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

SebastianZ's picture

Yes, your configuration should be fine.

- Multiple GUP list contains as you mentioned the IPs of all available GUPs in the environment

- Explicit GUP settings contain the mapping of the available GUPs to the client subnets

Mithun Sanghavi's picture

Hello,

Check this Article: 

About the types of Group Update Providers http://www.symantec.com/docs/HOWTO80957

Explicit Group Update Providers list

You can configure an explicit list of Group Update Providers that clients can use to connect to Group Update Providers that are on subnets other than the client's subnet. Clients that change location frequently can then roam to the closest Group Update Provider on the list.

An explicit Group Update Providers list does not turn clients into Group Update Providers. You use an explicit Group Update Provider list to map the client subnet network addresses to the Group Update Providers. You identify the Group Update Providers by any of following means:

  • IP address

  • Host name

  • Subnet

Explicit Group Update Providers can be static or dynamic, depending on how you configure them. If you use an IP address or a host name to configure an explicit Group Update Provider, then it is a static Group Update Provider. This difference affects how Group Update Providers act in networks that mix legacy version clients and managers with clients and managers from the current release.

If you use a subnet to designate a Group Update Provider, it is dynamic, as clients search for a Group Update Provider on that subnet.

NOTE: This subnet is the Group Update Provider subnet network address, which is sometimes also referred to as the network prefix or network ID.

Multiple Group Update Providers list

Multiple Group Update Providers use a set of rules, or criteria, to elect themselves to serve groups of clients in their own subnets. To configure multiple Group Update Providers, you specify the criteria that client computers must meet to qualify as a Group Update Provider. You can use a host name or IP address, registry keys, or operating system as criteria. If a client computer meets the criteria, the Symantec Endpoint Protection Manager adds the client to a global list of Group Update Providers. Symantec Endpoint Protection Manager then makes the global list available to all the clients in the network. Clients check the list and choose the Group Update Providers that are located in their own subnet. Multiple Group Update Providers are dynamic Group Update Providers.

Configuring multiple Group Update Providers turns multiple clients into Group Update Providers.

Configuring single or multiple Group Update Providers in a LiveUpdate Settings policy performs the following functions:

  • It specifies which clients with this policy are to act as Group Update Providers.

  • It specifies which Group Update Provider or Providers the clients with this policy should use for content updates.

Configuring an Explicit Group Update Provider list performs only one function:

  • It specifies which Providers the clients with this policy should use for content updates. It maps Group Update Providers on subnets for use by clients on different subnets.

  • It does not specify any clients as Group Update Providers.

Although it does not turn clients into Group Update Providers, you can still configure and apply a policy that contains only an explicit provider list. However, you must then have a single Group Update Provider or multiple Group Update Providers configured in another policy in the Symantec Endpoint Protection Manager. Or, you can have both types configured in other policies.

Hope that helps!!

Mithun Sanghavi
Senior Consultant
MIM | MCSA | MCTS | STS | SSE | SSE+ | ITIL v3

Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

SOLUTION