Export (0) Print
Expand All

Planning Configuration Manager Boundaries

Updated: December 1, 2009

Applies To: System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2, System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System Center Configuration Manager 2007 SP2

Configuration Manager 2007 boundaries are defined in the Configuration Manager console and are defined by IP subnet, Active Directory site name, IPv6 Prefix, IP ranges, or any combination of these.

noteNote
Do not use Active Directory site names if these contain supernets because Configuration Manager does not support supernets for boundary configuration.

When creating Configuration Manager 2007 boundaries, you must also specify the type of network connection that the boundary will operate on. You must decide if the boundary will be used for either a Slow or unreliable or Fast (LAN) network connection. An example of a slow boundary would be one defined by an IP subnet connected to the site over a WAN. Fast boundaries should be made up of faster, more reliable connections such as a corporate LAN.

noteNote
In order for clients located on IP subnets configured as VPN scopes to install software updates and software distribution packages, the IP subnets defined as VPN scopes must be added as Configuration Manager 2007 boundaries and, if the VPN connection is fast and reliable enough, configured as fast boundaries. If VPN scopes are not added as boundaries, the VPN scope subnets will be treated as slow boundaries and clients located on VPN scope subnets will be unable to download software updates or software distribution packages without specifying slow boundary behavior in the software update or software distribution advertisement.

Boundaries are used to assign clients to a specific Configuration Manager 2007 site and should be unique to each site. When defining site boundaries for sites, ensure that you do not define the same boundary for more than one Configuration Manager 2007 site. Doing so leads to a situation called overlapping site boundaries. Overlapping site boundaries are not supported and can lead to undefined results in Configuration Manager client behavior.

While Configuration Manager 2007 boundaries are used to assign clients to a site, they are not used to specify which computers are assigned site system roles for a site. Configuration Manager 2007 site systems do not need to be located within a site’s boundaries.

Configuration Manager clients are able to communicate with site systems that are members of another site in the Configuration Manager 2007 hierarchy when they roam. Roaming is the ability to move a computer that is running the Configuration Manager 2007 client from the designated boundaries of a Configuration Manager 2007 site to within the assigned boundaries of another Configuration Manager 2007 site or to a network location not defined as a boundary for a Configuration Manager 2007 site at all.

An essential part of the deployment planning process is determining the appropriate boundaries for your Configuration Manager 2007 site. Use the Choose Configuration Manager Boundaries planning task to help you identify and organize possible Configuration Manager 2007 boundaries.

See Also

For additional information, see Configuration Manager 2007 Information and Support.
To contact the documentation team, email SMSdocs@microsoft.com.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft