Overview of boundaries and boundary groups
Applies to: Configuration Manager (current branch)
Boundaries in Configuration Manager define network locations on your intranet. These locations include devices that you want to manage. Boundary groups are logical groups of boundaries that you configure. A hierarchy can include any number of boundary groups. Each boundary group can contain any combination of the following boundary types:
- IP subnet
- Active Directory site name
- IPv6 prefix
- IP address range
- VPN (starting in version 2006)
Clients on the intranet evaluate their current network location and then use that information to identify boundary groups to which they belong.
Clients use boundary groups to:
Find an assigned site: Boundary groups enable clients to find a primary site for client assignment. This behavior is also known as automatic site assignment.
Find certain site system roles they can use: Associate a boundary group with certain site system roles. Then the site provides clients with that list of site systems in the boundary group. Clients use these site systems for actions such as finding content or a nearby management point.
Clients that are on the internet or configured as internet-only clients don't use boundary information. These clients can't use automatic site assignment. They can download content from an internet-based distribution point from their assigned site or a content-enabled cloud management gateway.
During OS deployment, while a device is running Windows PE, the site can convert Active Directory site boundary information to IP subnet information. This behavior is only during this process, and specifically for these devices. In other words, if your site only has Active Directory site boundaries, Windows PE clients during an OS deployment will still be in a boundary.
Overlapping boundaries
Configuration Manager supports overlapping boundary and boundary group configurations for content and service location requests. Overlapping occurs when a client's location maps to multiple boundary groups. This behavior happens for one of two reasons:
You add the same boundary to multiple boundary groups.
You add separate boundaries that include the client's location to different boundary groups.
When overlapping occurs, Configuration Manager creates a list of all site systems referenced by all boundary groups that include a client's location. Configuration Manager sends this list to a client in response to a content or service location request. Configuration Manager doesn't apply any precedence or deterministic ordering to this list based on overlapping boundaries and boundary groups. Instead, the client chooses at random from this list.
For client content requests, Configuration Manager includes only distribution points that have the requested content in the list of site systems returned. For other service location requests, Configuration Manager includes only site systems that host the type of role requested which may be one of the following roles:
State migration point
Software update point
Management point
This behavior enables the client to select the nearest server to communicate with for each request type.
Recommendations
Use a mix of the fewest boundaries that meet your needs
Use whichever boundary type or types you choose that work for your environment. To simplify your management tasks, use boundary types that let you use the fewest number of boundaries you can.
Avoid overlapping boundaries for automatic site assignment
Although each boundary group supports both site assignment and site system reference, create a separate set of boundary groups to use only for site assignment. Make sure that each boundary in a boundary group isn't a member of another boundary group with a different site assignment.
A single boundary can be included in multiple boundary groups.
Each boundary group can be associated with a different primary site for site assignment.
For a boundary that's a member of two different boundary groups with different site assignments, clients randomly select a site to join. This behavior might not be for the site you want the client to join. This configuration is called overlapping boundaries.
Overlapping boundaries aren't a problem for content location. It can be a useful configuration that provides clients more resources or content locations they can use.
For more information on boundary groups and site assignment, see Site assignment.