Best practices for Group Update Provider (GUP) from Symantec Endpoint Protection MR3 or earlier builds
|Article:TECH105652|||||Created: 2008-01-18|||||Updated: 2013-11-06|||||Article URL http://www.symantec.com/docs/TECH105652|
You would like recommendations on how to configure GUP's within the Symantec Endpoint Protection Manager MR3 or earlier builds to help preserve LAN and WAN bandwidth and to provide most reliable performance.
The following suggestions will help the overall efficiency and performance of the GUP's to preserve network bandwidth:
- Ensure MR3 or later is running on both Symantec Endpoint Protection clients and Symantec Endpoint Protection Managers
- MR2-MP2 and earlier GUP can only handle up to 100 Symantec Endpoint Protection clients. MR3 GUP now officially supports up to 1000 Symantec Endpoint Protection clients
- For a high number of Symantec Endpoint Protection clients, it is recommended to run the GUP on a Windows Server due to the limits of concurrent TCP connections in Windows XP and Vista.
- A client operating system (Windows XP, Vista or Win7) can be used as a GUP for 100 machines but if the number of clients are more than 100, the best practice would be to use a server operating system.
- Ensure all GUP's have their thread count increased to at least 10 (This functionality was added in MR3 or later)
- Configure all SEP clients to use PULL mode and heartbeat every 60 minutes or longer
- Configure 1 specific Symantec Endpoint Protection client (GUP) on same LAN as Symantec Endpoint Protection Manager to heartbeat every 2 minutes
- Create a group specifically for this one Symantec Endpoint Protection client. (This is for configuration, tracking and organizational purposes).
- Symantec Endpoint Protection Manager starts to build needed deltas in advance for most Symantec Endpoint Protection clients and GUP's connecting looking for specific delta files.
Article URL http://www.symantec.com/docs/TECH105652