This post outlines the implementation of Cumulative Update 1 for Configuration Manager 2012 R2 in a lab environment. Note that this update is applicable for R2 only, if you are currently still running Configuration Manager 2012 SP1 please refer to my previous blog post on implementing Cumulative Update 4 for ConfigMgr SP1.

The detailed description and download link for this Cumulative Update  are available here: http://support.microsoft.com/kb/2938441/en-us .

The CU is applicable directly to the following components:

• CAS
• Primary Sites
• Secondary Sites
• SMS Provider(s)
• Console(s)

Additionally it contains updates for the following components:

• CAS
• Primary Sites
• Secondary Sites
• SMS Provider(s)
• Consoles
• Clients

The lab infrastructure on which we will implement the CU is rather small: a standalone primary site with the site database and all site system roles installed on a single server. Additionally there is one remote Distribution Point. There are no secondary sites.

Primary Site

A CU implementation needs to be done from top to bottom so we start with the site server first.  Make sure there are no console connections open and then run the installer with elevated privileges.

The installation wizard is started:

Click Next on the welcome screen.

Accept the license terms and click Next.

Review all checks and click Next.

Leave the option to install the update for the console and click Next.

Leave the option to update the Site Database and click Next.

As part of the setup process Configuration Manager can create packages to update other components part of the environment. Leave the options to have these packages created and click Next.

Leave the default options for the first Update Package and click Next.

Leave the default options for the update package for consoles and click Next.

And finally also leave the default options for the remaining packages for clients. Click Next.

Review the setup summary and click Install to kick off the installation.

Installation progress is shown.

If you are interested in what is happening under the hood make sure to have a look at the installation log files in the %windir%\temp directory.

Click Next once all steps have been completed successfully.

Click Finish and restart the server.

In ARP there should be two entries indicating that the Cumulative Update was installed on the system: one for the site server and one for the console. Both are shown in the screenshot below:

Also in the registry the CU level for the site can be verified:

When opening the About Configuration Manager window from the console the version should show 5.0.7958.1203

Remember that at one point we opted to have packages created to implement the CU on other components. These packages are now available in the Software Library workspace:

Do not forget to distribute the content for these packages to your Distribution Points. This is not something that is done automatically!

 

Secondary Sites

If there are any Secondary Sites in your environment the next step is to implement the CU on those sites. The server update package can be used to automate this. To target the site servers a collection can be built which is populated based on the following query:

• select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name, SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,
  SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS_64 on SMS_G_System_ADD_REMOVE_PROGRAMS_64.ResourceId = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS_64.DisplayName = "System Center 2012 R2 Configuration Manager Secondary Site Setup"

Consoles

As part of the implementation process on the site server the locally installed console was updated as well. Any remote consoles in the environment can be updated using the console upgrade package which was automatically created during the installation process.

To build a collection containing the machines with the console installed the following query could be used:

• select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name, SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM. ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceId = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = "System Center 2012 R2 Configuration Manager Console"

Clients

Last but not least also the clients within the environment need to be brought up to the level of the Cumulative Update. There are multiple approaches to accomplish this; one method could be to deploy the client update packages which were also created automatically during the implementation process.

As there is a package per processor architecture we will also create matching collections to target our deployments. This is an example query for a collection containing all 64-bit clients with a client version not equal to CU1:

• select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name, SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,
  SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_SYSTEM on SMS_G_System_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_R_System.ClientVersion != "5.00.7958.1203" and SMS_G_System_SYSTEM.SystemType = "X64-based PC"

The query for the collection with 32-bit clients is identical; just replace “x64-based PC” with “x86-based PC”.

A client with the CU installed should have the following version displayed in the properties:

 

And the updated components:

 

 

That’s it! I hope this post gives you a good overview on how you could implement the Cumulative Update in your environment.

See you around!

Tim