Create one for assingment when you have multiple sites, if not, then just set the site at client install and the fallback site and you're done assignment wise.
For content location, you typically create one per physical location. In reality this should actually be one per connection link. As that is what you can change on a boundary group. The speed a connection has to a dp. As there is no way to have different speeds for clients behind one link, there should never be a need to make that distinction. As mentioned initially that usually comes down do physical location unless you have a bizar setup where half a building uses one link and the other half uses another one, and the speeds between both are significantly different. From: [email protected] [mailto:[email protected]] On Behalf Of Jeff Poling Sent: 17 September 2013 17:22 To: [email protected] Subject: [mssms] Boundaries and Boundary Groups 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
