Computers are assigned as clients to Configuration Manager 2007 sites according to the boundaries you configure in the Configuration Manager console. Boundaries are defined by IP subnets, Active Directory site names, IPv6 Prefix, or IP ranges.
 Note |
|---|
| Configuration Manager does not support supernets for site boundary configuration. This includes supernets that are defined directly in the Administrator console and supernets that are configured in Active Directory sites. When you define a site boundary as an Active Directory site, make sure that the Active Directory site does not contain supernets. |
When you create Configuration Manager 2007 boundaries, you must specify the type of network connection that the boundary will operate on. You must also decide if the boundary will be used for either a Slow or unreliable or Fast (LAN) network connection.
Configuration Manager 2007 clients have the ability to 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 another network location not defined as a Configuration Manager boundary for any site at all. Ensure that you plan for client communications and manageability when clients roam from one Configuration Manager 2007 site to another. For more information about Configuration Manager 2007 client roaming, see About Client Roaming in Configuration Manager.
Advantages and Disadvantages of Site Boundary Types
Evaluate the advantages and disadvantages of each Configuration Manager 2007 boundary type before choosing which type you will use to assign clients.
| Site Boundary Type | Advantage | Disadvantage | ||
|---|---|---|---|---|
|
IP Subnets |
Using IP subnets to define the boundaries of Configuration Manager 2007 sites allows you to be very specific about which clients will be assigned to which Configuration Manager 2007 sites based on their individual subnets. This also allows you to assign computers residing in the same Active Directory sites, but on different subnets, to different Configuration Manager 2007 sites.
|
Each IP subnet you want to be part of your Configuration Manager 2007 boundaries must be entered individually in the Configuration Manager console. IP subnet changes or additions will require additional Configuration Manager 2007 boundary administration. |
||
|
Active Directory Sites |
Because Active Directory sites are based on physical network segments, the easiest method of defining Configuration Manager 2007 boundaries is to base them on Active Directory sites. This allows Configuration Manager 2007 administrators to split up or combine IP subnet boundaries based on logical, not physical, criteria. One advantage to using Active Directory sites as Configuration Manager boundaries is that subnet changes to Active Directory sites are automatically reflected within Active Directory boundaries.
|
Before assigning clients using Active Directory sites, you must ensure that the Active Directory administrators have included all of the subnets you expect to be present in the Active Directory site. If the Active Directory sites are not properly configured, and you use them for Configuration Manager 2007 boundaries, you will have unmanaged clients on those subnets. |
||
|
IPv6 Prefix |
IPv6 allows for many more addresses to be assigned and many current and future operating system releases will support its use.
|
IPv4-only systems cannot communicate directly with IPv6 computers and may require IP translation, such as NAT, to communicate. |
||
|
IP Ranges |
In some cases, you may not want to add an entire IP subnet as a boundary. In these cases it may be advantageous to specify only an IP range to use for client site assignment. |
Entering IP ranges can result in more planning to ensure that the IP ranges used are not configured as part of an IP subnet boundary for a different Configuration Manager site. |
Important