Installing the System Center 2012 Configuration Manager Cumulative Update 1

Literally two days ago I wrote a quick blog post about the ConfigMgr 2012 cumulative update servicing model, but didn’t have an update\cumulative bundle to install so pretty much just blogged what I took from the documentation, well what do you know, a day later the first cumulative update bundle releases, so here’s a run through installing it along with my comments

Firstly before you install you need to do a couple of things:

Download the Cumulative Update 1 for System Center 2012 Configuration Manager from here (KB2717295)

Make a backup of your Site server. Never apply a cumulative update without having some kind of recourse for recovery, and nothing beats a valid ConfigMgr backup produced from the Backup Site server Maintenance Task as a free get out of jail card. Copy the backup to an alternative location to make it safe and out of harms way (backup runs again, wipes your important backup folder for example)

Now let’s install the cumulative update

Visit a Site server, I’ve chosen a Stand-alone Primary Site server, all actions below should be performed there locally

Launch the executable and choose the folder to expand the cumulative update into

Visit the newly created folder and launch the cumulative update file ConfigMgr2012-RTM-CU1-KB2717295-X64-ENU.EXE

image

It seems obvious but I’ll call it out, note the cumulative update has a unique KB ID

Right away we’re told where this cumulative update can be applied in its current form (notice that the Console and Client are not listed), and it also shows what type of targets the update applies too (which does include the Console and Client)

Select Next

image

Tick I accept these license terms

Select Next

image

A prerequisite checker is included, it validates the current system the patch is running on and gives me the OK to proceed

Included is a button for the installation log file, which has already been created by the update. If you have CMTrace registered, which you should, then click the log button to open the log file for viewing

This is what the log file looks like

image

Put the CMTrace window to the side and return to the Cumulative Update wizard

Select Next

image

Now, all the patches in the cumulative update can be uninstalled except for the SQL update. To roll out the SQL update you will need to restore a backup, which explains why backups should be treated with care and consideration. Make sure you have a backup in case the database update goes wrong. We do get the option to bypass the database update at this point, so that it can be performed manually at a later time, very hands on, gives us more options around dealing with the database

Select Yes, update the site database

Select Next

image

The cumulative update is going to help out by creating a bunch of packages so that you can deploy this cumulative update to Site servers, servers running a remote SMS Provider and Clients

Make sure all systems types are selected

Select Next

image

These updates are destined for systems, not users, so packages are created instead of applications

We get the option to define the package properties for the cumulative update going to Site servers and remote SMS Provider servers

Notice the path for the source files: \\labicm12.smslab.com\SMS_INF\hotfix\KB2717295\Server\x64

Select Next

image

Same again for systems running the Console

Select Next

image

And finally the package for the Clients

Select Next

image

Here’s what it spat out:

Cumulative Update 1 for System Center 2012 Configuration Manager RTM (KB2717295)

More Information: http://support.microsoft.com/KB/2717295
SQL Script: Yes
Run script during update installation: Yes
SQL Server: labicm12.smslab.com
SQL Database: CM_INF
Software Catalog: C:\Program Files\Microsoft Configuration Manager\hotfix\KB2717295\SCUP\2717295.cab

Deployment packages for clients will be created:
Package: Cumulative update 1 – x64 client update – INF
Program: Cumulative update 1 – x64 client update install
Package Source: \\labicm12.smslab.com\SMS_INF\hotfix\KB2717295\Client\x64

Package: Cumulative update 1 – x86 client update – INF
Program: Cumulative update 1 – x86 client update install
Package Source: \\labicm12.smslab.com\SMS_INF\hotfix\KB2717295\Client\i386

Deployment package for consoles will be created:
Package: Cumulative update 1 – console update – INF
Program: Cumulative update 1 – console update install
Package Source: \\labicm12.smslab.com\SMS_INF\hotfix\KB2717295\AdminConsole\i386

Deployment package for servers will be created:
Package: Cumulative update 1 – server update – INF
Program: Cumulative update 1 – server update install
Package Source: \\labicm12.smslab.com\SMS_INF\hotfix\KB2717295\Server\x64

Ok we’re ready to install

Select Install

image

We’re treated to a cool monitoring page showing us the status of each of the tasks needed to complete the update installation on the Site server

image

Select Next when everything has finished, I assume you get no errors at this point and that all tasks are a success

image

Install complete, Select Finish

Return to the updates log file

image

It shows us that the process completed, however the Site server is now buzzing with activity

Monitor the Site Component Manager log (SITECOMP.LOG) file on the Site server until all the components have been reinstalled

The SITECOMP log activity should settle down and look like this

image

Done, will take some time, 10 minutes or so

Now open the ConfigMgr 2012 Console

Visit the Software Library, expand Packages and expand the Configuration Manager Updates folder

image

Here are the four cumulative update packages, one for the Console, one for the Server, but two for the Client (X86 and X64)

The cumulative update package source files basically consist of a Windows Installer MSP file for the Console, an MSI for the Site server and MSP for the Client in both X64 and X86 forms

All four packages programs invoke typical MSIEXEC command lines such as

msiexec.exe /p configmgr2012ac-rtm-kb2717295-x64.msp /L*v %TEMP%\configmgr2012ac-rtm-kb2717295-x64.msp.LOG /q REINSTALL=ALL REINSTALLMODE=mous

You can deploy these packages to custom collections to target your systems

On the Site server and in the ConfigMgr installation folder you’ll find another folder called hotfix containing a folder for each update bundle applied

C:\Program Files\Microsoft Configuration Manager\hotfix\KB2717295

Listed in there are the files for the cumulative update, including a very handy CAB file for import into SCUP, so that you can deploy the updates as literal updates via the Software Updates feature (Software Update Management\WSUS\WUA)

C:\Program Files\Microsoft Configuration Manager\hotfix\KB2717295\SCUP\2717295.cab

I’ll check out importing this into SCUP and deploying via Software Updates in another blog post

I opened the Site server MSI to see what lives in there

image

SMSAPPINSTALL.EXE, along with DLL’s, SQL, MSI and MSP files. I didn’t see a setup.vbs as mentioned in the documentation for the servicing model feature

In the ConfigMgr console under Administration \ Sites and select your Site server, the properties of the site show the major version information only

image

Check out Sites properties

image

The version hasn’t changed, 5.00.7711.0000 is the RTM version string

This is no mistake, even the registry key for version is the same, thanks to John Marcum for confirming this on his lab build

image

The article for KB2717295 shows what versions the touched files will move too

image

If you go to your Site servers bin\x64 folder and check out the properties for SMSPROV.DLL, you’ll see the right version listed

image

If you visit Control Panel \ Programs on the Site server the cumulative update was just applied too, select Uninstall a program and finally select View installed updates you’ll see the cumulative update has been installed

image

Now if you run a Hardware Inventory on the Site server just patched, you’ll see the cumulative update appearing in Add/Remove Programs (X64)

image

Not sure why the version hasn’t changed, assume that the updates are not significant enough to update the product minor version number

Enjoy

email

Written by , Posted .