SCCM 2012 Architecture

Hello,

I am looking for ideas for our new SCCM 2012 environment with:

- 20,000 Desktops (Windows 7)

- 2,000 servers (windows, Linux,...)

Thanks,

March 26th, 2015 6:02pm

Hi,

Not much of a question in there, what ideas are you thinking of? A lot more information is needed to be able to assist in anything like a new environment. Post what your thoughts are and ask for comments on the approach you have planned instead.

Regards,
Jrgen

Free Windows Admin Tool Kit Click here and download it now
March 26th, 2015 6:08pm

As Jorgen says not much of a question. few more details are required.

Are the 20000 windows desktops all on the same site or spread out geographically? Same for the servers?

If they are spread out how are they connected via WAN? Slow links, fast links? How many users? Do you use Active Directory? One forest? Lots of things to consider before a propper answer can be provided.

You should consider reading through this: https://technet.microsoft.com/en-gb/library/gg712681.aspx 

Basically though with potentially 22000 clients your Management Point is going to get busy (according to this the ax MP client count is 25k). You may want to consider a CAS with two primary sites or maybe a secondary/proxy MP to better control the load on the MP. But this really depends on the topography of your network and where the clients are based geographically.

March 27th, 2015 2:26am

You may want to consider a CAS with two primary sites or maybe a secondary/proxy MP to better control the load on the MP. 

No way! A CAS is only needed for scaling purposes (>100k clients). A single MP can handle up to 25k clients, so you can also add a second MP to a standalone primary. 
Free Windows Admin Tool Kit Click here and download it now
March 27th, 2015 3:03am

Based on your original question and excluding how dispersed your clients are;

1 Primary to manage the clients with DP's in appropriate locations

No CAS

