Looking for hierarchy suggestions

[crashrebootrepeat]

I have recently started a project doing an implementation of SCCM 2012 that will eventually grow to 100,000 clients or more. There will be three primary sites. I am looking for best practices on how to best configure this. The sites are globally distributed. I will be doing Application / Operating System Deployment as well as compliance (Updates etc). Please suggest hardware configuration, layouts etc.

 

Thanks.

 

 

 

[GarthMJ]

I hate to say this but there is nowhere enough details for anyone to give you a recommendation.

 

I would start by hiring a senior consultant who has experience with this type of thing, there are not many worldwide. In the meantime, start documenting your network, network speed, # of user, what existing at the site now, what problem exist at the site, expected growth, etc.

 

Keep you primary sites to a minimum. Each primary site that you add, serious increase the complexity

[Garrett804]

I'd agree with GarthMJ. Your data doesn't give us anything to go on really and depending on the overall network layout what we may suggest could not even be workable for yoru business environment.

 

Document the network as he said to start with and depending on the layout of that either come back to us with more details on your network speeds etc.. and maybe we can help with a design in terms of network traffic. Hardware though isn't really that complex and will be based off of what the network layout is.

 

For example if you have 1Gb connections throughout your environment then you don't have to control traffic that much depending on your current saturation on those connections. Without having to consider traffic you wouldn't need secondary sites etc.. to mitigate the cross-network policies. If you have DSL 1.5Mb or below and a 10+ clients behind that then obviously pushing OSD or larger packages and even policy and WSUS updates can totally cripple that network.