Monthly Archives: February 2015

An alternative guide for applying CU4 for ConfigMgr 2012 R2

Recently, Cumulative Update 4 for System Center 2012 R2 Configuration Manager 2012 was released. A release like this generally spawns a lot of tweets, blogs, tweets about blogs and their respectable retweets making it hard to miss. It also allowed me to check out which guides are written. While these guides are generally a good way to start, I did notice they generally have the following properties in common:

  • Packages are created containing the updates
  • Device collections are created to deploy them to
  • Optionally, the PATCH=<blabla fix.msp> is used in a task sequence

I try to achieve a matter of simplicity as much as possible and I also try to facilitate a ‘fire and forget’ mechanism as well. If System Center Updates Publisher (SCUP) 2011 is used, then deploying this update becomes much easier. The following location provides a guide that can be used to install SCUP 2011:

When SCUP 2011 is used, applying CU4 goes a little bit different. Here are the steps how to do it, assuming the hotfix is downloaded and accessible by the site server. I used as a reference.

Before starting, verify a valid backup is available.

First, the update must be applied to the site server.

Log on the Configuration Manager site server with a user account that has administrative privileges to execute the update.


Start the .exe file to start installing the cumulative update.


Select Next.


Accept the License Terms en select Next.


The prerequisite check verifies if all prerequisites are met. In this screenshot a previous software installation needs to be restarted to be completed. In this case the installation may continue by pressing Next.


The installation is run on the site server which runs the Configuration Manager console. Make sure the checkbox is filled in and press Next.


Select Yes, update the site database and press Next.


The distribution and deployment will be done using Software Updates, this means the packages are not going to be used. To prevent them from creating, uncheck each checkbox and press Next.


Review the summary and select Install.


Installation in progress…


After a few moments the installation is finished successfully. Select Next to continue.


Press Finish to close this window

System Center Updates Publisher 2011 (SCUP) allows publishing updates to WSUS in conjunction with Configuration Manager that are not published by Microsoft Update. Catalogs are used to import these updates to SCUP 2011 which are then published to WSUS. The cumulative update contains a catalog that can be imported into SCUP 2011.

Start SCUP 2011, make sure to start this application by the Run as administrator feature.


Select the Import button.


Browse to the catalog file (.cab) and press Next.


Press Next.


The security warning pops up. Because Microsoft delivers this hotfix, it is safe to trust them by pressing the Accept button.


The updates are imported successfully. Select Close to close this window.


The updates are now visible in the Console. Select the updates and choose Assign.


The publication type must be Full Content. Create a new publication as displayed and press OK.


In the Publications tab, select the newly created publication and press the Publish button.


Press Next.


Review the summary and press Next.


Publishing in progress…


The updates are published successfully. Press Close to close the window.

All tasks in SCUP are completed and the SCUP console can be closed.


The final step is distributing the updates for deployment.

The following Software Updates synchronization should pick up the newly published updates. Review the wsyncmgr.log file to verify the updates are synchronized by Software Updates.


Yes, there they are…


It is recommended to have a separate Automatic Deployment Rule which is targeted to the All Desktop and Server Clients device collection. In this scenario, it is not scheduled to run automatically since it rarely has to run. Select the Run Now option to run the Automatic Deployment Rule.


Press OK to confirm.


Verify the newly published updates are part of the Deployment Package. Once present and distributed, Configuration Manager clients are able to download and install the updates automatically. The client itself will determine which particular updates are needed.

That’s it. Feel free to try this method in a test environment before applying this in a production environment.

Steve Thompson [MVP]

The automation specialist

Boudewijn Plomp

Cloud and related stuff...

Anything about IT

by Alex Verboon

Deployment Made Simple

Modern Workplace

Azure, Hybrid Identity & Enterprise Mobility + Security

Daan Weda

This site is all about System Center and PowerShell

IT And Management by Abheek

Microsoft certified Trainer -Abheek

Heading To The Clouds

by Marthijn van Rheenen