How to: Setup SCCM 2012 R2

By Rory Monaghan


I previously posted instructions on how to setup SCCM 2012, the first release. While this was a huge improvement on 2007, even more has changed and been improved upon since, with extended support and integration for App-V 5.0, managing clients on MACs, Linux, Android etc. In honesty this post may be a little bit overkill as not a whole lot has changed in the setup but I recognized this as an opportunity to clarify on certain aspects of the Setup. Also, there has been a couple of changes in the setup of the requirements e.g. installing the SDK, no need to extend the schema on Server 2012. So that’s where the value will likely come in this post.

So first, let’s cover the the pre-requisites required on your SCCM Server.

Configure your Server\Install your pre-requisites

On your SCCM Server you should Add the following roles: Windows Desktop Services, .Net Framework, WSUS, Remote Differential Compression, IIS, BITS and ADDS Snap-in Tools.


Static Content Compression

Health and Diagnostics

HTTP logging


Request Monitor

Common HTTP Features

HTTP Errors

HTTP Redirection

Basic Authentication

Windows Authentication

Static Content

Default Document

Request Filtering

Directory Browsing

HTTP Errors

HTTP Redirection

IP and Domain Restrictions


Management Tools

IIS Management Console

IIS Management Scripts and Tools

Management Service

IIS 6 Management Compatibilty

IIS 6 Metabase Compatibility

IIS 6 WMI Compatibility

IIS 6 Scripting Tools

IIS 6 Management Console

Application Development


.NET Extensibility


ISAPI Extensions

ISAPI Filters

On the server in question. If you use Windows Firewall you will need to set exception for port 1433 and 4022 as these are used by SCCM


You need to browse to ASDI Edit which should be on your server now. You need to connect to your SCCM server. You need to create a container called System Management. Navigate to the System Container and then create the System Management Container within. Next modify the security properties on the System container and ensure the SCCM Server itself has Full Control.

Ensure you have a SQL Server setup and ready as SCCM stores reporting information in this database. Your SQL Server must be SQL Server 2008 SP2 or later. SQL Server 2012 as of yet is not supported. But I have not had issue with it, I setup SQL Server 2012 for my most recent setup of SCCM 2012. I set it up as default and then went into the Configuration Center after install and modified the services to use the Local System account as their service account. This seemed to meet SCCM 2012’s requirements. If the SQL Instance you are using is not the default instance, you’ll need to make sure Dynamic Ports are not enabled. Personally, I ensure the SQL Server runs using the Local System account and I create a login with DBReader and DBWriter rights for the server name in SQL.

Also no matter what version of SQL you use you will need to go into SQL Management Studio and modify the settings to modify the maximum memory setting. The suggested setup for a primary site is a minimum of 8GB and 4GB for a secondary site. You can find this in the Properties for your Database in SQL Management Studio.

If you’re not installing to the Default Instance on your SQL Server. You will want to ensure Dynamic Ports are not configured for your Named Instance.


More info can be found HERE

SCCM 2012 originally required extra pre-requisites and manual effort before setup could be completed. Fortunately in 2012 R2 there’s a little less, that’s because a lot if covered by installing Configuration Manager 2012 SDK, which can be found HERE


Launch the SCCM 2012 R2 Installer



Click Install



Click Next



You can setup a central administration site if you intend on having multiple SCCM Servers which you would like to manage from a central point, for this post I am selecting to install a primary site. Click Next



Enter the product key and Click Next



Check I accept these license terms and then Click Next



Check all three of the checkboxes and click Next



Download the Setup to a share in your environment. Can be a local drive but you may prefer a UNC path. Click Next



Enter a three letter Site Code, a descriptive Site Name and leave the default Installation folder. Ensure to have the checkbox on this dialog checked to install the management console. Click Next.



Choose whether or not to provide feedback to Microsofts mothership. Click Next.



Click Next




The setup will complete.

Deploy the SCCM Client to End Users

Open the Configuration Management Console. Navigate under Administration and Hierarchy Configuration and right click on Boundaries and click Create Boundary



Select IP address range from the drop down box. Give a decent description. Select a valid IP address range for your environment. Click Apply, Click OK



You can next right click on Boundary Groups and click Create Boundary Group and Add the Boundary just created



Under the Preferences tab and Add the Site System Server which was setup.



Next, browse to Discovery Methods. Right Click on Active Directory System Discovery and click Run Full Discovery Now. Repeat this on other ‘methods’ which are relevant for you e.g. Group Directory (A little different but not complicated), User Directory








Expect to receive the above prompt. Click Yes.


Browse to Assets and Compliance. Now if you browse under the collections and Devices you should see these are populated.



Now you are ready to deploy the client. Navigate to Administration, Site Configuration and click on Sites. Under Settings click on Client Installation Settings, Client Push Installation. Here you can select some of the Client Deployment settings and configure the service account for management of the client. If you browse to a Device under Assets and Compliance you should now be able to click Install Client by right clicking on the machine or the collection (device collection).

At this point, you should ensure that there’s a Firewall exception for VMI set on your client machines. It’s a good idea to also ensure the BITS is installed on the primary site server and is working.



If you browse to a machine which was part of the collection, you’ll see a process has started for the SCCM Client Setup.



Software Center will now appear in the Start Menu and Configuration Manager should appear under the Control Panel. You can now deploy applications to this machine. For more on deploying applications take a look at some of my other posts under the SCCM option at the top of my site.

Let's make virtualization easier!

Be amongst the first to know when I publish new reviews, guides and tools to simplify your projects.

By signing up, you agree to our Terms of Use and acknowledge the data practices in our Privacy Policy. You may unsubscribe at any time.