Step by Step: Installing SCCM 2012 SP1 on Windows Server 2012 and SQL 2012 SP1

Well, after some testing with SCCM 2012 SP1 I decided to reinstall everything in my lab to the latest software. So Windows 2012, SQL 2012 RTM and of course System Center Configuration Manager 2012 SP1.

In this blog I used my laptop:
-Intel(R) i5-2410M CPU @ 2.30GHz, 2 Core(s)
-8 Gb of internal memory
-Two SSD disk (C:\ for OS and D:\ for Hyper-V)

Lab setup:
Domain Controller: Windows 2012 Enterprise; DC, DNS and certificate server
SCCM 2012; Windows 2012 Enterprise, SQL 2012 Enterprise, IIS and SCCM components

1. SQL 2012 installation
ConfigMgr 2012 SP1 Beta supports SQL 2012 RTM with a minimum of CU 2. ConfigMgr has very strict SQL collation requirement, pretty much across the entire System Center range, essentially only SQL_Latin1_General_CP1_CI_AS collation is supported.
This has to be selected during installation if you are running a non-USA regional\system OS.

– Login as the SQL admin on the SQL Server
– Launch the SQL 2012 RTM installer
Select Installation on the left navigation pane
Select New SQL Server stand-alone installation or add features to an existing installation
– Ok, Next,
and choose Accept the license terms, Next
We will open the Firewall later, so skip the warning
– Choose Next
– Select SQL Server Feature Installation

Select the following
– Database Engine Services
– Reporting Services – Native
– Management Tools – Basic
– Management Tools – Complete
Because I’m in a test environment I didn’t change the path’s. In production it’s recommended to choose alternative path’s
Next, Next

– Choose the default Default instance, and change the path’s if necessary and choose Next, Next
By default each of the services will be configured using a service-specific user account, we used NT AUTHORITY\SYSTEM

Do this for the SQL Server Agent, the SQL Server Database Engine and the SQL Server Reporting Services services
– Click Account Name, Browse, Browse locally for SYSTEM and accept
– Set the services Start-up Type to automatic
Select the Collation tab
– Double check
If SQL_Latin1_General_CP1_CI_AS is shown, otherwise Customize this, Next
Add the current user and a domain user at this point. I add the SQL admin and the local administrator, Next
– Select Install and configure, Next
Set Send Windows and SQL Server Error Reports to Microsoft, choose Next, Next
Alrighty then SQL is Ready, lets rock.

– Next we will run SQL 2012 SP1 (SCCM 2012 requires minimal CU2 to have an successful install)
Download link SP1
Download link CU1

Note If you do not install CU2 (or SP1) you’ll receive SQL Server Version Error in the Perquisites.

The Advanced logging says that the SQL server Version is not supported. So patch you’re SQL Server.

Make the nessesary Firewall Exeptions for SCCM;
– Open the settings, Control Panel, System and Security, Windows Firewall
– Choose Advanced Settings, Inbound rules
– Create a new Rule called SQL Ports,
– On Rule Type, Choose Ports, Next
– On theTCP tab 4022, 1433 and click Next
ScreenHunter_191 Jan. 25 10.08
– Choose allow the connection, Next
– On profile choose all, Next
Fill in a name (we used SQL Ports)

2. Installing the SCCM 2012 Perquisites
Open Server Manager
– Select Add Roles and features, click Next
– Choose Role Based or Feature based installation
– Select the local server, Next
Open Web Server (IIS) and ADD select the following features
HTTP Features
Static Content
Default Document
Directory Browsing
HTTP Errors
HTTP Redirection

.NET Extensibility
ISAPI Extensions
ISAPI Filters

Health and Diagnostics
HTTP logging
Logging tools
Request Monitor

Basic Authentication
Windows Authentication
URL Authorization
Request Filtering
IP and Domain Restrictions

Static Content

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
– Select Windows Server Update Services, Add features
– Select Windows Deployment Services, Add Features

– Choose Background Intelligent Transfer Service (BITS), Add features
– Choose Remote Differential Compression
– Telnet Client (not necessary but it’s useful), Next
– On the WSUS section choose next.
– On the Role Services choose WSUS Services and Database, Next
– Choose Store updates and choose a location (This is a testlab, in production it is not recommended to save these files to the C:\ drive), Next

