Upgrading to ConfigMgr 2012 SP1 CU4

Cumulative Update 4 (CU4) for ConfigMgr 2012 SP1 was released today (January 28, 2014). Info about the CU4 update is found here: http://support.microsoft.com/kb/2922875 

here follows a short guide on upgrading to it. The high-level steps are:

1. Check for pending reboots
2. Install the CU4 update
3. Update the boot images
4. Create/Update Client Package
5. Update Task Sequences

Check for pending reboots

The CU4 setup will stop if there are pending reboots on the server, and I rather check it first before launching the setup, using the Get-PendingReboot.ps1 PowerShell function available on TechNet. “"Load the function by "dot sourcing" the .ps1 file, as in the following example: “. .\Get-PendingReboot.ps1” (note there is a space between the first and second dot”). The run the Get-PendingReboot function. In the below example, my site server needed a reboot.

Running the Get-PendingReboot function on the site server (the function also supports the –ComputerName parameter).

Install the CU4 update

Installing the CU4 update is quite straight-forward, but as usual, make sure you have a backup of the site server in the very event something goes wrong. Cumulative Updates are less tested than full releases. Run the CM12-SP1CU4-KB2922875-X64-ENU.exe script, and complete the wizard. After the wizard is completed reboot the site server.

Initial Wizard Page.

Prerequisite check.

Installing CU4 on my site server.

Update the boot images

After the update is installed (and possibly server rebooted), you need to update the boot images. Right-click the boot image that you want to update, and select the Update Distribution Points action. Repeat for additional boot images.

Updating the boot images.

Create/Update Client Package

Since the CU4 update contains client updates, I recommend integrating those hotfixes in your client package. I usually create a separate client package anyway, and just add the hotfixes to it.

A custom ConfigMgr 2012 client package with hotfixes.

Update Task Sequences

To have the task sequence deploy the updates, use the PATCH option for the Setup Windows and ConfigMgr action. In the below example, I’m using PATCH="C:\_SMSTaskSequence\OSD\\Hotfix\KB2905002\KB2922875\x64\configmgr2012ac-sp1-kb2922875-x64.msp" for x64 task sequence. If you still are deploying x86 operating systems, you need to change to the i386 folder.

Configuring the task sequence to deploy the new client.