Installing Cumulative Update 1 for System Center 2012 R2 Configuration Manager

Cumulative Update 1 for System Center 2012 R2 Configuration Manager has been released by Microsoft.  To download and get more detailed information about what this update fixes please visit the official Microsoft KB Article, http://support.microsoft.com/kb/2938441.

I will walk through how to update a primary site with a single site server.  How to create custom collections to deploy those updates to clients. How to update the boot images after the update has been applied and how to verify the update has been applied.

Please be aware that with cumulative updates, the clients will need to have the update deployed to them separately.  If you have the Auto Update Client feature enabled that will only update clients with a major service pack is installed.

Installing The Update

The following are basic step by step instructions on how to install the cumulative update.  I left all the settings default, however there are some settings you may want to look at for your environment.

  1. The first step is to download the cumulative update from Microsoft’s site.  You can find the update here. Download and extract the file to location on the site server.
  2. Run CM12-R2CU1-KB2938441-X64-ENU.exe
3. Click Next, this is just your standard welcome screen.  The window will give you links to more information about this update, etc.. image
4. Agree to the license terms and click Next. image
5. Click Next after all the prerequisites have passed. image
6.  By default the “Install the update for the Configuration Manager console” is selected.  I will leave this option checked. image
7.  This is where your team needs to discuss all the possible issues with upgrading your database.  This step has to be done but make sure you have taken a good backup before you do this.  Leave the bullet for Yes, update the site database and click Next. image
8.  This next step will auto create the needed packages that you will then need to deploy.  Click Next. image
9.  Here you can customize the name of the package that the installer will create for your site servers and computers that run the SMS provider.  Click Next. image
10.  Here is where you can customize the name of the package that needs to be deployed to all computers running the Configuration Manager console.  Click Next. image
11.  Here you can customize the package names for both client installs that will need to be deployed.  Click Next. image
12.  This is the summary screen.  Double check your settings and click Install. image
The installation progress window will show us the current status of the installation.  I use CMTrace to view the logs.  It is a nice way to see what is going on in the background.  If you click “View Log” it will open the log in your default log viewer.  As for me, CMtrace is my default log viewer, why is it not yours? image
image
13.  The installation is successful with no errors.  Click Next. image
14.  Click Finish and Reboot your site server. image

At this point we are ready to install the update to your other site servers, the clients, and the systems that may have the console installed.  We should also update the boot images as well.  Below, I will go into how to create custom collections to help with the deployment of the updates and how to update the boot images as well.


Creating Custom Collections

I will create the following 6 new custom collections that will help deploy the cumulative update.  The below chart shows the name of my new collections and the type of membership rules they have.  For smaller organizations some of these collections may not be needed depending on the hierarchy design.

Collection Name
Membership Type
Central Administration Site Server Direct Membership
All Primary Site Servers Direct Membership
All Secondary Site Servers Direct Membership
All x86 Clients Query Membership
All x64 Clients Query Membership
Computers With Configuration Manager Console Direct Membership
Remote Computers with SMS Provider Installed Direct Membership

 

The following are the queries you can use for the x86 and x64 client collections:

x86

Select * from SMS_R_System inner join SMS_G_System_SYSTEM on SMS_G_System_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_SYSTEM.SystemType = “X86-based PC”

x64

Select * from SMS_R_System inner join SMS_G_System_SYSTEM on SMS_G_System_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_SYSTEM.SystemType = “X64-based PC”

 

image


Deploying Updates using Software Deployment

