Plan and Configure Boundaries

Plan and Configure Boundaries We will start our configuration with the SCCM boundaries. First, let’s define what a boundary in SCCM is :

From Technet :

In MEMCM/SCCM, a boundary is a network location on the intranet that can contain one or more devices that you want to manage. Boundaries can be an IP subnet, Active Directory site name, IPv6 Prefix, or an IP address range, and the hierarchy can include any combination of these boundary types. To use a boundary, you must add the boundary to one or more boundary groups. Boundary groups are collections of boundaries. By using boundary groups, clients on the intranet can find an assigned site and locate content when they have to install software, such as applications, software updates, and operating system images.
A boundary does not enable clients to be managed at the network location. To manage a client, the boundary must be a member of a boundary group. Simple Boundaries on do nothing, they must be added to one or more boundary groups in order to work.

A boundary group is self-explanatory, it’s a group of boundaries used for site assignment and for content location. Beginning with SCCM 2012 R2 SP1, a boundary group can direct your clients to their Distribution Points for content, State Migration Point, Preferred Management Point and Software Update Point. Prior to R2 SP1, Content location is used by client to identify available Distribution Points or State Migration Point based on the client network location.

To resume :

• Site Assignment boundary group associate a resource to a site
• Content Location boundary group is used to retrieve its deployment content (applications, packages, images, etc)

PLANNING FOR SCCM BOUNDARIES AND BOUNDARY GROUPS

Before designing your strategy choose wisely on which boundary type to use.

If you’re unsure of which type of boundary to use you can read Jason Sandys excellent post about why you shouldn’t use IP Subnet boundaries.

Microsoft recommends the following :

• When designing your boundary strategy, we recommend you use boundaries that are based on Active Directory sites before using other boundary types. Where boundaries based on Active Directory sites are not an option, then use IP subnet or IPv6 boundaries. If none of these options are available to you, then leverage IP address range boundaries. This is because the site evaluates boundary members periodically, and the query required to assess members of an IP address range requires a substantially larger use of SQL Server resources than queries that assess members of other boundary types
• It’s also recommended to split your Site Assignment and Content location group

OVERLAPPING BOUNDARIES

SCCM Current Branch supports overlapping boundary configurations for content location.

When a client requests content, and the client network location belongs to multiple boundary groups, Configuration Manager sends the client a list of all Distribution Points that have the content.

This behavior enables the client to select the nearest server from which to transfer the content or state migration information.

REAL WORLD SCENARIO

In our various SCCM installations, our clients are often confused about this topic. Let’s make an example to help you understand :

• Contoso has 1000 clients
• 1 Primary Site (Montreal)
• 3 remote offices with their local Distribution Point (New York, Chicago, Los Angeles)
• Active Directory Site are based on their site subnets (MTL,NY,CHI,LA)

In that scenario, we need to create 4 Boundary, 1 for each office :

• Open the SCCM Console
• Go to Administration / Hierarchy Configuration / Boundary

Right-click Boundaries and select Create Boundary

CREATE BOUNDARY GROUP

Now, we’ll create a Site Assignment Boundary Group and add all those AD Site. That way, all my clients for my 4 locations will be assigned to my Montreal Primary Site.
For Content Location, we want clients to get their content locally at their respective location. We will create 4 Content Boundary groups, add only their AD Site Boundary and assign their local Distribution Point.

Here’s how to make this happen in SCCM :

• Open the SCCM Console
• Go to Administration / Hierarchy Configuration / Boundary Groups
• Right-click Boundary Groups and select Create Boundary Groups

CREATE SITE ASSIGNEMENT BOUNDARY GROUP

• We’ll start by creating a group for Site Assignment : SA – MTL
• Click the Add bouton on the bottom
• On the Add Boundaries screen, select all boundaries. This will direct all my clients to the Primary Site located in Montreal for Site Assignment

SCCM Training 

Live Instructor-led Online Training

Click here for SCCM Course Content

Watch SCCM Demo Video