Endpoint Protection

In the city A I have a SEPM. In others cities I have about 17000 SEP clients. Recently, I've installed in the city B about 300 SEP clients with their own LU Server.

After that, the network has been saturated because the SEP clients of the city B are consulting continually the SEPM in the city A. How can resolve this problem?

Configure a GUP at City B. Once you have a GUP at B only one client will come to City A to take the update. That will update all clients at City B, Thus saving the network Bandwidth



Title: 'Symantec Endpoint Protection 11.0 Group Update Provider (GUP)'
Document ID: 2007092720522748
> Web URL: http://service1.symantec.com/support/ent-security.nsf/docid/2007092720522748?Open&seg=ent

Title: 'Configuring the Group Update Provider (GUP) in Symantec Endpoint Protection 11.0 RU5'
Document ID: 2009092901593448
> Web URL: http://service1.symantec.com/support/ent-security.nsf/docid/2009092901593448?Open&seg=ent
 
 

 
https://www-secure.symantec.com/connect/videos/group-update-providers-part-1#new
 
https://www-secure.symantec.com/connect/videos/group-update-providers-part-2

Check this article

Title: 'How To Optimize Endpoint Protection for Branch Offices using GUPs, Load Balancing, and Location Awareness'
Web URL: http://service1.symantec.com/support/ent-security.nsf/docid/2009052116101548?Open&seg=ent

Make sure your GUP has at least 20-30 versions of the defs, as well as your SEPM.

If Symantec makes certified defs every 4-5 hours, that means 4-5 downloads a day.  The default setting is 3 to save in the SEPM.

If a machine is off for more than a day, the client machine will reach out to the SEPM for a full def package.  That is over 100MB.  Times that by your 17000 clients.

So, keep enough cached copies of your defs at the edge where it will make a HUGE difference for folks that have left their machines off over the weekend, and not kill the network upon start up.