Requirements and Recommendations before installing SCCM 2012 R2

Benoit LecoursSCCM24 Comments

Download and own part 1 to 21 of the SCCM Installation Guide in a single PDF file.

The PDF file is a 162 pages document that contains all informations to install and configure SCCM 2012 R2 or SCCM 1511 and later (Current Branch). Use our products page or use the button below to download it .

Icon Info

This blog post applies to both SCCM 2012 R2 , SCCM 1511 and later.

In the first part of SCCM 2012 and SCCM 1511 blog series, we will cover SCCM installation prerequisites most specifically hardware requirements, design recommendations and server prerequisites.

Hardware Requirements

The hardware requirements for a Primary Site server largely depends on the features that are enabled, and how each of the components is utilized. When the number of clients grows and changes, the server hardware requirements change accordingly. For the initial deployment, hardware requirements can be estimated for each server by determining:

  • The overall need for each component (Will you do Operating System Deployment ? How many daily software deployments ? Is Inventory and reporting is important for your organisation ? Will you manage Internet Client ?)
  • The number of clients planned to be installed
  • The load on each of installed SCCM components

In general, medium environments (couple thousand clients) should consider the following recommendations when planning hardware:

  • SCCM and SQL Server communicate constantly. We recommend that the main database and SQL Server be installed on the Primary site server. This is fully debatable and we understand that some organisation try to standardize their SQL distribution. Performance are simply better using a local installation when configured properly
  • Neither the SCCM site nor the SQL database should share their disks with other applications
  • Configure the SQL Server databases and logs to run on a different disk than the disk where the SCCM database is located.

Another issue to consider when determining hardware requirements for a site servers is the total amount of data that will be stored in the database. To estimate the required database size for a single site, an approximate figure of 5Mb to 10Mb per client is typically used.

In our setup, we will install a single Primary Site that has the role of  Management Point, Reporting Point, Distribution Point, PXE Service Point, State Migration Point, Fallback Status Point and Software Update Point. SQL Reporting Services will be used to provide consolidated reporting for the hierarchy. This role will also be installed on the SCCM Server. Running reports can have an impact on server CPU and memory utilization, particularly if large poorly structured queries are executed as part of the report generation.

Consider placing client facing role (Distribution Point, Reporting Point) on separate server in order to reduce load on your Primary server.

Here’s our recommended reading about hardware requirements:

SCCM 1511

SCCM 2012

We strongly recommend that you understand SQL Server before installing SCCM. Talk and have a good relation with your DBA if you have one in your organisation.

Here’s our recommended reading  about SQL :

OS

For this post,  our servers runs Windows 2012 R2 with latest security patches

Disks

Disks IOs is the most important aspect of SCCM performance. We recommend to configure the disks following SQL Best practice. Split the load on different drive. When formatting SQL drives, the cluster size (block size) in NTFS must be 64KB instead of the default 4K. See the previous recommended reading to achieve this.

LetterContentSize  
C:\Windows100GB
D:\SCCM200GB
E:\SQL Database (64K)40GB
F:\SQL TempDB (64K)40GB
G:\SQL Transaction Logs (64K)
SQL TempDB Logs
40GB

Primary Site server prerequisites

Once your hardware is carefully planned, we can now prepare our environment and server before SCCM Installation.

Active directory schema extension

You need to extend the Active Directory Schema only if you didn’t have a previous installation of SCCM in your domain. If you have SCCM 2007 already installed and planing a migration, skip this step.

  • Logon to a server with an account that is a member of Schema Admins security group
  • From SCCM ISO run .\SMSSETUP\BIN\X64\extadsch.exe

sccm 2012 r2 installation prerequisites

  • Check schema extension result, open Extadsch.log located in the root of the system drive

sccm 2012 r2 installation prerequisites

Create the System Management Container

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

  • Start ADSIEdit, go to the System container and create a new Object

sccm 2012 r2 installation prerequisites

  • Select Container

sccm 2012 r2 installation prerequisites

  • Enter System Management

sccm 2012 r2 installation prerequisites

Set security permission

  • Open properties of the container System Management created previously

sccm 2012 r2 installation prerequisites

  • In the Security tab, add the site server computer account and Grant the Full Control permissions

sccm 2012 r2 installation prerequisites

  • Click Advanced, select the site server’s computer account, and then click Edit
  • In the Applies to list, select This object and all descendant objects
  • Click OK and close the ADSIEdit console

SCCM Accounts

Create the necessary accounts and group created before installation. You can use different name but i’ll refer to these names throughout the guide.

  • SQL server services account – SCCM-SQLService
  • SCCM Network Access Account – SCCM-NAA
  • Domain user account for use SCCM client push install  – SCCM-ClientPush
  • Domain user account for use with reporting services User – SCCM-SQLReporting
  • Domain account used to join machine to the domain during OSD – SCCM-DomainJoin
  • Domain group containing all SCCM Admins Group – SCCM-Admins
  • Domain group containing all SCCM servers in the hierarchy Group – SCCM-SiteServers

