Share This Post

Install Guide – ConfigMgr 2012 SP1 Beta + Server 2012 + SQL 2012 CU 3

Here’s a guide for installing ConfigMgr 2012 SP1 Beta onto Windows 2012 with SQL 2012 RTM CU 3.

We can now for the first time join together all three 2012 products, Configuration Manager, SQL and Windows Server

The whole installation experience is the easiest I’ve seen from Microsoft across all aspects of the install. I did not keep a record of installation times to see if the run time is different than for CM 2012 RTM and Server 2008 R2 with SQL 2008 R2, but it seemed quicker. I expect there isn’t much in it between the two but will do a timed run-through at some point out of interest when SP1 RTM’s

To get going you’ll need to download a few files and have a VM ready to install into. A Domain controller is a must, VM or physical so that you can domain join your Site server in readiness for ConfigMgr

You will only need X64 files, there will be no X86 files required, the only exception to this is the ConfigMgr 2012 console which is installed for you as part of Site installation

Ok, you just need to go through in the same order as below and you should get an identical result, a successful ConfigMgr 2012 SP1 Beta install

Something worth noting is that I don’t explicitly install all of the OS requirements simply because the products we’re installing, and the order they go on in results in everything needed getting turned on or installed

Download Cache

Make sure you download all of this before starting the builds below, in order to save the most time

Windows Server 2012 evaluation

Windows Assessment and Deployment Kit for Windows 8

SQL 2012 RTM evaluation

System Center 2012 Configuration Manager SP1 Beta

Note: This is the full installer, you install fresh using this media. There is no requirement to upgrade from RTM to SP1

ConfigMgr 2012 SP1 Beta prerequisites

This is not a specific download but a collective group of files that ConfigMgr downloads either before setup or during

Once you have downloaded Beta 1, follow this guide and use the Beta 1 setup downloader to download the prerequisite files for storage

We had eight kits to deal with before, now we have just 5, WAIK is no longer included in the ConfigMgr install kit and is called WADK now, as a separate download

Virtual Machines

The following Virtual Machines will need to be assigned and built:


OS for the LAB

Usage and configuration recommendations for this LAB guide only

Domain Controller

Can be Windows 2008 R2 or Windows 2012

The domain controller for your ConfigMgr SP1 Beta Site server


Windows 2012 RTM

Assign a minimum of 2GB of Memory, ideally 4GB

Join this server to an existing lab AD domain

Install the Domain Controller

It’s pretty easy to DCPROMO a Windows server to become a domain controller once you’ve built one. Go through the motions and produce a new AD domain controller, or reuse an existing one

Once the Domain Controller has been created, or if you have an existing one, you need to extend the Active Directory Schema to support ConfigMgr’s heavy tie-in with Active Directory. Follow this guide to extend the schema and this still-applicable ConfigMgr 2007 guide to setup the System Management container and appropriate permissions

Check out this guide which has some good info on taking care of the Domain Controller, Extending the Schema and setting up the System Management container

Install Windows Server 2012

I won’t screenshot the Server 2012 installation as there isn’t much too it, instead install Windows Server 2012 into your VM and log onto it

Do the following to the Windows Server 2012 OS

If you haven’t already, change the machine name

Give it a static IP address

Join it to your AD domain

Remember the more you tweak the OS the more likely it is to present an issue. Keep It Simple

Install WADK

We no longer use WAIK, we’re now on WADK for Windows 8

Launch the WADK installer


I just accept default paths for all my installs, unless there is a known issue or a pretty good reason to not do so

Select Next


I like to give the CEIP telemetry data from my lab installations, it actually does help them to reveal trending issues, and most other companies opt you in by default (the fruit company for example)

Select Yes

Select Next


Select Accept


Un-tick everything short of

Deployment Tools

Windows Preinstallation Environment (Windows PE)

User State Migration Tool (USMT)

Select Install


Read the getting started guide if you want to catch up with the changes in WADK

Select Close

Install OS prerequisites

Open a PowerShell prompt and type

Import-Module servermanager

Add-WindowsFeature BITS,RDC,Web-WMI,WDS

I’ve really cut this down, magic happens during the installs that results in what we need being switched on or installed

