Configuring Boundaries and Boundary Group

One of the first things you will need to do is configure your boundaries. Boundaries are an IP subnet, Active Directory site name, IPv6 Prefix, or an IP address range that contains clients you want to manage. The boundary by its self doesn't allow for client management in order for you to do that you need so assign the boundary to a boundary group, you can assign multiple boundaries to a singe boundary group but it is the boundary group that allows the client to find its correct site and content location when deploying software, updates or images.

1. Open the SCCM Configuration Manger Console. Navigate to Administration > Hierarchy Configuration > Boundaries.

2. From the top ribbon choose Create Boundary

3. From this window you can configure what you are going to use for the boundary for the first boundary I will be using an Active Directory Site. This boundary will include all clients that are apart of the Default-First-Site-Name Ad Site

4. Once you create the boundaries you want you will then assign them to a boundary group that you can use to assign a site and a content location to the clients in the boundary. Under hierarchy Configuration click on Boundary Groups and in the top ribbon choose Create Boundary Group.

5. Add the boundaries you want to be apart of the group by clicking the add button. Then name the group so its easy to identify what is in the group. For example if you have a second office building you could use the address of your office buildings. In my case since I will be adding the AD site boundary to this group I will call mine Full Domain.

6. On the relationships tab you will want to check "Use this boundary group for site assignment". You then need to select the site.

By coordinating your boundaries you can choose what objects talk to what servers, this is one way you can help reduce the bandwidth your SCCM environment uses.

Popular posts from this blog

SCCM Task Sequence GUI - How to set up the TS to work with a GUI

SCCM Applications vs. SCCM Packages: Understanding the Key Differences

How to Deploy a Windows 10 Servicing update as a Application