Network Configuration

  • Make sure that the server has a fix IP and that internet connection is up

Firewall Configuration

  • Make sure the firewall service is ON

Run this script in an elevated command prompt order to open the necessary ports needed for SCCM.

** If you are using custom ports, change the values before running the script. **

@echo ========= SQL Server Ports ===================
@echo Enabling SQLServer default instance port 1433
netsh advfirewall firewall add rule name="SQL Server" dir=in action=allow protocol=TCP localport=1433
@echo Enabling Dedicated Admin Connection port 1434
netsh advfirewall firewall add rule name="SQL Admin Connection" dir=in action=allow protocol=TCP localport=1434
@echo Enabling conventional SQL Server Service Broker port 4022
netsh advfirewall firewall add rule name="SQL Service Broker" dir=in action=allow protocol=TCP localport=4022
@echo Enabling Transact-SQL Debugger/RPC port 135
netsh advfirewall firewall add rule name="SQL Debugger/RPC" dir=in action=allow protocol=TCP localport=135
@echo ========= Analysis Services Ports ==============
@echo Enabling SSAS Default Instance port 2383
netsh advfirewall firewall add rule name="Analysis Services" dir=in action=allow protocol=TCP localport=2383
@echo Enabling SQL Server Browser Service port 2382
netsh advfirewall firewall add rule name="SQL Browser" dir=in action=allow protocol=TCP localport=2382
@echo ========= Misc Applications ==============
@echo Enabling HTTP port 80
netsh advfirewall firewall add rule name="HTTP" dir=in action=allow protocol=TCP localport=80
@echo Enabling SSL port 443
netsh advfirewall firewall add rule name="SSL" dir=in action=allow protocol=TCP localport=443
@echo Enabling port for SQL Server Browser Service's 'Browse' Button
netsh advfirewall firewall add rule name="SQL Browser" dir=in action=allow protocol=TCP localport=1434
@echo Allowing Ping command
netsh advfirewall firewall add rule name="ICMP Allow incoming V4 echo request" protocol=icmpv4:8,any dir=in action=allow

No_sms_on_drive.sms

Place a file name no_sms_on_drive.sms on the root drive of each drive you don’t want SCCM to put content on.

Windows Server Features

On the Primary site server, the following components must be installed before SCCM installation. We’ll install all these components using a PowerShell script.

  • .Net Framework 3.51 SP1
  • .Net Framework 4
  • IIS
  • Remote Differential Compression
  • BITS Server Extension
  • WSUS 3.0 SP2
  • Report Viewer
  • ADK for Windows 8.1

Roles and features

On the Site Sever computer, open a PowerShell command prompt as an administrator and type the following commands. This will install the required features without having to use the Windows 2012 GUI.

Get-Module servermanager
Install-WindowsFeature Web-Windows-Auth
Install-WindowsFeature Web-ISAPI-Ext
Install-WindowsFeature Web-Metabase
Install-WindowsFeature Web-WMI
Install-WindowsFeature BITS
Install-WindowsFeature RDC
Install-WindowsFeature NET-Framework-Features -source \\yournetwork\yourshare\sxs
Install-WindowsFeature Web-Asp-Net
Install-WindowsFeature Web-Asp-Net45
Install-WindowsFeature NET-HTTP-Activation
Install-WindowsFeature NET-Non-HTTP-Activ

Ensure that all component are showing as SUCCESS as an EXIT Code. It’s normal to have Windows Update warnings at this point.

sccm 2012 r2 installation prerequisites

Report Viewer

Download and install – here

ADK for Windows 8.1

Download and install – here

  • Select the default path

sccm 2012 r2 installation prerequisites

  • Do not join CEIP

sccm 2012 r2 installation prerequisites

  • Accept the License Agreement

sccm 2012 r2 installation prerequisites

  • Install the following components
    • Deployment Tools
    • Windows Pre-installation Environment
    • User state Migration tool

sccm 2012 r2 installation prerequisites

Active Directory

  • Add the computer account of all your site servers in the SCCM-SiteServers AD group
  • Ensure that the group has Full Control on the SYSTEM Container in Active Directory

Local Admin accounts

Add both SCCM computer account and the SCCM Admin account to the local administrator group on the site server.

  • SCCM-Admins
  • SCCM-SiteServers

SCCM 2007 Client

If applicable, uninstall SCCM 2007 client and FEP if present on the server before the installation. If the client is present, the 2012 SCCM Management Point installation will fail.

Windows Updates

Run windows update and patch your server to the highest level

Your server is now ready for the SQL installation.

Overview | SCCM 2012 R2 Step-by-Step Installation Guide

Next Part | How to install SQL 2012 before installing SCCM 2012 R2

  sccm 2012 r2 installation prerequisites