Note: .NET Framework 4.0 is built in to Server 2012 now, so no need to install it anymore!

Install SQL 2012 RTM

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

Something handy to know ahead of the installs is that you can use CMTrace to view the resulting log files for the SQL 2012 RTM and CU 2 installations. Each execution creates a new folder on the following path called detail.txt:

C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log

Launch the SQL 2012 RTM installer


Files are expanded …


Select Installation on the left navigation pane


Select New SQL Server stand-alone installation or add features to an existing installation


All rules will pass

Select OK


Select Specify a free edition and make sure Evaluation is the chosen option

Select Next


Tick Accept the license terms

Tick Send feature usage data

Select Next


I open the firewall later, hence the warning above

Select Next


Select SQL Server Feature Installation

Select Next


Select the following

Database Engine Services

Reporting Services – Native

Management Tools – Basic

—    Management Tools – Complete

Select Next


Ho hummm, we wait while wheels turn


Rules are good

Select Next


The default is Default instance, which we’ll accept along with the paths

Select Next


Ho hummm  …


Select Next


By default each of the services will be configured using a service-specific user account, we need to revert back to using 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 locally for SYSTEM and accept

Set the services Start-up Type to automatic

When done, Select the Collation tab


If SQL_Latin1_General_CP1_CI_AS is not shown, click Customize otherwise skip this part


Select SQL collation, used for backwards compatibility

Scroll down the list and choose SQL_Latin1_General_CP1_CI_AS

Select OK


Select Next


Add the current user and a domain user at this point. I usually add domain admins and the local administrator unless I want to be very specific about who gets what

Select Next


Select Install and configure

Select Next


Tick Send Windows and SQL Server Error Reports to Microsoft …

Select Next


Rules passed again

Select Next


SQL is ready to install, show time!

Note the Configuration file path, you can automate this part of SQL install by using this file next time

Select Install


Once it’s done we get success reported back for all the features being install

Install SQL 2012 RTM CU 3

Now we’ll put SQL 2012 RTM CU 3 on

Run the SQL 2012 RTM CU 3 installer


Unpack file time …


Tick I accept the license terms

Tick Send feature …

Select Next


The CU 3 detects a version it can upgrade

Select Next


No files in use, this is on a brand new install with no reboot yet, and none required before we patch. That’s cool

Select Next


That’s it, SQL 2012 RTM with CU 3 both installed successfully

Select Close

Install WSUS

We’re going to install WSUS using Server Manager now. You can add this feature using PowerShell, but I’m passing through quickly and haven’t looked to see how you configure WSUS so that it uses the existing SQL installation and not WID

Open Server Manager

Select Add Roles and features


Select Next


Select Role-based or feature-based installation

Select Next


Select Select a server from the server pool

Select Next


Tick Windows Server Update Services

The following window will appear


I show this and the two shots below so you can see what feature are needed to support this role



Select Add Features


Select Next


Select Next


Select Next


Previously the WSUS installer wizard would be launched after we’d elected to install the role, that would then allow us to configure the Database and Website settings. We now have this integrated pretty much into the role creation

Tick WSUS Services

Tick Database

Select Next


Enter a valid (as in the directory exists) path to store WSUS Content.

You should do this to get patch licensing files, otherwise licensed patches won’t install on the clients

Select Next


Punch in the SQL server hostname

For this guide we’re just going to use the default SQL instance so no need to specify it above

Select Check connection

It should be able to reach back to SQL 2012 RTM with CU 3 and confirm connection is successful

Select Next


Notice that you can export configuration settings.

It has also put the Windows Internal Database (WID) into the list even though we haven’t selected it directly. I assume ticking Database during role creation induces this, I’ll see what that is about when I pass through here again once SP1 has released

Select Install


Select Close

Configure the firewall

This Primary won’t have a parent most likely, but if you do configure the beta in a hierarchy then you’ll need to open up the firewall ports or take the firewall down entirely

To open up the firewall ports that are needed by ConfigMgr for inter-site database replication

From Powershell or CMD prompt enter the following

netsh advfirewall firewall add rule name=”SQLServer” dir=in action=allow protocol=TCP localport=1433

