Thursday, 15 January 2015

Install SCCM 2012 R2 on Windows Server 2012 R2 and MS SQL 2012 SP1

Install features:

.Net Framework 3.5 > HTTP Activation
.Net Framework 3.5 > Non-HTTP Activation
.Net Framework 4.5 > HTTP Activation
.Net Framework 4.5 > TCP Activation
Background Intelligent Transfer Service
Remote Differential Compression

Install IIS components:

Windows Authentication
Application Development > ASP.NET 3.5
Management Tools > IIS 6 Management Compatibility > IIS 6 WMI Compatibility

Create users:

SQL Agent
SQL DB Engine
SQL Reporting

CM Network Access
CM Admin

Install SQL server:

DB Engine Services
Reporting Services
Management Tools

Extend AD schema:

Create a backup of the DC holding Schema FSMO role.
Run CMD as admin > cd cd-drive:\SMSSETUP\BIN\X64\ > extadsch.exe
Check the log for any issues: C:\ExtADSch.log

The Active Directory schema extensions for ConfigMgr 2012 are unchanged from those used by Configuration Manager 2007. If you extended the schema for Configuration Manager 2007, you do not have to extend the schema again for ConfigMgr 2012. ConfigMgr 2012 uses the Windows Active Directory (AD) environment to support many of the features it provides and can publish information to AD about sites and services. In this manner, the AD clients of ConfigMgr 2012 have this information easily accessible, but in order to use this feature the AD schema has to be extended in order to create the objects and the classes specific to ConfigMgr 2012. Extending the schema is not required for the installation of ConfigMgr 2012 but it is recommended.

Extending the Active Directory Schema for ConfigMgr 2012 allows clients to retrieve many types of information related to Configuration Manager from a trusted source. In some cases, there are workarounds for retrieving the necessary information if the Active Directory schema is not extended, but they are all less secure than querying Active Directory Domain Services directly. Additionally, not extending the schema might incur significant workload on other administrators who might need to create and maintain the workaround solutions such as logon scripts and Group Policy objects (GPO) for computers and users in your organization. The Active Directory schema can be extended before or after running ConfigMgr 2012 Setup, however as a best practice, it’s best to extend the schema before you run Configuration Manager 2012 Setup. You have to extend the Active Directory schema only once for the forest that contains site servers; you do not have to extend the schema again if you upgrade the operating systems on the domain controllers or after you raise the domain or forest functional levels. Similarly, if you extended the schema for ConfigMgr 2012 with no service pack, you do not have to extend the schema again for ConfigMgr 2012 SP1.

Extending the Active Directory schema is a forest-wide action and can only be done one time per forest. Extending the schema is an irreversible action and must be done by a user who is a member of the Schema Admins Group or who has been delegated sufficient permissions to modify the schema. If you decide to extend the Active Directory schema, you can extend it before or after setup. Only after the schema is AD extended and the steps needed to publish the ConfigMgr 2012 site information to AD, ConfigMgr 2012 can publish information to AD.

You can extend the ADSchema using either the extadsch.exe tool or the ConfigMgr_ad_schema.ldf file.When using the ldf file you will need to edit and configure this file.

Set permissions on System Management object in AD:

ADSIEdit > Default naming context > CN=System > create a new container CN=System Management > edit its properties

Add SCCM 2012 computer object to ACL > grant it full control > under advanced options set “This object and all descendent objects” in “Applies to:”.

After the schema has been extended with the classes and attributes that are required for Configuration Manager, create a System Management container in the System container in each site server's domain partition in Active Directory Domain Services. Because domain controllers do not replicate their System Management container to other domains in the forest, you must create a System Management container for each domain that hosts a Configuration Manager site.

Configuration Manager does not automatically create the System Management container in Active Directory Domain Services when the schema is extended. The container must be created one time for each domain that includes a Configuration Manager primary site server or secondary site server that publishes site information to Active Directory Domain Services.

After you have created the System Management container in Active Directory Domain Services, you must grant the site server's computer account the permissions that are required to publish site information to the container. The site server computer account must be granted Full Control permissions to the System Management container and all of its child objects. If you have secondary sites, the secondary site server computer account must also be granted Full Control permissions to the System Management container and all its child objects.

Install Windows Assessment and Deployment Kit 8.1:

Under select features, either leave everything selected (~6.5GB) or untick SQL Express and optionally ACT, VAMT, WPT and WAS.

Run SCCM 2012 prerequisite checker (optional):

Run CMD as admin > cd cd-drive:\SMSSETUP\BIN\X64\ > prereqchk.exe /pri /sql sql_fqdn /sdk sms_provider_fqdn>c:\sccm-prereqchk.log

/pri – primary site
/cas – cas site
/sec – secondary site
/sdk – sdk server
/adminUI – GUI

Install SCCM:

Download SCCM 2012 prerequisites
Select what to install/upgrade
Set the site code and site name
Set the SQL server/instance FQDN and DB name
Set the SMS provider FQDN
Select the security option for client/server communication (HTTP/HTTPS)
Set FQDNs for management and distribution points.

Install Microsoft Deployment Toolkit 2013:

Run the MDT integration wizard - Configure ConfigMgr Integration.


If you get an error "Setup could not install SQL RMO, ConfigMgr installation cannot be completed", you may need to reboot the server to complete the installations of SCCM prerequisites.

If you try to reinstall SCCM using the same SQL server, Prerequisite Check may fail on "Dedicated SQL Server instance", so you'll need to detach and remove the old CM database and delete the registry key HKLM\SOFTWARE\Microsoft\SMS\ on the SQL server.


1 comment:

  1. Extremely through. Thanks Zoran for putting this document together. I was running into issues getting SCCM installed in our Dev environment and this helped me get through those issues.