using vNext beta2 in a LAB – Part 2. Configuration configuring SCCM 2012 beta 2

In Part 1. of this series we Installed vNext, now we will start to configure it.


In Configuration Manager 2012, a boundary
is a network location 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 it can include any
combination of these elements. To use a boundary you must add the boundary to one or more boundary groups.
Boundary groups are collections of boundaries and they allow clients to
find an assigned site and to locate content when they need to install
software, such as applications, software updates, and operating system

Boundaries are no longer site-specific. Instead, you define them one
time only for the hierarchy and they are available for all sites in the
hierarchy. Each boundary must be a member of a boundary group before a
device on that boundary can identify an assigned site or locate content
on a distribution point. Each boundary represents a network location in
Configuration Manager 2012 and it is available from every site in your
hierarchy. A boundary does not enable you to manage clients at the
network location. To manage a client, the boundary must be a member of a
boundary group.

Content Location

You can associate one or more distribution points with each boundary
group. You can also associate a distribution point with multiple
boundary groups. When a client requests content for a deployment,
Configuration Manager sends the client a list of distribution points
that have the content and that are associated with a boundary group that
includes the current network location of the client.

Configuration Manager 2012 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 download
the content.

You can configure the network connection speed of each distribution
point in a boundary group. Clients use this value when they connect to
the distribution point. By default, the network connection speed is
configured as Fast, but it can also be configured as Slow. The network
connection speed and the deployment configuration determine whether a
client can download content from a distribution point when the client is
on an associated boundary.

Step 1. Creating Boundaries and Boundary Groups

Perform the following on the vNext server as SMSadmin

Click on the Administration workspace

Resized to 70% (was 1026 x 728) – Click image to enlargeAttached Image: monthly_05_2011/post-1-0-81900000-1305873861.png

In the navigation pane expand Site Hierarchy and then Boundaries, we havn’t created any yet so nothing will appear, click on Create Boundary in the ribbon on top.

Resized to 70% (was 1025 x 726) – Click image to enlargeAttached Image: monthly_05_2011/post-1-0-21428100-1305875654.png

In the Create Boundary dialogue box, enter the following details, for Type box, choose IP address range from the drop down menu, and input for the starting address and for the ending address.

Attached Image: monthly_05_2011/post-1-0-81570000-1305876066.png

Click ok and your newly created boundary should appear.

Resized to 70% (was 1025 x 703) – Click image to enlargeAttached Image: monthly_05_2011/post-1-0-38253200-1305876289.png

Boundaries in SCCM 2012 do nothing unless they are assigned to a Boundary Group so click on Boundary Groups,
nothing appears as we havn’t configured any Boundary Groups yet. In
order to assign clients to our site through discovery and for clients to
access content from distribution points we need to create a Boundary
Group with suitable boundaries.

Click on Create Boundary Group in the ribbon.

Resized to 70% (was 1024 x 375) – Click image to enlargeAttached Image: monthly_05_2011/post-1-0-63927400-1305877198.png

for Name type P01 Clients and click on Add to add our previously created boundary

Attached Image: monthly_05_2011/post-1-0-28539500-1305877389.png

when the Add boundaries dialogue box appears, select our previously created boundary and click ok.

Attached Image: monthly_05_2011/post-1-0-92559500-1305877528.png

Next click the References tab and select Use this boundary group for site assignment.

Attached Image: monthly_05_2011/post-1-0-15488200-1305881083.png

Click on Add to Add site systems
(distribution points and State Migration Poins) to our Boundary Group,
select our vnext server listed and click ok.

Attached Image: monthly_05_2011/post-1-0-31322600-1305881419.png

Step 2. Create an Active Directory Site

Complete this task on your Active Directory computer as Domain Admin.

Start up Active Directory sites and Services and click on Sites, the default site name of Default-First-Site-Name is listed.

Resized to 86% (was 833 x 293) – Click image to enlargeAttached Image: monthly_05_2011/post-1-0-82379800-1305890280.png

We will create a custom AD site which is unique from other AD sites in our heirarchy. Right click on sites and choose New Site, when the New Sites wizard appears give it a name windows-noob-AD-site, select the DEFAULTIPSITELINK and click ok.

Attached Image: monthly_05_2011/post-1-0-86030200-1305891003.png

Note the message after creating the new AD Site

Attached Image: monthly_05_2011/post-1-0-72107600-1305891132.png

Right Click on Subnets, choose New Subnet

Resized to 86% (was 834 x 290) – Click image to enlargeAttached Image: monthly_05_2011/post-1-0-25125900-1305891270.png

In the prefix box type and select the windows-noob-AD-site

Attached Image: monthly_05_2011/post-1-0-63189700-1305891422.png

We have now assigned the subnet to our newly created
site, now lets move our Domain Controller (AD1) to the new AD site.

expand Default-First-Site-Name until you see AD1 listed. Right click on AD1 and choose Move

Attached Image: monthly_05_2011/post-1-0-07846900-1305891585.png

when prompted where to move the server, select the windows-noob-AD-site and click ok.

Attached Image: monthly_05_2011/post-1-0-98004800-1305891670.png

We have now moved our DC out of the Default AD site and to our custom AD site.

Resized to 87% (was 831 x 293) – Click image to enlargeAttached Image: monthly_05_2011/post-1-0-80153700-1305891750.png
Step 3. Configure Active Directory boundaries through Active Directory Discovery

In the console click on Discovery Methods.

Resized to 70% (was 1023 x 536) – Click image to enlargeAttached Image: monthly_05_2011/post-1-0-27370200-1305889966.png

Double click on Active Directory Forest Discovery, note that this is a new feature in SCCM 2012. Select the following options

  • Enable Active Directory Forest Discovery
  • Automatically create Active Directory site boundaries when they are discovered

and click ok.

Attached Image: monthly_05_2011/post-1-0-69616900-1305889978.png

The discovery will be run every week by default, but we want to trigger
it now, so click on Run Full Discovery now in the ribbon.

Resized to 70% (was 1027 x 405) – Click image to enlargeAttached Image: monthly_05_2011/post-1-0-11664600-1305889989.png

answer Yes when prompted

Attached Image: monthly_05_2011/post-1-0-21631800-1305890015.png

Click on Boundaries and click on the
refresh icon to the right (refresh “boundaries”), after some moments the
discovery has run and our Active Directory Site Boundary is listed
under our previously created Boundary.

Resized to 70% (was 1027 x 726) – Click image to enlargeAttached Image: monthly_05_2011/post-1-0-91395100-1305891911.png

This discovery will create a new boundary for each Active Directory site
that is discovered in the site servers forest. Remember that boundaries
in SCCM 2012 do nothing unless added to a Boundary Group.

Read the original post (including screenshots) here
This entry was posted in Uncategorized. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.