In the first three posts of my SCCM 2012 R2 posts I covered the Active Directory, SQL and Windows requirements to install Microsoft SCCM 2012 R2 in a lab environment.
SCCM 2012 R2 Pre-requisite installs part 1 Covered Active Directory and Schema Extensions
SCCM 2012 R2 Pre-requisite installs part 2 Covered SQL 2012 Additional Feature Installs (Reporting Services)
SCCM 2012 R2 Pre-requisite installs part 3 Covered the Windows 2012R2 Requirements for SCCM 2012 R2, this includes IIS, WSUS and ADK
In part 4 I cover the installation of SCCM 2012 R2 and the recently released Cumulative Update 4 (CU4).
Installing SCCM 2012 R2
The installation of SCCM 2012 R2 is fairly straight forward, using either the ISO or installation media run the splash.hta file to launch the installer.
Because I am using a remote SQL Server instance I didn’t tick the Use typical installation options. Click Next
Choose whether you’re installing the evaluation or enter a key. Click Next
Click I accept these license terms, Click Next
Accept all three licenses, click Next
Choose a location to store the download files or point to a location if they already exist. In SCCM 2007 the folder had exist to continue but I have to be honest and say I didn’t check here. Click Next
Wait for the files to be downloaded.
Select the server language and click Next
Select the client language and click Next
Define your 3 digit site code and site name, Microsoft have some names that cannot be used as the site code and they can be found here.
Install the console on the server if required then click Next
As this is a stand-alone server I selected the second option. Click Next
Take note of the message and click Yes
Enter the details of the remote SQL server, click Next
Check the default locations, click Next
If you get this message check that the account you’re using to install SCCM 2012 R2 also has the sysadmin role on the SQL server then check again.
Select Configure the communication method on each site system role as I am not using a PKI infrastructure in this environment. Click Next
It’s now running the pre-req check.
It’s discovered one warning however due to certain VMware infrastructure requirements that require SQL authentication we need to ignore this and click Begin Install
We can see that the installation was successful, click Close
Now prior to running SCCM 2012 R2 I am going to check the current CU (Cumulative Update) version that I am running.
There are a couple of ways to do this but the easiest and fastest is simply to do a reg query from the command line.
reg query hklm\software\microsoft\sms\setup\ /v culevel
Running the above command will display the currently installed CU level (in our case it’s 0) so that means we need to installed CU4.
Installing SCCM 2012 R2 CU4
Cumulative Update 4 can be found via the following link – http://support.microsoft.com/kb/3026739
Download the file locally and run it to start the installation
Accept the license and click Next
Install the update to the console and click Next
Update the database, click Next
Select all three systems, click Next
Assuming you installed successfully click Next
Run the reg query again to check the CU Level, here we can see that we are now running CU4.
That completes the SCCM 2012 R2 Installation Posts, yes they only cover the requirements and actual installation and doesn’t cover the configuration and use of SCCM (it’s a big heavy product and I am only going to be using it for the immediate future as a patching resource for my Windows estate, no bare metal \ VM builds via OSD or Application Deployments.
I may in the future return to SCCM 2012 and post additional blog posts but my main concern for the next few posts is going to be around VMware’s vRealize Automation Suite and vSphere 6