Founder of System Center Dudes. Based in Montreal, Canada, Senior Microsoft SCCM Consultant, 4 times Enterprise Mobility MVP. Working in the industry since 1999. His specialization is designing, deploying and configuring SCCM, mass deployment of Windows operating systems, Office 365 and Intunes deployments.
Requirements and Recommendations before installing SCCM 2012 R2
4.2 - 9 votes

24 Comments on “Requirements and Recommendations before installing SCCM 2012 R2”

  1. Hello, in Part 1 5.6 (Firewall Configuration) you mention that you should run “this” script in elevated command prompt in order to open the necessary ports needed in SCCM. Where is “this” script? It immediately goes to 5.7.
    Please advise.

  2. Pingback: Miniseriál o SCCM (System Center Configuration Manager)- díl 3. SCCM 2012 R2 – Instalace SQL serveru – IT-News von PC-Meister

  3. Pingback: Miniseriál o SCCM (System Center Configuration Manager)- díl 3. SCCM 2012 R2 – Instalace SQL serveru – Christopher Golden Blog

  4. Hello,
    I’ve a question about the users :

    SQL server services account – SCCM-SQLService
    SCCM Network Access Account – SCCM-NAA
    Domain user account for use SCCM client push install – SCCM-ClientPush
    Domain user account for use with reporting services User – SCCM-SQLReporting
    Domain account used to join machine to the domain during OSD – SCCM-DomainJoin
    Domain group containing all SCCM Admins Group – SCCM-Admins
    Domain group containing all SCCM servers in the hierarchy Group – SCCM-SiteServers

    Which AD Rights they need? It’s enough to create standard users or they need special AD Rights?
    For Example, I think that SCCM-ClientPush has to be a LOCAL ADMIN on domain computers right?

  5. Your guide is truly top notch! Could you comment on how the install occurs in an environment where the ads schema is NOT extended? I’m certain that it can work but not certain what additional steps or configurations are needed for this scenario to work.

  6. SCCM Accounts

    Create the necessary accounts and group created before installation. You can use different name but i’ll refer to these names throughout the guide.

    Do I really need to create all these groups and users, below, for a single site supporting 500 devices tops? What happens if I just use one SCCM user account and set the SQL DB up Local System?

    SQL server services account – SCCM-SQLService
    SCCM Network Access Account – SCCM-NAA
    Domain user account for use SCCM client push install – SCCM-ClientPush
    Domain user account for use with reporting services User – SCCM-SQLReporting
    Domain account used to join machine to the domain during OSD – SCCM-DomainJoin
    Domain group containing all SCCM Admins Group – SCCM-Admins
    Domain group containing all SCCM servers in the hierarchy Group – SCCM-SiteServers

  7. Do we need to set up a new share for this ?
    “Install-WindowsFeature NET-Framework-Features -source \\yournetwork\yourshare\sxs”
    Or is this pointing to source files ?
    Sorry for the lame question.

    1. You don’t need a share for this; you can point it to the Server 2012 R2 install DVD (or mounted ISO). If mounted to D:\ just set
      -source D:\sources\sxs

  8. • Your link to report viewer is to a French Microsoft page and is for report viewer 2010… shouldn’t we be using a newer version?
    • You don’t list how to install wsus 3.0 sp2 and shouldn’t we be installing wsus 4.0?

  9. Pingback: SCCM Deploy – Post 1. Setting up VMware AD and SCCM 1511

  10. Pingback: SCCM Deploy – Post 4. Setup SCCM 2012 1511

  11. Neat guide, I’ll be using it to upgrade our system from running on a 2008 R2 server to 2012 R2.

    But I have a question in regards to the disk requirements. We use a similar setup on our primary site (though with the SQL on it’s own server) and our D: drive is currently using 750GB+. The server is not set up as a DP but it still seems to have a copy of all our packages and applications (which is A LOT, with many big CAD programs).

    Is this normal and should we just make the new server with 1-1.5TB, or are we doing something wrong?

    Thanks

  12. I’m looking to do a fresh install of SCCM 2012 R2 SP1 so that I can migrate our current setup that’s running on Server 2008 R2 with SQL Server 2008. I was planning to do the new install on a Hyper-V server that I have available. The Hyper-V storage is local and is setup as one big RAID10 on SATA disks. Do I still need to create the additional 5 disks for the Hyper-V server (as per your recommendation), or do I just install everything on single disk?

    Many thanks.

  13. Pingback: Part 1 - Requirements and recommendations before installing SCCM 2012 R2 - SLR-Corp

  14. Currently running SCCM 2012 R2 on Windows Server 2012 R2. Any attempt to install SCCM 2012 R2 SP1 nets an error message saying that SCCM 2012 has to be running – Did Microsoft error in publishing the SCCM 2012 R2 SP1?

    1. It constantly amazes me just how blog writers for example your self can find some time plus the dedication to keep on writing terrific blogposts. Your site iswonderful and one of my own ought to read blogs and forums. I just wanted to thank you.

Leave a Reply

Your email address will not be published. Required fields are marked *