I typically create one boundary group per SCCM site for automatic site assignment, and a boundary group per boundary for content location and define the appropriate DP for each of one.
Jerry From: [email protected] [mailto:[email protected]] On Behalf Of Jeff Poling Sent: Tuesday, September 17, 2013 12:22 PM To: [email protected] Subject: Re: [mssms] Boundaries and Boundary Groups Thanks to all who replied. I appreciate the sanity check! On Tue, Sep 17, 2013 at 10:53 AM, Jason Sandys <[email protected]<mailto:[email protected]>> wrote: KISS Assuming you have one DP for every one of those locations, then yes, this is perfect. There are various reason to potential add or change this up, but keeping it simply like this is generally the best route. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Ryan Sent: Tuesday, September 17, 2013 10:32 AM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] Boundaries and Boundary Groups That's what we do and it works well. On Sep 17, 2013 10:22 AM, "Jeff Poling" <[email protected]<mailto:[email protected]>> wrote: This is one of those questions for which I feel I should know the answer but am having a hard time wrapping my brain around. In CM12, how do I determine the number of boundary groups I need? I've read http://technet.microsoft.com/en-us/library/gg712679.aspx but it does not seem to give any recommendations or clues for how to determine the number of boundary groups needed. Right now, I am using the boundary group only for content and not site assignment. I have 8 remote sites that I am migrating from CM07. My current thinking is to create one boundary group that contains the AD site boundaries for each remote site. Does that make sense? Thanks, Jeff
