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

Boundaries, boundary groups, and site systems-2

This article mainly discusses the relationship between boundary group and site system in ConfigMgr.

Site resources

To run the ConfigMgr client, you not only need to use the local resources of the client, but also need the services provided by ConfiMgr to ensure that the client can perform various tasks normally, such as:

Deployment of applications and packages: the participation of distribution and management points is required to complete the entire deployment task

Software update: the participation of software update point, distribution point and management point is required.

Operating system deployment: it requires the participation of power generation, management point, state transfer point and software update point.

ConfigMgr deployment scenarios are often cross-regional. If the client in Beijing requests to download the required program source files from the distribution point in Shanghai, there will be the following problems:

There must be network connectivity between Beijing and Shanghai

Download across local area network, slow speed

Occupy the bandwidth of the line between Beijing and Shanghai

Clients using all kinds of site system resources can be defined through boundary groups.

Site system

Site systems, such as management points, distributed power generation, software update points, and state migration points, can all be associated with the boundary group. For example, we can associate the branch power generation in the Beijing office with the boundary group that can represent the Beijing subnet. and associate the distribution point in Shanghai to the boundary group that represents the Shanghai subnet.

In this way, when requesting site resources, those who end up in the Beijing boundary group will use the distribution point in Beijing according to our design, rather than cross-domain physical regions to use the distribution point in Shanghai.

Management point

When the client requests the site resources, who tells the client which site system should be used? The answer is the management point. During the installation of the ConfigMgr client, an initial list of management points is generated first. The rules for generating the list of management points are as follows:

Use the management point specified by the SMSMP or MP parameter during installation to obtain the management point information through Active Directory, through DNS and through WINS.

The client then communicates with the management point sequentially according to the management point in the initial list, and obtains the following information:

List of all management points in the site, which will be cached by the client; the boundary group in which the client is currently located

Finally, the client will take the management point defined in the boundary group as the preferred management point, and subsequent site resources will query this management point, which will inform the client of the other site system information under the current boundary group.

List of management points

The client caches the list of management points, and the client updates the list with the following rules:

Every 25 hours when the client gets a new IP address, the client network adapter reconnects to the network, and the management point is sorted every time the client restarts.

The client sorts the management points in the following order:

A management point with HTTPS communication capability and a management point with HTTP communication capability

If the client has HTTPS communication capability, the management point with HTTPS communication capability will be given priority.

If there are multiple management points in the current boundary group and they have the same communication capabilities, the sort order between them is random. For example, if the client current boundary group contains MP A (HTTPS), MP B (HTTP), MP C (HTTPS), MP D (HTTP), the sort order of the management points may be:

MP A,MP C,MP B,MP D

But it could also be:

MP C,MP A,MP D,MP 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.