netsh advfirewall firewall add rule name=”SQL Service Broker” dir=in action=allow protocol=TCP localport=4022

The rules should both be accepted with an OK message

Configure SQL 2012 Maximum server memory usage

Method 1

SQL will consume all your memory. It needs to be throttled back

Open SQL Server Management Studio and get the properties for the database up


Select Memory and change the maximum server memory setting

Method 2

Use OSQL to make the change to the maximum allowed memory

Note that this sets aside 1GB of memory for SQL to use before it “bottoms out” and begins paging. 1GB is enough for a small lab but if you encounter performance bottlenecks this is a place to revisit to increase the memory allocation.

Open a CMD prompt and type OSQL -E

Paste the following

sp_configure ‘show advanced options’, 1




sp_configure ‘max server memory’, 1024




Install ConfigMgr 2012 SP1 Beta

We’re ready to install ConfigMgr 2012 SP 1 Beta now

Launch the HTA from the installation media


Let’s check the server is ready before we get any further into the installer

Select Assess server readiness


Both of these benign warnings can be ignored

Configuration Manager requires SQL Server to reserve a minimum of 8 gigabytes (GB) of memory for the central administration site and primary site and a minimum of 4 gigabytes (GB) for the secondary site. This memory is reserved by using the Minimum server memory setting under Server Memory Options and is configured by using SQL Server Management Studio. For more information about how to set a fixed amount of memory, see

The site server might be unable to publish to Active Directory. The computer account for the site server must have Full Control permissions to the System Management container in its Active Directory domain. You can ignore this warning if you have manually verified these permissions. For more information about your options to configure required permissions, see

Nothing missing, all good.

Select OK

Now let’s Install CM 2012 SP1 Beta straight off the media with no recourse to RTM then SP1

Select Install from the HTA


Select Next


Select Next


Select Install the evaluation edition of this product or tap in a product key

Select Next


Select I accept these license terms

Select Next


Tick all three, SQL Server R2 Express, SQL server 2008 native client and Silverlight prerequisite licenses

Select Next


If you’ve already downloaded the prerequisites then Select Use previously downloaded files or let it down them into an existing folder now

Select Next


The components will be verified


Select Next


Select Next


Punch in some details, mine is Lab 2 Primary 1 which translates into L21

Select Next


Select Install the primary site as a stand-alone site

Select Next


Handy tip that later on we can upgrade

Select Yes


Select Next


Select Next


Select Configure the communication method on each site system role

Select Next


Select Next


Select Join the Customer Experience Improvement Program

Select Next


Select Next


Prerequisite checker runs again, we know it’s all good

Select Begin Install


Dig out CMTrace from the installation media, open it and associate with log files

Click the View Log button in the dialog above to open up the installation log in real time, so that you can monitor the installation if you prefer looking at log files

You can return to the installer by clicking the following icon on the task bar



Install completed successfully

Select Close

Open the ConfigMgr 2012 SP1 Beta Console


There we go, a brand new ConfigMgr 2012 SP1 Beta site to play around with. The two components with warnings are benign

SP1 brings a lot of cool new stuff, 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