Perhaps consider/look into 1 Config Manager instance to manage your workstation clients, OSD, inventory etc and a separate instance to manager your server fleet (Microsoft's model)

Cheers

Damon


March 27th, 2015 3:32am

Based on your original question and excluding how dispersed your clients are;

1 Primary to manage the clients with DP's in appropriate locations

No CAS

Perhaps consider/look into 1 Config Manager instance to manage your workstation clients, OSD, inventory etc and a separate instance to manager your server fleet (Microsoft's model)

Cheers

Damon


Free Windows Admin Tool Kit Click here and download it now
March 27th, 2015 3:32am

You may want to consider a CAS with two primary sites or maybe a secondary/proxy MP to better control the load on the MP. 

No way! A CAS is only needed for scaling purposes (>100k clients). A single MP can handle up to 25k clients, so you can also add a second MP to a standalone prim
March 27th, 2015 3:39am


Perhaps consider/look into 1 Config Manager instance to manage your workstation clients, OSD, inventory etc and a separate instance to manager your server fleet (Microsoft's model)


Why would you do that? Servers and clients can be managed with the same (standalone primary) site just perfectly fine. Role based access (RBA) will handle that. Using separate sites are not needed. 
Free Windows Admin Tool Kit Click here and download it now
March 27th, 2015 4:00am

Well I only said that because of the high number of servers - I know it can be done with one environment - that's why I said "perhaps" :) Plus he asked for ideas - and that's an idea!

Cheers

Damon


March 27th, 2015 4:04am

Based on your original question and excluding how dispersed your clients are;

1 Primary to manage the clients with DP's in appropriate locations

No CAS

Perhaps consider/look into 1 Config Manager instance to manage your workstation clients, OSD, inventory etc and a separate instance to manager your server fleet (Microsoft's model)

Cheers

Damon


Free Windows Admin Tool Kit Click here and download it now
March 27th, 2015 7:30am

Well I only said that because of the high number of servers - I know it can be done with one environment - that's why I said "perhaps" :) Plus he asked for ideas - and that's an idea!

Cheers

Damon


March 27th, 2015 8:02am

You don't give any details on geographical location of your systems.

With the provided information I would suggest 1 Primary with Distribution Points in remote locations.

If your remote location has lots of clients, consider placing secondary sites.

Place additional MP if needed but be aware of client assignment process. Look at Management Point Affinity in CU3 if needed but I usually don't recommend it.

Check my guide for further recommendations : http://www.systemcenterdudes.com/sccm-2012-r2-installation-prerequisites/ 

Free Windows Admin Tool Kit Click here and download it now
March 27th, 2015 8:03am

Hi,

Not much of a question in there, what ideas are you thinking of? A lot more information is needed to be able to assist in anything like a new environment. Post what your thoughts are and ask for comments on the approach you have planned instead.

Regards,
J

March 27th, 2015 11:36am

As Jorgen says not much of a question. few more details are required.

Are the 20000 windows desktops all on the same site or spread out geographically? Same for the servers?

If they are spread out how are they connected via WAN? Slow links, fast links? How many users? Do you use Active Directory? One forest? Lots of things to consider before a propper answer can be provided.

You should consider reading through this: https://technet.microsoft.com/en-gb/library/gg712681.aspx 

Basically though with potentially 22000 clients your Management Point is going to get busy (according to this the ax MP client count is 25k). You may want to consider a CAS with two primary sites or maybe a secondary/proxy MP to better control the load on the MP. But this really depends on the topography of your network and where the clients are based geographically.

Hello,

Desktops are spread out within 6 sites:

- 2 main sites hosting 18,000 desktops with several buildings each... about 10-15 buildings...

(2 groups of building with FAST LINKS, split of 6,000 Desktops on the main site and 12,000 on the remote site)

... the link between the two sites is excellent there have not been issues in the past with SCCM 2007 between those sites. (SCCM all sites were hosted in Building 1 ONLY for the three sites)

- 1 site hosting 1,500 with 3 buildings

- 3 sites hosting between 50 desktops and 500 desktops  

- 1 main site 800 servers ( Data Center)

- 1 site 150 servers (Date Center)

- 1 site 50 servers (Date Center)

- Fast links everywhere: but in SCCM 2007 the clients were not reporting well!!!

- 25,000 users

- Yes we are using Active Directory, one forest, clients in different OUs with different policies and rights.

- Also Desktops as well as servers have different owning chart:

- Dept1 own the server Hardware, OS, SQL, Application

- Dept 1 own the hardware, Dept 2 own OS, SQL, Application

- Dept 1 own the hardware and OS, Dept 2 own SQL, Application

- Dept 1 own the hardware, OS, SQL, Dept2 own the application

So we should be able to delegate rights and privileges per groups

Thanks,
Dom

Free Windows Admin Tool Kit Click here and download it now
March 27th, 2015 11:47am

You may want to consider a CAS with two primary sites or maybe a secondary/proxy MP to better control the load on the MP. 

No way! A CAS is only needed for scaling purposes (>100k clients). A single MP can handle up to 25k clients, so you can also add a second MP to a standalone prim
March 27th, 2015 11:49am

Based on your original question and excluding how dispersed your clients are;

1 Primary to manage the clients with DP's in appropriate locations

No CAS

Perhaps consider/look into 1 Config Manager instance to manage your workstation clients, OSD, inventory etc and a separate instance to manager your server fleet (Microsoft's model)

Cheers

Damon


Excellent if I understand properly 1 Primary site , 5-6 DPs a locations, 2 SQL Instances to split between desktops and servers

Thanks,
Dom

Free Windows Admin Tool Kit Click here and download it now
March 27th, 2015 11:51am


Perhaps consider/look into 1 Config Manager instance to manage your workstation clients, OSD, inventory etc and a separate instance to manager your server fleet (Microsoft's model)


Why would you do that? Servers and clients can be managed with the same (standalone primary) site just perfectly fine. Role based access (RBA) will handle that. Using separate sites are not nee
March 27th, 2015 11:54am

Thank you all for the discussion.

The summary is :

1 Primary Site

1 SQL Instance

- DP as needed

- RBA for permissions

No CAS

So I am looking at a hardware that will work for 20,000 Clients?

Ram 64+GB

16 cores

3 raid  arrays, maybe SSDs (1xR1 2xR10?) 1GB net? or should we do 10GB?

most of the docs say 1GB

Thanks,

Free Windows Admin Tool Kit Click here and download it now
March 27th, 2015 11:56am

You'll be fine with the hardware you're describing.

Make sure that your disks are well configured for SQL

http://technet.microsoft.com/en-us/library/hh846235.aspx

http://www.systemcenterdudes.com/sccm-2012-r2-installation-prerequisites/

March 31st, 2015 3:54pm


Why would you do that? Servers and clients can be managed with the same (standalone primary) site just perfectly fine. Role based access (RBA) will handle that. Using separate sites are not nee
Free Windows Admin Tool Kit Click here and download it now
March 31st, 2015 8:49pm


Excellent if I understand properly 1 Primary site , 5-6 DPs a locations, 2 SQL Instances to split between desktops and servers


No. You cannot "split SQL instances". Just use a standalone primary and use RBA for the separation. 
April 1st, 2015 2:09am


To play devil's advocate:  then why does Microsoft do it with their own product?  RBAC makes things way easier ... but it's not a cure-all at this point IMO. 
What does Microsoft do with its own product?
Free Windows Admin Tool Kit Click here and download it now
April 1st, 2015 2:13am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics