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

Boundaries, boundary groups, and site systems-3

This article mainly discusses the ConfigMgr client resource discovery process.

Boundary group current boundary group

Refers to the boundary group where the ConfigMgr boundary corresponding to the current network location of the client resides, for example:

The network address of the client Client An is: 10.0.0.0Comp24.

ConfigMgr Boundary Boundary Avatar 10.0.0.0-10.0.0.255

Boundary Boundary A belongs to boundary group BG A

For Client A, his current boundary group is BG A.

Neighbor boundary group

After ConfigMgr 1610, a boundary group can define an one-way link to another boundary group, which is called a boundary group relationship, while the other boundary group it points to is called a neighbor boundary group of the current boundary group. For example, multiple neighbor boundary groups BG B, BG C, etc., can be defined for BG A

Boundary group relationship

When defining a boundary group relationship, you can configure the fallback time, which defaults to 120 minutes. The exact meaning of the fallback time is explained below.

Default site boundary group

Each ConfigMgr site creates a default site boundary group when it is installed

ConfigMgr creates an implicit link to the default site boundary group for each boundary group

The return time defined in the implicit link is 120 minutes and cannot be modified

If the client's network location does not fall within any other boundary group, the client will be divided into the default site boundary group for fallback

As described in the previous article, when a client needs to request various services of ConfigMgr, it sends a resource location request to its preferred management point, and the management point returns the corresponding site system list based on the client's current boundary group information.

If none of these site systems returned by the management point are available, the client can use the site system in the neighbor boundary group defined as the current site boundary group

Distribution point fallback

When all the distribution points in the current boundary group are not available, the client will calculate the return time defined in the boundary group relationship between the current boundary group and its neighbor boundary group. When the return time is reached, the client will add the distribution points in the neighbor boundary group to the distribution point list and try to contact each distribution point

Software update point

The neighbor boundary group has added support for software update points in ConfigMgr 1702. The fallback time is 120 minutes and cannot be modified.

In ConfigMgr 1706, you can customize the return time of software update points.

The fallback behavior of software update points requires attention to the following:

By default, the client always uses the software update point on the last successful connection, because the switching of the software update point is a relatively resource-consuming process for both the software update point and the client. Because the client synchronizes the software update metadata and reports update availability information to the new software update point

No matter how much the fallback time of the software update point is modified, the client will always select a new software update point after the current software update point does not have to reach 120 minutes.

When the client fails to contact the last successfully connected software update point for the first time, and the return time is reached at the software update point in the neighbor boundary group, it is added to the list of software update points

When the client cannot contact the last successfully connected software update point for 120 minutes, the client uses a shorter cycle time to communicate with other software update points in the list of software update points. ensure that you can quickly leave the remaining available software update point management points in the list

In ConfigMgr 1802, neighbor boundary groups have added bounce support for management points, and the selection behavior of preferred management points is also defined by the boundary group mechanism.

You can observe the newly added Locality attribute identification in the client's LocationService.log:

0: indicates unknown 1: indicates that this management point is nearly associated with the default site boundary group 2: indicates that this management point is in the remote or neighbor boundary group 3: indicates that this management point is in the local or current client boundary group. If the preferred management point feature is not enabled in the ConfigMgr level, the management point is always identified as 3, regardless of which boundary group it is in.

The order in which clients use management points is as follows: 3 > 2 > 1

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.