We can now deploy the update packages the installer created to the collections we just created.

  1. To deploy these packages from the Configuration Manager console click on the Software library Workspace.
  2. Expand the Application Management Folder
  3. Expand Packages
  4. Click on Configuration Manager Updates folder.image
  5. Right click the first package R2 CU1 – Console Update – SITE and then click Deploy
  6. Under the Deploy Software Wizard Window select the collection that we will be deploying this package to.  For this package we will be deploying it to the “Computers with Configuration Manager Console” collection we pervious created. Click Next.
  7. If by this point you have not already added content destination, then we will added our distribution points to the proper distribution group/distribution points.
  8. Click Add and select Distribution Group or Distribution Point
  9. Select the proper groups or distribution points you want to assign this package to.
  10. Click OK and then click Next.
  11. On the ‘Specify settings to control how this software is deployed” select the appropriate purpose and optional settings.  Depending on your environment these settings will vary.  For this example I will leave the default Required setting and click Next.
  12. Specify the schedule you would like for this deployment.  In most cases you will have pre-defined internal policies on when and how you can deploy updates, applications, etc..  For this example I will add As soon as possible to the assignment schedule and leave everything else default.  Once again, you should already have some policies in place within your organization for change control.
  13. On the User Experience window, since we have made this deployment  “Required” giving the user any control isn’t necessary. However, you can check the box that Allows users to run the program independently of assignment.
  14. Since this is a required deployment I will also allow this installation to be performed outside of the maintenance windows.  ***Note, this probably should be communicated first to employees receiving this update for their console.***
  15. Click Next
  16. Click Next on the Distribution Points window.  You may need to change some of these settings depending on your environment.
  17. Click Next on the Summary Window.
  18. Click Close on the Completion Window.

You will want to repeat the steps above for the remaining site roles and clients as well.  So for R2 CU1 – x64 Client Update you would deploy it to the All X64 Clients collection, the R2 CU1 – x86 Client Update you would deploy to the All X86 Clients collection.  The R2 CU1 – Server Update package you would then deploy to the following collections: All Primary Site Servers, All Secondary Site Servers, Central Administration Site Server, and Remote Computers with SMS Provided Installed.

My advice in choosing between  ‘Required’ or ‘Available’ deployment on those servers is to go with ‘Available’.  My best practice is to make the deployment available and then manually run the software deployment from the servers themselves.  This prevents the update from kicking off and unintentionally interfering with production usage of the servers.

As for the clients, I would make them “Required” with no user notification.

 


Updating Boot Images

Once we have updated our site server we will also need to update our current boot images.  To update our boot images follow these steps:

  1. Open the Configuration Manager Console and click on Software Library workspace.
  2. Expand the Operating systems folder.
  3. Click on Boot Images
  4. Select the boot image that we are going to update
  5. Right-click and then select the Update Distribution Points action.
  6. You will need to repeat these steps for all boot images that were previously distributed.

Just a warning, doing this may cause some network issues for your remote sites.  Plan to do this off hours when possible if you have slower connections at your remote sites where these boot images will be updated.

 


How to verify if computer has Cumulative Update 1 installed

How to determine the installation status of this cumulative update

This cumulative update changes the following Configuration Manager version numbers and installation properties.

Site systems
The CULevel value is located under the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Setup

Note The CULevel value is set to 1 for Cumulative Update 1.

Administrator Console
The version that is displayed in the About System Center Configuration Manager dialog is 5.0.7958.1203.

Client
The version that is displayed on the General tab of the Configuration Manager Control Panel item or the Client Version field of device properties in the Administrator Console is 5.00.7958.1203.

 

Endpoint Protection Client
This update brings the anti-malware client version to 4.5.0216.0. You can find the version information by clicking About on the Help menu of the Endpoint Protection client UI.

Advertisements
Tagged with: , , , , , , , ,
Posted in Configuration Manager 2012 R2, SCCM 2012 R2, System Center 2012 R2
2 comments on “Installing Cumulative Update 1 for System Center 2012 R2 Configuration Manager
  1. URL says:

    … [Trackback]

    […] Read More: kristopherjturner.com/2014/04/12/installing-cumulative-update-1-for-system-center-2012-r2-configuration-manager/ […]

    Like

  2. […] installed CU3 you can find it here KB2994331.  I have previously written a blog on how to install Cumulative Update 1 for ConfigMgr 2012 R2 but plan to revise that blog with more information and better ways to build collections based off […]

    Like

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow Kristopher Jon Turner on WordPress.com
Archives
%d bloggers like this: