Shulou(Shulou.com)06/03 Report--

Boundaries, boundary groups, and site systems-1

This article mainly discusses the concept of boundary and boundary group in ConfigMgr. Boundary and boundary group play a decisive role in whether the client can communicate with the site and locate the service resources.

Boundary

Boundaries are used to define a set of network locations that reflect the location of the client system

In ConfigMgr, boundaries can be defined in the following ways:

Active Directory sites: for domain member clients

IP subnet: by specifying a set of network IP locations defined by the VLSM network ID, for example, the network ID of 10.0.0.100ax 24 is 10.0.0.0X 10.0.1.130ex25 and the network ID is 10.0.1.128

Note that the network ID defined in the IP subnet cannot be an aggregated network ID. For example, the above two network ID, 10.0.0.0 and 10.0.1.128, cannot simply converge to 10.0.0.0max 23, but must be defined in the ConfigMgr respectively.

ConfigMgr finally uses the network ID to match the location of the client, for example, when defining the boundary 10.0.0.0Uniple 23, ConfigMgr finally calculates that the network ID of this subnet is 10.0.0.0 and stores the network ID of this subnet in the database, while the actual network ID of the client with an IP of 10.0.1.130amp 24 is 10.0.1.0, although logically 10.0.0.0Uniple 23 contains the 10.0.1.0Uniple 24 segment. But in the end, it will make it impossible for the client to obtain the service location normally.

IP range: define a set of consecutive IP segments, such as 10.0.0.1-10.0.1.254

IPv6 prefix: defines the prefix address boundary group for IPv6

The boundary group mainly provides functions such as automatic site assignment and location service resources. The boundary group can contain one or more boundaries.

Service resources

The service resources provided by the Border Group are divided into:

Management point distribution point state migration point software update point boundary group overlap

The overlapping part of the boundary group is allowed in ConfigMgr, that is, assuming that boundary group A contains a set of boundaries: 10.0.0.0max 23, and boundary group B also contains a set of boundaries 10.0.1.128x25, then boundary group An and boundary group B contain overlapping IP subnets 10.0.1.128x25.

Automatic site assignment: this configuration is not supported by the automatic site assignment feature. If there is overlap in the boundary group, manual site assignment must be performed to achieve the desired results.

Locate protected site systems: support boundary overlap. If a client is in the 10.0.1.128 / 25 subnet, then for this client, he can use both the service resources defined in boundary group An and boundary group B.

It is the original intention of this series of articles to refine the basic knowledge, precautions, operating mechanism and troubleshooting methods involved in SCCM for readers. There are already many articles in the network to refer to the information on the various components and functional deployment steps of SCCM, so this series of articles do not focus on providing deployment guides similar to Step-by-Step, please forgive me. At the same time, due to the limitations of personal ability and knowledge, there are inevitably some mistakes and mistakes in the article. I hope you can correct them. Thank you very much.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.