Secondary sites are about remote locations and bandwidth usage only, not domains or political boundaries. Because of SQL replication, you also can’t include a secondary site in an untrusted domain.
Thus, your use of secondary sites should be based entirely upon your network topology, client, counts at locations, and bandwidth to those locations. J From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Burke, John Sent: Wednesday, September 14, 2016 12:44 PM To: mssms@lists.myitforum.com Subject: [mssms] 2012 and Current Branch - no need for secondary or child sites ? Hi, We run 2007 and we with a Primary and 2 child secondary sites we use for proxy management points. At the time we did this because of the slower links we didn’t want to congest. We are being told 2012 and current branch we are moving to, we can flatten it. I’m just wondering if there is no value now to secondary sites to have clients “closer” to management points anymore? We only have 7k or so. Used to have 15 to 20k clients. Larger project is going to be up to 70k clients across 3 domains. Right off top of my head I was thinking 1 primary with a secondary for each of the smaller companies and separate domains but now I’m questioning all that. Thoughts?
