Video Screencast Help

Remote GUPs / Multiple GUPs

Created: 18 Mar 2013 • Updated: 17 Sep 2014 | 5 comments
This issue has been solved. See solution.


We have a large environment where we would like to do the following:

  1. Create a group that has all of the GUPs
  2. Those gups should be assigned to other groups that has clients (we name our groups as locations)

Can this be done or the gups have to be in the same group as the clients?  If this can be done, can anyone suggest a good reading?

Operating Systems:

Comments 5 CommentsJump to latest comment

ᗺrian's picture

You would need to create a policy to define the GUPs and than apply to the groups.

If using 12.1.2, than you use the explicit GUP. You can create one policy and add all your GUPs to it than apply.

Understanding "Explicit Group Update Providers (GUPs) for Roaming Clients" in Symantec Endpoint Protection (SEP) 12.1.2

padding: 1px;padding-bottom: 3px ;font: 12px Arial; text-align: left;">Article:TECH198640 padding: 1px;font: 12px Arial; text-align: left;"> |  padding: 0px;font: 12px Arial; text-align: left;">Created: 2012-10-19 padding: 1px;font: 12px Arial; text-align: left;"> |  padding: 1px;font: 12px Arial; text-align: left;">Updated: 2012-11-15 padding: 1px;font: 12px Arial; text-align: left;"> |  padding: 1px;font: 12px Arial; text-align: left;">Article URL

The tool here from Elisha will help you create it quickly:

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.

consoleadmin's picture

You can assign the policy of on that group where you need to define.

Best Practices with Symantec Endpoint Protection (SEP) Group Update Providers (GUP)
Article:TECH93813  |  Created: 2009-01-05  |  Updated: 2012-01-31  |  Article URL
Group Update Provider: Sizing and Scaling Guidelines
Article:TECH95353  |  Created: 2009-01-03  |  Updated: 2010-01-31  |  Article URL


Rafeeq's picture

Earlier it has to be in the same group, but now its changed. client can update any subnet.

Mithun Sanghavi's picture


Yes, it surely could be done.

In SEP 11.0.RU5 or later (including SEP 12.1), any client that identifies itself to SEPM as a GUP will be added to the globallist.xml, regardless of whether they were configured as Single or Multiple GUP initially.

This globallist will be presented to clients that are configured to use a GUP. This list is applied in ascending order by the client, so if the IP Addresses are in the same subnet as the requesting client, the first one on the list will be used by that client.

In this design, clients will only attempt to contact GUPs in their own local subnet. These GUPs will never cross a router or a gateway, so if there is a router or a gateway in between the two networks then clients will only use the local GUP.

I would suggest you to check this Article:

About the types of Group Update Providers

Hope that helps!!

Mithun Sanghavi
Associate Security Architect


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

Riya31's picture

To assign GUP(Which are in one group) to each location

Define a liveupdate policy with multiple GUP and assign it to all groups(location). 

Note:-Ensure that you have define GUP in each subnet.