System Center Configuration Manager 2012 is another of the big releases in the System Center suite this year, and promises to deliver a lot of exciting new functionality.
I’m already running SCCM 2007 SP2 R3 in my home lab environment, so I’m keen to find out how SCCM 2012 performs. Here’s my step-by-step installation experience…with screenshots! Oooo….
UPDATE 08/03/2012 (that’s March 8th for my US readers!) – I’ve recently written about installing SCCM 2012 on Windows 8 Server. The process I used there to install the server prerequisites using PowerShell is a better system than the one I originally described here. So read that first 🙂
Information about SCCM 2012 system prerequisites are still being released, and the in-built prerequisite checker doesn’t ship with the Beta 2 installation media. However, from what I’ve been able to ascertain, the following is required on the system designed to be the Primary Site server:
- .NET Framework 3.5 (Feature)
- .NET Framework 4.0 (Windows Update)
- WSUS SDK (Role – either the full WSUS installation or just the administration console – you can install this later, it’s not an installation showstopper)
- Microsoft Remote Differential Compression (Feature)
- IIS (Role – see below)
- BITS (Feature)
Important Note #1 – An SCCM 2012 infrastructure has similar PKI certificate requirements for HTTPS communications. Read my blog post here on how to set this up.
Important Note #2 – The site SQL server needs to be running SQL Server 2008 SP1 with CU10 or higher (SQL Server 2008 SP2 and SQL Server 2008 R2 are not supported, bizarrely) and firewall exceptions are needed either for the SQL application or for TCP ports 1433 and 4200. Additionally, the AD computer account of the site server needs to be added to the local Administrators group on the SQL server.
Important Note #3 – The required IIS Role Services are:
- Common HTTP Features – Static Content, Default Document, Directory Browsing, HTTP Errors, HTTP Redirection (note, no WebDAV! Woohoo!)
- Application Development – .NET Extensibility, ISAPI Extensions
- Health and Diagnostics – HTTP Logging, Logging Tools, Request Monitor, Tracing
- Security – Windows Authentication, Request Filtering
- Performance – Static Content Compression
- Management Tools – IIS Management Console, IIS Management Scripts and Tools
- IIS 6 Management Compatibility – IIS 6 Metabase Compatibility, IIS 6 WMI Compatibility
Important Note #4 – The Active Directory schema has to be extended as per SCCM 2007 (read this TechNet article on how to do this). If the schema has already been extended, you will just have to give the AD computer account for the primary site server (the SCCM 2012 site server, that is) Full Control rights to the System Management container using ADUC:
Now…on with the installation…
I’m going with the default installation options selected. I’m not doing a typical installation because I want to nominate a different SQL server:
Enter the license key (automatically entered, in the case of beta media) and accept the EULA. Then, download the latest product updates for use during installation:
Enter the details for the new Primary Site:
I don’t have a central administration site server (no existing SCCM 2012 hierarchy), so this will be installed as a standalone site:
Enter the SQL server details:
Choose the SMS provider:
Accept the client/server communications default, which is that all communications have to happen over HTTPS (there’s a PKI in the lab environment, so this is all fine – see the important note above):
Select the Management Point and Distribution Point:
The next screen (which I unaccountably forgot to capture) summarises what you’ve selected so far, and then you’re prompted to commence installation. At this point it launches the system readiness checker – the same feature which was disabled in the autorun splash screen (go figure). This is really, REALLY useful for making sure that you’ve got everything installed, although some checks are less than thorough (it didn’t pick up the fact that the SQL server wasn’t listening for incoming connections, for example).
Installation takes a while to complete (around 30 minutes) but you can keep launching the logfile throughout the process to see where it’s up to.
Once done, the Console launches and we are done!
That’s it for installation – now there’s lots of work to do with configuring and getting clients chatting, but that’s for another series of posts 🙂