– Type the SQL Server name and choose Check connection

– Next, Next,
– Choose Deployment Server and Transport Server
– Next, Install

3. Install the WADK (Windows Assessment and Deployment Kit)
In Windows 2012 you no longer use WAIK, we’re now on WADK for Windows 8.
– Go to and download the ADK Setup.
– Run the ADKSetup.exe as an administrator

– I left the path’s default and choose Next
– Choose if you want to join CEIP and choose Next
Accept the Licence Agreement and choose Accept
– Check Deployment Tools, Windows Preinstallation Environment (Windows PE) and User State Migration Tools (USMT)

– Choose Next and install the Software

3. Next step is to install SCCM 2012 SP1 Beta
Ok, we are now ready to install ConfigMgr 2012 SP 1 Beta
– Launch the spash.HTA from the installation media

– First check the server is ready before we get any further into the installer Select Assess server readiness

Some minor issues but no show stoppers so lets continue
– Go back to the Splash.hta screen and click Install, Choose Next
– Because we are on one demo server we choose Install a Configuration Manager Primary Site and check the Use typical installation… Choose Next.

– Choose yes and I Agree, Next
– Accept all the licence therms and choose next

– Download the files to a folder you choose and click Next

-Choose a site code, Site name and installation folder for SCCM 2012 SP1, Next

– Hit next a couple of times and then choose Begin Install

That’s it, we are now up and running.

SP1 brings a lot of nice new stuff like the cross-platform clients, Azure Cloud DP, mobile device management through Microsoft Exchange ActiveSync amongst others.
Check out what’s new in SP1 here for a list of fun things to play around with and get to know in preparation for the actual SP1 release, as well as the release notes detailing what is knowing to be in a broken state during the Beta. You can also provide feedback to Microsoft for anything quirky that you may find during the evaluation.

Have Fun!

What about System Center Server licensing?

In sales and presales conversations my experience is that knowledge of the licensing suite is sometimes crucial to close the deal. Therefore this post about how the licensing suite in System Center is build.

To make things clear;
This part only counts for Server Operating Systems; not for clients (workstations)

Basically it is very simple; You can only buy the complete System Center suite, if you only use SCCM or only SCOM you still have to buy the complete suite.
Advantage is that if you license one product you get the right to use:
–  Configuration Manager
–  Service Manager
–  Virtual Machine Manager
–  Operations Manager
–  Data Protection Manager
–  Orchestrator
–  App Controller
–  Endpoint Protection
Now we’re talking !!

Licence models
System Center 2012 management licenses will be released in 2 editions differentiated by virtualization rights only:

-System Center Datacenter: Maximizes cloud capacity with unlimited Operating System Environments (OSEs) for high density private clouds.

Each Data Center license covers up to two physical processors, so you must count the number of physical processors on the server, divide that number by two, round up to the nearest whole number, and acquire and assign that number of licenses to your server.

-System Center Standard: For lightly or non-virtualized private cloud workloads. Standard Edition allows the management of up to two  “Operating System Environments” per license.

For each managed server count the number of physical processors and the number of managed OSE’s. You need the number of licenses to cover the greater number (processors or OSE’s).

Extra information:
– Both licenses includes SQL Runtime or SQL CAL
– Licensed Per processor
– Always includes Software Assurance (SA)


Time for a quick recap of the licensing suite:
Standard for servers with low or no virtualization
Datacenter for high density virtualisation

Underneath an example on what licence is to most suitable.

Are there separate offerings without SQL Server Technology?
No. All System Center 2012 products include the right to run a runtime version of SQL Server Technology (SQL Server Standard Edition) to support System Center so there are no longer separate offerings.

How much do the Server MLs cost?
The Microsoft Volume Licensing Open License No Level (NL) U.S. Estimated Retail Price (ERP) is
– $1,323 for System Center 2012 Standard
– $3,607 for System Center 2012 Datacenter.

For your specific pricing, contact your Microsoft reseller. Actual prices may vary. Microsoft does not determine pricing or payment terms for licenses acquired through resellers.

