Detailed Explanation of SCCM
In the realm of enterprise management, System Center Configuration Manager (SCCM) plays a crucial role in maintaining control over a vast array of devices. One key aspect of SCCM is determining the appropriate site structure for your organisation, based on the number and type of devices to be managed.
Recommended SCCM Hierarchy
Microsoft recommends the following hierarchy structure based on scale and device counts:
- Central Administration Site (CAS): Used only in very large enterprises when supporting more than 100,000 clients or for managing multiple primary sites. It does not manage clients directly but coordinates administration across primary sites.
- Primary Sites: These sites manage clients directly. A single primary site can support up to approximately 100,000 clients depending on hardware and configuration. For organisations with fewer than 100,000 clients, a single primary site is typically sufficient.
- Secondary Sites: Used to manage clients in remote locations with limited bandwidth or where local content distribution is needed. Secondary sites cannot directly manage clients and are administered through their parent primary site.
Choosing the Right Site Structure
The number and type of sites are strategically chosen based on:
- Number of clients: For fewer than 100,000 clients, a single primary site usually suffices; above that, multiple primary sites and a CAS may be required.
- Geographical distribution: Secondary sites can be deployed in remote locations to optimize bandwidth and content distribution.
- Administrative boundaries: Primary sites can be used to separate administrative control and reporting.
This means smaller environments may have just one primary site (and no CAS), medium-large environments may have a CAS with multiple primary sites, and remote locations use secondary sites as needed.
SCCM Site Capacities
Each CAS and primary site requires at least one SMS Provider for database access. Secondary sites do not have local databases and rely on their parent site.
A standalone site supports up to 250 distribution points, up to 15 management points, and up to 175,000 total clients and devices. The scope of a secondary site supports 1 management point, 15,000 desktops, and does not exceed 15,000 clients and devices.
IBCM and Cloud Management
IBCM (Internet-Based Client Management) allows managing clients when they are not connected to the network but have an Internet connection, with Cloud Management Gateways (CMG) and Cloud Distribution Points (CPD) used as the cloud infrastructure to support IBCM.
IBCM requires an Azure subscription and clients and site system servers that the clients connect to use PKI certificates.
Role-Based Administration
Role-based administration model in SCCM centrally defines security access settings for all sites and site settings by using security roles, security scopes, and collections.
Conclusion
In conclusion, the recommended SCCM hierarchy scales from 1 primary site for up to 100,000 clients, expanding to multiple primary sites plus a CAS for larger environments, and adding secondary sites for remote locations. By understanding the key factors that influence site structure, organisations can ensure an efficient and effective SCCM deployment.
Read also:
- Shaping production and consumption tendencies via cosmetic certification
- Youth in Quebec urgently demand attention from its authorities
- Underwater photography gadget, patent-protected, now subject to import taxes in Brazil due to Trump's trade policies
- Summer competition at the local library captivates entire Michigan metropolis