Share This Post


  1. Hi, very nice guide mate! just want to point out that I have followed your guide and I came across some small issues which I noted here:

    • Great post Rob, I am new in learning SCCM and this post solved lots of installation problem.

  2. Awesome post. I’ve been struggling for weeks to get this all installed and with your post I had it up and running in about 8 hours. Part of that was building a new virtual server to host the whole thing on.

    At work we are implementing SCCM 2012 and I need to learn to use it. Limited budget means I’ll pretty much have to teach myself how to use it.

    I have one warning showing up, SMS_DATABASE_NOTIFICATION_MONITOR. Call me anal but I’ll have to get rid of that before I move on.

    I found this guide helpful as well.

    Thanks very much.

  3. Jeroen, Dana, thanks for the feedback!


    Issue 1, it should support W12 domain functional level:

    Issue 2 is really ignorable for the lab guide, the product will run as SYSTEM post-instal and thus, use it’s computer account to interact with the AD and not your logged in user account, but really I could remove this by logging in as a domain account in future guides.

    Issue 3, I’ve never delegated in my labs, only set as described in the guide and the sites can publish fine, not sure why you see this, I’d like to know more about your AD setup?.

    Issue 4 Yes you’re right, I didn’t mention the WSUS ports but I thought they were now not an option as WSUS will default to the high ports, I usually mention this so … oops thanks for noting!

    Dana: Those SMS_DATABASE_NOTIFICATION_MONITOR status messages, go check them out in the status message viewer (invoked as a right click off one the component with the warnings\errors or via the ribbon), they should be about maintenance tasks that missed that days schedule for firing. You can clear these warnings, or let it tick over for a few hours and they will eventually go. Totally benign and won’t impact your evaluation experience 🙂

    I’ll make a new guide for SP1 RTM soon, and roll this valuable input into it, thanks!

  4. I’m getting a critical error and things don’t seem to be working quite right.

    WSUS Configuration Manager will not be able to configure WSUS Server “myserver.mydomain” as the WSUS Server remoting API’s of version 3.0 SP2 or greater are not installed on this site server.

    Also I’m getting messages about an inability to install something called: SMS_WSUS_CONTROL_MANAGER

    I downloaded the latest Windows Server 2012 Datacenter from TechNet along with the latest SCCM 2012 also SQL 2012. All were downloaded within the last week.

    hope you can help.

    • It may be the same issue Jeroen noted above, when you installed the Software Update Point role did you choose default or custom website?

      Need to use Custom website, uses ports 8530/8531 instead of 80/443.


      • Hi Rob;

        I suspect my problem is elsewhere but I will keep Jeroen’s point in mind as I configure the latest build of my server. The last build didn’t use the SCCM SP1. Now I’ve rebuilt the server for the 3rd or 4th time and hopefully I got it right this time. Will have to try configuring it tomorrow.

  5. Well I’m making headway. Prior to starting to configure the server I had all green in Site Status and Component Status. After configuring the Application Catalog web stuff I started getting the same errors that I had been getting before. After much research I came across a log file that indicated that needed to be installed. I checked Features and found that 4.x was installed but the earlier version wasn’t. So it started to install the earlier version. Then I thought to check the ASP service and found that it was not running. I set that to run automatically and started it and my problems cleared up. Not sure if the solution was the running service or installing the earlier version of the

    When I did the Forest discovery SCCM found my domain and setup everything real neat, however the computers listed in devices are not showing the site code and nothing I do will get the client installed on these computers. Any suggestions?

    Thanks again for a great post.

  6. Not sure that I saw that in my lab, most probably problem does exist but I’ve not taken it for a proper drive like you have or subconciously fixed it without noting hehe 🙂 Thanks again Dana! When SP1 RTM’s I’ll redo this guide … not long now!

  7. Lab: I have a DC vm and now i have a clean server 2012 where i am planning to install sql2012 and SCCM 2012SP1. As a first step you have :Give it a static IP address
    Join it to your AD domain. If i have DHCP on my DC do i need to assign static ip to sccm server?

  8. One more question. Do i need to install any updates to SQL 2012 SP1? CU is not for SP1? no features to update.
    Thank you,

  9. Hi Mike,

    1. Fixed IP or Dynamic, both work, but I tend to pin IP addresses to my VM’s entirely due to the way I set my labs up, go with DHCP if it is easier

    2. For CM12 SP1 you can install SQL2012 RTM CU2. They don’t specify a CU specifically, but CU3 is ok, the product does not currently support SP1.

    Here’s the SQL requirements from the documentation library:

  10. Jeroen: Forest discovery yields odd results in a Windows 2012 functional level forest. You can log in as a domain account with local administrator rights so that the AD check succeeds, but there is another issue if you put publishing site servers into an AD group and bind it to the permission list on the System Management container. They are just warnings and won’t stop the site becoming as operational as the death-star 🙂

  11. Dana, All, install ASP.NET 3.5 to complete the setup, I’ll make a new guide soon now that everything is RTM

  12. Hello,

    i want to say that this is the first tutorial what helped me out to do my school-job. We are now at a point that we must install and configure the SCCM. Realy nice tutorial. Great job,,,

Leave a Reply