Microsoft has now released Cumulative Update 3 (CU3) for ConfigMgr 2012 R2. More details about the Cumulative Update is available here. Follow the steps in this guide to install the Cumulative Update in your ConfigMgr 2012 R2 hierarchy or for your stand-alone Primary Site server.

As with all Cumulative Updates that has been released in the past, the recommended way to install it in your ConfigMgr hierarchy is from the top down. So if you’re running a CAS with a couple of Primary Site servers, you should start with by upgrading your CAS.

What’s new

With the release of CU3, Microsoft has finally provided us with a way of managing the Management Points a client can talk to. This is also known as Management Point Affinity, and it’s described more in detail in this blog post. This feature

Overview

  • Before you start with the update process
  • Download the CU3 update
  • Upgrade your CAS server
  • Upgrade your Primary Site servers
  • Upgrade your Secondary Site servers
  • Upgrade systems with the ConfigMgr console
  • Upgrade your Clients
  • Summary

Before you start with the update process

I recommend that you take a look at the following blog post called ConfigMgr Servicing model, by Brian Huneycutt. It gives you an idea what a Cumulative Update for ConfigMgr is and what it’s intended for.

Make sure that you have a backup of your databases before you go ahead and perform the update to CU3. This Cumulative Update contains changes to the site database, so the backup should preferably not be older than 1 day. You can check out this excellent blog post on how to perform backups of a ConfigMgr 2012 SP1 and above database. It’s also considered a best practice to make sure all the servers affected by this update are running with the latest updates from Microsoft. Finally, restart all your site servers that you will install CU3 on before you begin.

If you don’t have a CAS and are running a stand-alone Primary Site server, the steps shown in the Upgrade your CAS server below applies to a Primary Site server as well.

Download the CU3 update

1. You can request the Cumulative Update from Microsoft here. Extract the content to a preferred folder.
2. Copy the CM12-R2CU3-KB2994331-X64-ENU.exe file to all of your server where you’re will be performing the update. In this post it will be the CAS, Primary and Secondary Site servers.

Upgrade your CAS server

1. Run the CM12-R2CU3-KB2994331-X64-ENU.exe and click Yes in the UAC prompt.
2. Click Next on the Welcome page.

110_1

3. On the Microsoft Software License Terms page, accept the license terms and click Next.

110_2

4. On the Prerequisite Check page, make sure that all checks are green before you continue. Remediate any warning or errors. Click Next when ready.

110_3

5. On the Console Update Option page, make sure that Install the update for the Configuration Manager console is selected and click Next.

110_4

6. On the Database Update page, select Yes, update the site database if you have backed up your CAS site database before running the setup. Click Next when ready.

110_5

7. On the Deployment Assistance Options page, make sure all the options are selected and click Next.

110_6

8.On the Update Package for Configuration Manager Servers page, click Next.

110_7

9. On the Update Package for Configuration Manager Consoles page, click Next.

110_8

10. On the Update Package for Configuration Manager Clients page, click Next.

110_9

11. On the Setup Summary page, click Install.

110_10

12. The update process will now begin, wait for it to complete.

110_11

13. Once the update process has completed, click Next.

110_12

14. On the Installation Complete page, click Finish.

110_13

Now that the installation has successfully finished, open the ConfigMgr console and go to Software Library -> Application Management -> Packages -> Configuration Manager Updates and distribute all the newly created packages to your Distribution Points.

Note: Remember to update your Boot Images, since CU3 contains updated OSD files (thanks to Johan Arwidmark for pointing this out in his post about CU3).

Upgrade your Primary Site servers

The process of upgrading your Primary Site servers are exactly the same as for the CAS, so I will not go through that step by step. I recommend that you evaluate if you need to create all the packages on the Primary Site server(s), since they are already available on the CAS. Unless you run a stand-alone Primary Site server with no CAS, you should let the wizard create the packages for you.

Upgrade your Secondary Site servers

For Secondary Site servers, the process is not exactly the same. If you have alot of Secondary Site servers, I recommend that you look at the option to distribute the R2 CU3 – server update – <site_code> package that the installation wizard has created, either on your CAS or Primary Siteserver, to a collection with all your Secondary Site servers. This package would need to be distributed to your Distribution Points before you ahead and deploy the it. If you’re lucky enough and only have a few Secondary Site servers, you could just copy the installation file for the CU3 to those servers and update them one by one.

