:::: MENU ::::

SCCM 2012 Roles

In order to learn the SCCM, We requires to know what are the roles available .

What is Role :– With SCCM we have many features. In-order to use those feature we requires to enable these roles. Most of the roles as similar to SCCM 2007. If something is added I’m pointing at the line

Site Servers:

Using installations with Software Media Wizard server Called as Site Server. Without Site Server You can’t install SCCM in our hierarchy. While installing Site Serve we will mention Site Server Name with 3 digit (alpha-numeric) code.It hosts the configuration manager components and services

Site System:

Once we have the Site Server, site system roles can be hosted on site server Or Installing the roles on different server. A server or server Share that hosts one or more site system roles for Configuration Manager site Manage content distribution

Site Database Server:

A site system role that runs Microsoft SQL server and hosts the configuration Manager Site Database

Management Point:

A site system role that replies to configuration Manager Client’s requests and accepts management data from configuration manager clients

Distribution Point:

A configuration manager role that stages packages for Distribution to clients

Application Catalog Website Point:

A site system role that serves as an application catalog website point

Application Catalog Web service point :

A site system role that serves as application catalog web services point

Asset Intelligence Synchronization Point :

A site system role that connects to system center online to download asset intelligence catalog information and upload uncategorized titles that can be considered for future inclusion in the catalog

Reporting services Point:

A site system role that provides integration with SQL server reporting services to create and manager reports for configuration manager

Software update point:

A site system role that runs Microsoft windows server update services and allows configuration manager to use the WSUS catalog to scan configuration manager clients for software updates

State migration Point:

A site system role that store user state and settings migrated during the Operating system deployment

Fallback Status Point:

A site system role that receives messages from ConfigMgr clients that cannot communicate with their management point


Central Administration Site:

A Central Administration Site (CAS) is the top level or Root level Site server in the hierarchy .CAS is dedicatedly for administration purpose. We cannot assign Clients to the CAS or we can’t manage clients with help of CAS. We can’t enable all roles in CAS.

CAS can’t support grandchild primary sites [Vertical] architecture. However, CAS can have multiple child primary sites [Horizontal]. Which they send the client data to CAS, It will stores in the SQL database which is nothing but CAS site database. In CAS we will be installing Administrator console from which we can manage our SCCM infrastructure.

Without CAS also we can install and manage the SCCM with Standalone Primary site .When we have more than one Primary site we required the CAS.

We install standalone primary site server, In future, based on business we need to expand the sites or need to add some more primaries. Then that time if we have the SCCM 2012 R2, we can install a CAS after we installed a primary site. Before SP1(service pack1),We have to install the CAS First.

CAS can support max 25 child primary sites


For roles supporting configuration http://technet.microsoft.com/en-in/library/gg682077.aspx#BKMK_SiteAndRoleScale

Primary SITE

Clients can assigned only to a Primary site. At least 1 Primary site requires in SCCM environment.Assigned clients data will be stored in SCCM database .Primary site can have multiple secondary sites.All these secondary will report to Primary site. Primary can be standalone or It may report CAS Site. Primary site have both Primary site client machines information and Secondary site data. Primary site requires the SCCM License

Primary site can support up to 250 secondary sites (It’s completely depends on WAN speed)

In SCCM 2007:

Not much difference but in SCCM 2007 Primary can have multiple primary sites.


Secondary Sites

Client won’t assign to Secondary sites .Secondary sites are always child site of the primary sites. So it managed through the console connected to parent primary site. Secondary wont requires SCCM license

Secondary site is a mediator or forwarder, it gathers the information like inventory, system status info, etc. from clients and sends to parent site. Secondary site are more useful where we have remote locations where we need links where we need to control bandwidth

In generally we used to implement on following circumstances :

Remote location has around 500+ clients

If required to use software update point

To control the Bandwidth like upward flowing traffic

In SCCM 2012 : It requires SQL database  atleast SQL server Express edition will fine. Most of the client to server data will be replicated with help of database in SCCM 2012. so they have introduced database to secondary site . Unlike in SCCM 2007 ,we have to install the secondary site from it parent site console wizard in CM 2012, at that time if database not exist , it automatically installs SQL Server Express edition