Minimizing network traffic from client-to-server communications in Symantec Endpoint Protection Manager 12.1
|Article:TECH164737|||||Created: 2011-07-15|||||Updated: 2014-09-25|||||Article URL http://www.symantec.com/docs/TECH164737|
Symantec Endpoint Protection (SEP) clients communicate with the Symantec Endpoint Protection Manager (SEPM) via an Apache Web server. SEPM 11.x utilized Microsoft's Internet Information Services (IIS) server for this same functionality.
In SEPM 11.x, it is possible to throttle client-to-SEPM communications using IIS configuration changes. Is the same throttling possible through Apache?
SEPM version 12.1.5 and later include Mod_bw for Apache which can be used to manage client bandwidth:
Symantec Endpoint Protection Bandwidth Control for Client Communication
No method exists to throttle client/server bandwidth usage directly through the SEPM Apache server for versions 12.1.4 and older. The majority of the bandwidth the SEPM uses is for client content updates. Minimize the network load for these updates using one of the following methods:
- Increase the interval between SEP client checkins to lower SEPM server load
- Add one or more Group Update Providers (GUPs) to distribute bandwidth usage
- Ensure that the SEPM is hosting sufficient content revisions. This allows deltas to be created for out-of-date clients instead of full content packages
Article URL http://www.symantec.com/docs/TECH164737