Throttling Bandwidth with SEPM

[Migration User]

Hello Team,
I have a fairly large enviornment, and bandwidth is an issue when pushing out to clients.
Is there a way to throttle bandwidth for SEP communication and pushes?

Thanks, 

[Migration User]

You  can change the commuincation mode and the Heartbeat interval

Modify the default communication settings:

1. Click the Clients Tab.
2. Select the client group you would like to modify.
3. Click the Policies tab.
4. If this is not the Global group, uncheck Inherit policies and settings from parent group. Ensure that Policy inheritance is OFF.
5. Under Location-independent Policies and Settings, with in the Settings box, click Communications Settings.
6. In the Download box select Pull mode.
7. Modify the default Heartbeat Interval from "5 minutes" to fit your needs. This modifies how often clients check-in with the manager to receive policies, settings, and content (definition) updates.
8. Click OK to save settings.
9.  
10. http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007102311173048

Also you can configre GUP

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


Title: 'How to throttle network bandwidth used by the Endpoint Protection Manager (SEPM) website in Microsoft's Internet Information Server (IIS)'
Document ID: 2008032806522248
> Web URL: http://service1.symantec.com/support/ent-security.nsf/docid/2008032806522248?Open&seg=ent

[Migration User]

I would also recommend dropping your definition updated down to once per day rather than the default of three times per day.
The benefit of triple daily definitions is outweighed heavily by 2/3 less bandwidth utilisation in large client sites.

Also make sure that when you push new packages out to clients for SEP installation that they contain the latest defintions:
http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/c7a72ad01d122b13882574330072026a?OpenDocument

GUP usage should be considered with at least one GUP on each remote subnet.

Z

[Migration User]

Perfect!
Thank you!
:)
Tommy 

[Migration User]

one other thing to try would be in IIS to limit the bandwidth.   I tried this when I was having a bandwidth issue several versions back and it sort of worked.   As others have stated GUP's are the best way to help control bandwidth in branch offices.

[postechgeek]

Xiao_Tommy,

We use GUPs here. Our SEPM is located at our datacenter, and we have GUPs setup in each of our three facilities.
What I did was create three groups (one for each facility) and three non-shared liveupdate policies. The setup has helped treamdously with bandwidth issues. 

Make sure you when you define a GUP to choose a computer with a server OS, so that you have unlimited connections. Also, hopefully in a future MR release we will be able to get client updates through the GUPs. How cool would that be?


Mike