Video Screencast Help

Replication sites for computers

Created: 15 Feb 2013 | 7 comments

Hi I have a client that will implement Symatec Endpoint.  There have a WAN with 14 remote sites all connected with a 2Mb data link.  I will like to implement Replication server or sites so each remote computer look and see for updates and policies is on replication server instead of going to the mail office where the SEPM server is.  Can this be done?  Thanks.

Comments 7 CommentsJump to latest comment

Ashish-Sharma's picture
The Philosophy of SEPM Replication Setup


Article:TECH93107 | Created: 2009-01-26 | Updated: 2012-06-01 | Article URL


How replication works

Article:HOWTO81035 | Created: 2012-10-24 | Updated: 2013-01-30 | Article URL


1) About installing and configuring Symantec Endpoint Protection Manager for replication

2) Installing Symantec Endpoint Protection Manager for replication
3) What is Management Server List and how to configure Failover between replication partners using embedded database.

Thanks In Advance

Ashish Sharma

ᗺrian's picture

You could set them up to replicate. You can than also setup a GUP at each remote site to provide contents to clients on each local LAN so they don't have to come back to the SEPM for updates, which will conserve on bandwidth

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

pete_4u2002's picture

14 sites is too many. 5 sites can be replicated as per best practies. Suggest to have GUP at other sites.

Mithun Sanghavi's picture


I would try my level best to get things under one umbrella..

There are various ways for Managing SEPM across WAN network.

Before we proceed, please Check this:

Top 10 Symantec Best Practices - Deploying Symantec Endpoint Protection Architecture

There are many methods. You need to understand what is the soul purpose.

Here are the various ways:

1) Replication - Replicate Sites

  • The Philosophy of SEPM Replication Setup

  • How to install the Symantec Endpoint Protection Manager(s) for replication

2) Failover -  

Where Symantec Endpoint Protection Manager (SEPM) servers are assigned a priority so that if the primary SEPM goes down, the clients know to contact a secondary SEPM.

About failover and load balancing

About Load Balancing and Failover Clustering in Symantec Endpoint Protection 11.0

3) Group Update Provider - used for updating SEP clients across sites.

How To Optimize Endpoint Protection for Branch Offices using GUPs, Load Balancing, and Location Awareness

4) Simple managing multiple SEPM from IE with the help of Dashboard. 

How do I access the Symantec Protection Center?

Logging on to the Symantec Protection Center Dashboard in Symantec Endpoint Protection RU6

How to delete a product from RU6 Dashboard/portal? 

Also, check this:

Multiple office WAN infrastructure best practices

Hope that helps!!

Mithun Sanghavi
Associate Security Architect


Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

ccotto's picture

Thanks for the information, I think that for what we need using the GUP should do the work.  I will check the information on how to setup up.

A. Wesker's picture

Replication with WAN performance is a bit dodgy.

Replication is fair especially with big sites. If you have 14 remote sites where finally there are few clients (I mean less than 1.000), you could forget replication completely.

Replication for small sites is absolutely not fair. Do not forget that replication can use somewhat bandwidth and especially the first one as it's all the db, group and policies which are getting replication.

Even the first replication may completely fail with WAN performance. A short time out may make the replication impossible to be completed.

For this reason I join at 100% the advice from Brian81. Setting GUP is absolutely the best way to go for your situation.

Configuring the Group Update Provider (GUP) in Symantec Endpoint Protection 11.0 RU5 and later


Kind Regards,

A. Wesker