Upgrade systems with the ConfigMgr console

If you’ve installed the ConfigMgr console on any other servers than the site servers, create a collection with a Query membership rule as shown below. Create a deployment for the R2 CU3 – console update – <Site Code> to that collection, and the stand alone ConfigMgr consoles will be updated.

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 like "System Center 2012 R2 Configuration Manager Console" and SMS_G_System_ADD_REMOVE_PROGRAMS.Version >= "5.00.7958.1000"

Upgrade your Clients

In order to upgrade your Clients, you can create a collection with a Query membership rule as shown below. It’s important that if you have both x86 and x64 clients in your environment, that you create a collection for each architecture. In the same location as for where the ConfigMgr console upgrade package is located, you’ll find the R2 CU3 – x64 client update – <Site Code> and R2 CU3 – x64 client update – <Site Code> packages as well. Deploy each package to the correct collection in order to update your Clients. It’s highly recommended that you test the upgrade of your clients first, before you go ahead and deploy the update globally in your environment.

x86

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_SMS_ADVANCED_CLIENT_STATE on SMS_G_System_SMS_ADVANCED_CLIENT_STATE.ResourceId = SMS_R_System.ResourceId inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_G_System_COMPUTER_SYSTEM.SystemType like "x86-based PC" and SMS_R_System.Client is not null  and SMS_G_System_SMS_ADVANCED_CLIENT_STATE.Version >= "5.00.7958.1000" and SMS_G_System_SMS_ADVANCED_CLIENT_STATE.Version < "5.00.7958.1401"

x64

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_SMS_ADVANCED_CLIENT_STATE on SMS_G_System_SMS_ADVANCED_CLIENT_STATE.ResourceId = SMS_R_System.ResourceId inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_G_System_COMPUTER_SYSTEM.SystemType like "x64-based PC" and SMS_R_System.Client is not null  and SMS_G_System_SMS_ADVANCED_CLIENT_STATE.Version >= "5.00.7958.1000" and SMS_G_System_SMS_ADVANCED_CLIENT_STATE.Version < "5.00.7958.1401"

Summary

If you’d like to verify that the upgrade was successful, launch the ConfigMgr console and click on the menu and choose About Configuration Manager. If the version is 5.0.7958.1401, the upgrade has been installed. The picture below is taken from a Client that has been upgraded to CU3.

110_14

Nickolaj Andersen
Principal Consultant and Enterprise Mobility MVP. Nickolaj has been in the IT industry for the past 10 years specializing in Enterprise Mobility and Security, Windows deployments and Automation. In 2015 Nickolaj was awarded as PowerShell Hero by the community for his script and tools contributions. Author of ConfigMgr Prerequisites Tool, ConfigMgr OSD FrontEnd, ConfigMgr WebService and a frequent speaker at user groups.

(98)

comments
  • seb
    Posted at 20:24 October 1, 2014
    seb
    Reply
    Author

    hi great post it’s very complete thanks for sharing! what would be your approach for client update during Os deployment? Do you do it during task sequence (and how exactly) or after the computer is deployed?
    thanks again!

  • Steve
    Posted at 17:05 November 5, 2014
    Steve
    Reply
    Author

    Thank you for this!

    One question…We have clients that are still receiving the KB2910552 hotfix through package deployment. Since this also updates the TS component, is it safe to stop the deployment of the 0552 hotfix and just jump clients to CU3?

  • justin
    Posted at 16:44 May 5, 2015
    justin
    Reply
    Author

    what about site systems/servers, how do i upgrade those? or do they not have to be upgraded?

    thanks.

    • Nickolaj
      Posted at 16:49 May 7, 2015
      Nickolaj
      Reply
      Author

      Hi Justin,

      That’s not something you need to worry about, if there’s an update for e.g. a DP the Site server will take care of that automatically. You only need to upgrade Central Sites, Primary Sites, Secondary Sites, ConfigMgr Console’s and the clients.

      Regards,
      Nickolaj

  • Leave a Reply