Part 1 – Fundamentals of SCCM 2012 r2

What is a SITE?

A site is building block of the Configuration Manager. Let’s say you are installing SCCM 2012 R2 in your environment, you must create a site.

Types of SITES:

We have three types of Sites available in SCCM 2012: 1- Central Administration Site (CAS) 2- Primary Site 3- Secondary Site

When you install SCCM for the first time, you can either create CAS or Primary Site. CAS is suitable for large scale deployments. Whereas, Primary Site is suitable for smaller deployments. Secondary site can only be created when Primary site is existing in the environment.

CAS is used to manage all other sites exist in the design. It facilitates site-to-site communication and does reporting. It does not process any client data. If you choose to install CAS, then you have to install one Primary site as well. At least one Primary Site is required in every SCCM implementation. As it is a large scale environment, you can deploy more Primary Sites with this design. Additional Primary sites can be helpful in managing devices present in different geographical locations.

However, if you choose not to install CAS and install only Primary site then you cannot add more primary sites with this design. This design is known as, “Stand-alone Primary Site”. However, you can add Secondary Sites. It is always a child site to the Primary site. Secondary sites basically spread a primary site to manage devices that have a slow network connection to the primary site.

All Good?

Now, let’s say you deployed “stand-alone primary site” model. But, for some reasons later-on you decide to use CAS model. Will you be able to do that?

If you are using SCCM 2012, the answer is

NO.

If you are using SCCM 2012 SP1 and later versions, the answer is ##YES.  This design change is known as

“Site Expansion”.

Publishing Site Information to Active Directory Domain Services

You need to extend the schema for System Center 2012 Configuration Manager one time only per forest to publish SCCM sites to Active Directory Domain Services so that Active Directory computers can securely retrieve SCCM site information from a trusted source. It is recommended to extend the schema before the installation of SCCM but not necessary. You can extend the schema after the installation as well. However, you must also create an Active Directory container named System Management in each domain that contains a SCCM site before publishing the site information.

Site Systems:

ConfigMgr comes with multiple site system roles to support management operations at each site. Any server hosting a site system role is considered as “Site System” server. Some roles are transferrable to other site servers and some are not. Following are the site system roles that in my opinion are required in each site:

Image alternative text

Image alternative text

-MAK blog: http://www.vnextadmin.com