More Flatter Hierarchy with SCCM ConfigMgr CB Some Smart Decisions? Scaling of SCCM hierarchy is very important with the release of new SCCM Current Branch with SCCM servicing and Windows 10 servicing options.
Planning and designing of the infrastructure are very important with SCCM CB. We need to carefully and smartly identify when we might need to use additional distribution points or management points.
Most of us, who already used SCCM CAS or read about the SCCM CAS-related advice from the community will try to avoid the CAS server installation. Rather we will try to flatten the SCCM CB Infra with a stand-alone primary server.
More Flatter Hierarchy with SCCM ConfigMgr CB Some Smart Decisions
Now flattening the SCCM Infra is very much possible with the increase of supporting numbers of clients; an SCCM Current Branch stand-alone primary site supports the following number of devices: 175,000 total clients and devices.
More Flatter Hierarchy
A standalone primary server can support 15 management points and 250 DPs. So with flatter infrastructure, we may have to deploy loads of DPs and MPs in the environment.
I’m not a very big fan of secondary sites for low bandwidth sites mainly because of SQL DB replication. More details in the following post here. More Flatter Hierarchy with SCCM ConfigMgr CB Some Smart Decisions Configuration Manager.
But for large environments, we may have trouble in placing MPs/DPs in each remote office mainly because SCCM CB can support only 15 MPs, 250 DPs, and 250 secondary sites. We can’t even think of operation teams overhead if we have hundreds of DPs and secondary sites in your SCCM CB infra.
TechNet documentation on SCCM current Branch supported sizing and scale numbers here. To scale out your SCCM Current branch architecture and design you must look into smart scaling options like Adaptiva Onesite.
Adaptiva can dynamically handle remotes offices without spanning out hundreds of DPs across your WAN. More details about Adaptiva here.