If all of your boundaries are configured properly, and the content exists on each DP, then yes, the clients should only download content from their local DP. When a TS runs, it validates that all associated content is available on its assigned DP(s), but If content is missing from a client's DP, the Task Sequence will fail before it starts to run and tell you what content is missing.
There is an option you can select when created the TS deployment labeled, "Allow Clients to use a fallback location for content". Just be sure this is not selected. Thanks, Jerry From: [email protected] [mailto:[email protected]] On Behalf Of Mawdsley R. Sent: Tuesday, February 23, 2016 6:06 AM To: [email protected] Subject: [mssms] Building machine at Remote Sites - Boundaries & DP's Morning all, I'm currently moving our MDT builds into SCCM, and 1 challenge I face is building machines at our remote sites. We currently have a distribution point groups for Main Site and for remote sites. Each remote site has its own DP. Boundaries are configured to ensure clients in there retrospective locations talk to their local DP. Network links to these remote sites are not great so fallback, for osd a least is not an option. Currently, OSD packages are not distributed to Remote Sites, and are only distributed to Main Site. So based on that, if I simply distribute content to the Remote Sites DP's, will the clients honour their boundary's (based on AD sites) whilst building and only pull content from their local DP? Thankyou Rich ------------------------------------- Rich Mawdsley Software & Desktop Services iSolutions University of Southampton -------------------------------------
