|Number of clients (Max)||15 000|
|Can have Parent||Primary site|
|Can have Child||False|
When do I need a Secondary site ?
When Do I want to install a Secondary Site ?
- To support subsidiary connected via Low-bandwidth network.
- No local point of administration is needed.
- Less then 15 000 clients to manage.
- You must manage the transfer of deployment content to sites lower in the hierarchy.
A secondary site might not be needed in all cases. Double check first if content management options might not be the better solution, as would might be able to avoid an administration overhead.
The main reason why you would like to have a secondary site in your hierarchy is if you have a site that (like a subsidiary) which is connected to your main network with a low-bandwidth. A secondary site offers a
You can simply go ahead and use one single Primary site.
Addind a secondary site to your existing ConfigMgr Hierarchy
Adding a secondary site to you hierarchy should really be thought through, since it will increase the complexity of your ConfigMgr infrastrucutre.
Only install a Secondary site if you need to cover a part of your clients that are connected via a low-bandwith network, and where Content management options do not answer your use cases.
When to add a … to an existing Infrastructure?
With ConfiMgr 2007, it was verry normal to have a big hierarchy, with a lot of components involved in it. ConfiMgr 2012 really changed on that matter, and it is possible to have the same amount of control with a hierarchy way less complicated to manage.
Adding a primary site, is one of these operations that could really make your hierarchy way more complicated that it actually has to. (Addind a primary site often resides in adding a CAS, and adding SQL servers as well).
All of that hierarchy needs to work well together, and you are not 100% protected from any CAS / primary site replication issues, and troubleshooting these things can be pretty annoying..
It also costs way more. Not directly, but adding SQL servers, Windows Servers etc… will defenitly costs in terms of licesenses.
And one crucial thing to know, is that very very very often, where you considered installing a primary site, it is actually possible to add a distribution point instead.
Ask yourself the right questions!
In order to decided whether or not adding a new … to your existing ConfigMgr infrastrucutre, ask your self the following questions:
- What are the services you need to offer on that site?
- Application deployment
- Have you considered a …?
Allowed site systems on a primary server:
The following table lists which Site systems you can install on a primary site:
|Site system role||Role|
|Application Catalog Web Service point||False|
|Application Catalog website point||False|
|Asset Intelligence synchronization point||False|
|Certificate registration point||False|
|Fall back status point||False|
|End point Protection point||False|
|Enrollment proxy point||False|
|Out of band service point||False|
|Reporting services point||False|
|Software update point||true|
|State Migration point||true|
|system Health validator point||False|
|Microsoft Intune connector||False|