The main use of fast/slow is for defining VPN locations. Using the fast/slow setting, the client determines that it shouldn't download the content at all based on the content's setting. So, for example, if a client connects via VPN and they Office deployed, the client will see that it is connected via a slow link and the content is set to not download over a slow link which is a good thing for slow links.
So it's always a combination of the client's link and the setting of any applicable content. There are of course other possibilities for slow links, but VPN is an easy one to identify and characterize. J From: [email protected] [mailto:[email protected]] On Behalf Of Mike Hammond Sent: Tuesday, August 20, 2013 9:17 AM To: [email protected] Subject: [mssms] Boundaries/Boundary Groups/Connection Speed Hi All, I'm coming up to speed on SCCM 2012, and have little to no understanding of the predecessor versions of SMS and SCCM. I'm struggling to understand the impact of the Fast/Slow connection idea on the design of boundaries and boundary groups. Documentation I've read on the Fast/Slow configuration setting seems vague and confusing. Can you recommend a best source for explanation of this topic? Ideally, I'd like to see a case study describing a network architecture, with illustration of how boundaries, boundary groups, and the Fast/Slow setting was used in various locations in that network. Best regards, Mike -------------------------------------------------------------------------------------------------------------------------------- Michael Hammond, MCT, MCITP:SA, MCITP:EA, MCSE, MCAD, MCDBA 2-Time Award-Winning* PowerShell Scripter President, Abacus Technical Services Phone: 630-945-MIKE (6453) *Well... sort of