Why do the Server MLs cover up to two processors?
The server management licensing is simplified by standardizing on a processor-based licensing model. Each license covers up to two physical processors because the vast majority of servers contain an even number of physical processors.

Endpoint Protection?
Endpoint Protection is included in de suite. It is possible to install Endpoint protection stand-alone. For managing the Endpoint Protection software SCCM 2012 is required. For monitoring there is a management pack available. Without SCCM 2012 it is possible to manage the clients with policies but this is not an optimal situation and I do not recommend this.

Extra information:
Standalone Standard or Enterprise Server Management Licenses will be exchanged for a minimum of 1 System Center 2012 Standard Edition licenses per server or for the actual number of processors in use.
At the end of the current agreement term, you should do a self-inventory, documenting the number of processors in each server in use with System Center Server Management Suite Enterprise Edition or standalone Server Management Licenses covered with Software Assurance.
This will enable customers to receive the appropriate number of processor licenses based on System Center 2012 to continue their current deployments.
You should do this self-inventory using the Microsoft Assessment and Planning (MAP) Toolkit or other inventory tools and processes to accurately archive a time/date stamped inventory of hardware tied to System Center installations.
If you do not perform the self-inventory, they will receive two System Center 2012 licenses for each System Center Server Management Suite Enterprise Edition and one license for each standalone Server Management License.

Configure/open Firewall ports for MS SQL 2008 R2/Windows 2008 (R2)

By default, installing SQL Server 2008 R2 on a brand new Windows Server 2008 R2 server does not open the required Windows Firewall ports.
I always wonder why they don’t give you the option during the installation of SQL and let MS make the changes for you. Anyway, MS has a tool to “Fix It” but on my Windows Server 2008 it runs but doesn’t apply to the Windows 2008 R2 setup.

You can of course follow Microsoft’s KB articles and manually add the Windows Advanced Firewall rules. For me, a script to do this was the way to go. Don’t forget to run the script as Administrator in the CMD box.

@echo =========  SQL Server Ports  ===================
@echo Enabling SQLServer default instance port 1433
netsh firewall set portopening TCP 1433 "SQLServer" 
@echo Enabling Dedicated Admin Connection port 1434
netsh firewall set portopening TCP 1434 "SQL Admin Connection" 
@echo Enabling conventional SQL Server Service Broker port 4022  
netsh firewall set portopening TCP 4022 "SQL Service Broker" 
@echo Enabling Transact-SQL Debugger/RPC port 135 
netsh firewall set portopening TCP 135 "SQL Debugger/RPC" 
@echo =========  Analysis Services Ports  ==============
@echo Enabling SSAS Default Instance port 2383
netsh firewall set portopening TCP 2383 "Analysis Services" 
@echo Enabling SQL Server Browser Service port 2382
netsh firewall set portopening TCP 2382 "SQL Browser" 
@echo =========  Misc Applications  ==============
@echo Enabling HTTP port 80 
netsh firewall set portopening TCP 80 "HTTP" 
@echo Enabling SSL port 443
netsh firewall set portopening TCP 443 "SSL" 
@echo Enabling port for SQL Server Browser Service's 'Browse' Button
netsh firewall set portopening UDP 1434 "SQL Browser" 
@echo Allowing multicast broadcast response on UDP (Browser Service Enumerations OK)
netsh firewall set multicastbroadcastresponse ENABLE

Check if the ports are opened successfully (see the picture).



SCCM 2012 – Reporting and DPM rights on SQL

At a customer of ours we have installed a SQL 2012 R2 server for all System Center Products including DPM 2012.
After installing the SCCM 2012 Reporting functionality on the SQL server the eventviewer flooded with:

Log Name: Application
Event ID: 18456
Task Category: Logon
Level: Information
Login failed for user ‘NT AUTHORITY\SYSTEM’. Reason: Failed to open the explicitly specified database. [CLIENT:]

After some investigation we found that the SCCM 2012 reporting installation messed around with the security rights of the System Center SQL database.

The NT Authority\System account was removed from the SYSadmin role


Add the NT\Authority\System account to the Sysadmin role