If endpoints are dispersed across different regions and each region must have local SEPM console access, if the WAN link between the regional site(s) and the central site goes down, local teams can still access a local SEPM console at each region.
If a regional site contains over 10,000 endpoints, a SEPM site (SEPM and database) may be more suitable than utilizing the Group Update Provider functionality. The other alternative is to set up a LUA 2.x distribution center.
If you will implement replication:
Minimize the number of sites you will replicate between (consider whether using the Group Update Provider functionality would make more sense at any of these sites)
Note: Best practice is to keep the number of replicated sites ideally below 5, and it is strongly recommended to not go over 20 replicated sites.
Do not replicate content and client packages. Best practice is to have each SEPM site retrieve its content updates from Symantec Liveupdate on the Internet.
Where possible, if replicating logging data, ensure this occurs in only one direction (e.g. 3 regional SEPM sites forwarding logging on one way to central SEPM site).
Do not replicate more frequently than once per hour.
If more than 3 SEPM sites are replicating, no more frequently than once per day is recommended (with the scheduled replication times during the day selected so they don’t overlap with either another site replication or a scheduled Liveupdate session).