If you have a site distributed over a wide geographical area, you might find that you have problems with how clients retrieve their content. We had a situation to which I alluded here, namely a remote site downloading all its Config Manager data over a throttled WAN link.
Frankly, yuck.
Anyway as promised, I thought I’d put my thoughts into a blog relating to content access and remote sites.
My site already had two boundaries set. One for the main Config Manager geographical location (we’ll call it SCCM_Boundary1), and another for location elsewhere in the United Kingdom (SCCM_Boundary2). These geographical locations are defined in AD as AD sites, so we’ll call them AD_Site1 (main) and AD_Site2 (remote) for ease here.
Confessions of a Config Manager Engineer 