0

Microsoft SCCM 2012 R2 – Installing SCCM 2012 R2 and CU4

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.

01

Click Install

02

Click Next

03

Because I am using a remote SQL Server instance I didn’t tick the Use typical installation options. Click Next

04

Choose whether you’re installing the evaluation or enter a key. Click Next

05

Click I accept these license terms, Click Next

06

Accept all three licenses, click Next

07

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

08

Wait for the files to be downloaded.

09

Select the server language and click Next

10

Select the client language and click Next

11

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

12

As this is a stand-alone server I selected the second option. Click Next

13

Take note of the message and click Yes

14

Enter the details of the remote SQL server, click Next

15

Check the default locations, click Next

16

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.

17

Click Next

18

Select Configure the communication method on each site system role as I am not using a PKI infrastructure in this environment. Click Next

19

Click Next

20

Click Next

21

Click Next

22

It’s now running the pre-req check.

23

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

24

25

26

We can see that the installation was successful, click Close

27

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

28

Click Next

29

Accept the license and click Next

30

Click Next

31

Install the update to the console and click Next

32

Update the database, click Next

33

Select all three systems, click Next

34

Click Next

35

Click Next

36

Click Next

37

Click Install

38

39

Assuming you installed successfully click Next

40

Click Finish

41

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

Simon

Leave a Reply

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