Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

SEP 11 Tips and advise for Group Updating

Created: 25 Jan 2008 • Updated: 22 May 2010 | 6 comments
I have a question. We are planning an install of Sep 11 and have about 4000 workstations spread out in about 60+ different sites.   The larger sites have about 300 workstations.  Smaller sites only 15 - 30.  
The links for the larger sites are between 4 and 2 meg.  The smaller sites have between 1 meg and 256 kbit. 
What do you guys recommend for the setup?    1 Primary server with Management console on it, and every site a Group Update server?   We will roll out the software with Altiris. 
Will this cause problems with policy changes or the workstations connecting to the root server all the time?  Anyone have experience with this?
Also i dont know where to find or how to install Group Updating tool? I cant find it on the SEP 11 cd's?
Anyone know where to find it and instructions on how to set it up.

Comments 6 CommentsJump to latest comment

Fabian-H's picture
--- >
Also i dont know where to find or how to install Group Updating tool? I cant find it on the SEP 11 cd's?
---> I think you want to use the GUP functionality... ther is no installer you have to install a normal sep client and define in the liveupdate policy this client as "GUP". The GUP defined client will cache the updates (not the policies) and the normal client will contact it for the defs.
Paul Van Dyk's picture
You do not have install any tool, it is integrated with SEP itself, you just have to Fill an IP adress which will be acting as a GUP for a paticular Group. GUP can be configured in Live Update Settings Policy
ebarcelos's picture


The Group Update Provider (GUP)is configured by LiveUpdate policies, you do not need to install any other tools to use this feature.
Each client defined as GUP can support 100 clients to download the updates, you can use multiple groups to a site that have more than 100 clients and configure each group to use a GUP client.

Refering to client's recommended that you use the Pull Mode in the following formula:
• It is recommend that setting for the heartbeat be set to no lower than the number of clients connecting to the management server divided by 1,000.
(# clients /1000 per minute)
Ex. 10,000 Clients on the Management Sever. Polling should not be set lower the 10 Minutes.


agpost's picture
Thats for your advise. 
I have a problem with the Group Updating.  I tried it and installed a package created on the main server.  IT has a policy to point it to the Group Upd server instead of the other for updates.   After it installed it was in the correct Policy group but still downloaded the updates from the main liveupdate server ignoring the Group update server.  
Any ideas?  I did configure the policy correct according to the manual..
fjorq's picture
Hi - I was wondering if someone has configured or if it would be possible to use a GUP to update large sites (over 250 systems) in the following manner:
1. Configure a DNS entry to resolve to 2 or 3 systems (GUPs)
2. In SEP, configure the GUP to use the DNS entry instead of an IP address....
This can help aleviate the need of only one GUP updating over 100 systems and would also workaround the need to split large sites into several groups to assign a GUP to each...
If you have tried this, I'd like to get your opinion...
Wayne Sheldon's picture

Its a nice idea, but I dont think it will work.

The GUP itself has to know its a GUP and it will probably resolve the address as one of the other machines 50-66% of the time, and therefore stop distributing updates.