SCCM scalability planning (2012 R2 and above)

Hi Friends

Hope this post finds you in good health and spirit. I was out of this space for a while as was busy with few due obligations but now I am back so here we go.

There are lot of documents online to guide about SCCM scalability numbers however these are long and scattered ( atleast for me,lol) so I thought to compile data. This will work as quick reference guide for SCCM designing and planning. I will try to keep this post short and crisp.

Client support number in sites and hierarchy

Clients supported in hierarchy with SQL Datacenter/enterprise edition

a. Till SCCM 2012 R2  – Windows and Linux/Unix Clients – 400,000, including mobile devices, MAC clients and Intune clients –  725,000.

b. SCCM 2012 R2, CU3+ – Windows and Linux/Unix Clients – 500,000, including mobile devices, MAC clients and Intune clients –  825,000.

c. SCCM 2012, SP2 + – Windows and Linux/Unix Clients – 600,000, including mobile devices, MAC clients and Intune clients –  925,000.

Clients supported in hierarchy with SQL Standard edition

Windows and Linux/Unix Clients – 50000, including mobile devices, MAC clients and Intune clients –  375,000

Stand-alone primary site

a. Till SCCM 2012 SP2 – Windows and Linux/Unix Clients – 100,000, including mobile devices, MAC clients and Intune clients –  175,000

b. SCCM 2012 SP2 and onwards – Windows and Linux/Unix Clients – 150,000, including mobile devices, MAC clients and Intune clients –  225,000

Secondary site

Till SCCM 2012 SP2 – 5000

SCCM 2012 SP2 and onwards – 10000

1 Central administration site – 25 Primary sites

1 Primary site – 250 secondary sites

Management Point

1 Central administration site – 25 MP

1 Primary site – 10 MP

1 Secondary site – 1 MP

1 MP- 25000 clients

Distribution Point

1 Primary site or Secondary site – 250 DPs + 2000 Pull DPs

1 Primary site including its child Secondary sites – 5000 DPs

1 DP – 4000 clients *

1 DP – 10000 packages *

* Actual number depends on size of package and network bandwidth.

Other site system roles

1 Software update point (SUP) installed on site server – 25000 clients

1 SUP on remote server before SP2 – 100,000 clients

1 SUP on remote server on and after SP2 – 150,000 clients

1 Fallback status point – 100,000 clients

1 instance of Application catalog website/web service point – 50000 clients ( You can have multiple instance and install both on same server)

1 System health validator point – 100,000 clients

I will keep on updating this list as new facts will add-on. Before we close let me answer a question which is asked lot of time

Should I use DP or Secondary site ?

Kent Agerlunds has described this beautifully in his Book “SCCM 2012 – Mastering the fundamentals”. He recommend installing a secondary site at remote locations if one of the following statements is true:

– The Remote locations have more than 500 and fewer than 5000 clients
– You need to compress traffic going to the site
– You need to control the upward flowing traffic
– You need a local management point
– You need a local SUP

otherwise settle for DP. 🙂

So, that’s all in this post. Stay tuned for more technical stuff to come.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s