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

SCCM Planning-system scalability, Internet client Management

This article mainly introduces the carrying capacity of ConfigMgr system roles.

When designing the overall site, the number of deployment of each component should also be determined according to the actual environment, taking into account the load capacity of the components.

When the number of clients in the current environment exceeds the maximum number of one site\ site role instance, additional role instances should be deployed.

Primary site, role carrying capacity subsite type supported subsite type supported number of subsites central management site 25 primary site secondary site 250SQL database central management site SQL version supported client number of SQL standard edition 50000SQL enterprise edition 400000 major site role juxtaposition support number of clients no 100000 is 50000

It is recommended that you do not install other site roles and site servers side by side:

Ensure that the client does not communicate directly with the site server for the purpose of download policy, distribution, etc.; the independent site server also ensures that the site server does not affect its processing performance due to other services Maximum number of clients supported by site type of management point per site main site 1025000 secondary site 12500 distribution point maximum number of clients per site 2504000 number of clients supported by software update point whether role juxtaposition supports number of clients 100000 is 25000

Prior to ConfigMgr 2012 SP1, NLB configuration was required if multiple software update points were to be deployed at the same site.

The above values are based on SCCM 2012 RTM. There may be differences in subsequent versions. Please refer to https://technet.microsoft.com/zh-cn/library/gg682077.aspx#BKMK_SiteAndRoleScale

Branch management

ConfigMgr support for remote offices can be divided into the following methods:

Main site

Consider adding a major site to meet any of the following situations

The number of remote office clients exceeds 100000; reduces the impact of server outages at the current major site; reduces the workload at the current major site; and the remote office will use ConfigMgr clients that are different from the current site

If there is a central management site, the information of all major sites under it will be copied to the central management site, and the team responsible for managing the central management site will have the right to manage any site under it.

Secondary site

Consider using a secondary site to meet any of the following situations

More than 500 remote office clients; control network traffic between the current site and the remote office; network traffic between the current site and the remote office needs to be compressed; remote management points and distribution points

Remote management points and distribution points provide policy and content distribution services for clients in remote offices to prevent clients from occupying a lot of WAN bandwidth when visiting the current site through WAN, and to provide more stable and reliable policy and content distribution services for local ConfigMgr, so as to avoid the negative impact of slow and unreliable WAN lines on clients.

Internet client support

ConfigMgr supports the following three Internet-based client management:

The functions supported by the method require IBCM (ConfigMgr comes with the ability to manage Internet clients) software and hardware asset information, status messages, software distribution, software updates, etc., which depend on the PKI architecture and need to be released to the public. The main functions of the site system Direct Access (individual functions are limited) DA services need to be deployed in the https://docs.microsoft.com/zh-cn/sccm/core/plan-design/configs/support-for-windows-features-and-networks environment, The client requires Enterprise SKUV P N and almost all major features require V P N connections

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.