Microsoft has now released Cumulative Update 2 (CU2) for ConfigMgr 2012 R2 SP1. Follow the steps in this guide to install the Cumulative Update in your ConfigMgr 2012 R2 SP1 hierarchy or for your stand-alone Primary Site server including Secondary Site servers. Be aware that you’d have need to updated your ConfigMgr 2012 R2 environment to SP1 before you can install this Cumulative Update.

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.

Update 2015-11-16: Re-download the CU2 installation setup. More details here:

What’s new

Cumulative Update 2 contains a lot of fixes, but also some general improvements in areas that are very much awaited for. You can read more about them here. Previously, the PowerShell module was also updated, but since that’s now a separate download (Configuration Manager Cmdlets Library), it’s not included. Below is a segment from the blog post by Microsoft regarding the release of this Cumulative Update, on some of the improvements:

  • General performance improvements to the device enrollment process in Intune hybrid environments.
  • More efficient processing of pull-distribution point packages in large environments.
  • Simplified  quarantine email experience to allow one-click enrollment. With this update, end users can click a single link in the quarantine email to complete the enrollment process within the company portal app.

You can read the full blog post from Microsoft on the link below:


  • Before you begin
  • Download the CU2 update
  • Upgrade your CAS server
  • Upgrade your Primary Site servers
  • Upgrade your Secondary Site servers
  • Verify Installation
  • Upgrade systems with the ConfigMgr console
  • Upgrade your Clients
  • Summary

Before you begin

I recommend that you take a look at the following blog post called ConfigMgr Servicing model, by Brian Huneycutt. It givesyou 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 CU2. 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 CU2 on before you begin.

Download the CU2 update

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

Upgrade your Central Administration Site

In the rare event that your environment contains a Central Administration Site (CAS), you should begin with applying the CU2 at that site. It’s required that you always apply a Cumulative Update from the top down in a hierarchy. The following steps below outlined for the Primary Site server applies to the CAS as well. After you’ve applied the Cumulative Update, make sure that your Site server is in a functioning state before you continue upgrading your Primary Site servers.

Upgrade your Primary Site server

Before you go ahead and install the Cumulative Update, I highly recommend that you turn on the Automatic Client Upgrade feature in your hierarchy. This will allow for a smooth and seamless upgrade of your clients, in other words, automatic. Since ConfigMgr 2012 R2 SP1, the Cumulative Update installation wizards will automatically create a ClientUpdate folder for both architectures in the default Configuration Manager Client Package if you select that option, which is something that I recommend that you do.

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


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


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.


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


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.


7. On the Automatic Client Update page, select to Automatically apply. This is what I was referring to earlier when I talked about the Automatic Client Upgrade feature. If you’ve not enabled that in your environment, you’ll not see this page during the installation wizard.


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


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


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


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


12. On the Setup Summary page, click Install.


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


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


15. On the Installation Complete page, click Finish.


16. The first time you launch the ConfigMgr console after you’ve applied the Cumulative Update, you’ll see that there’s new extensions for Microsoft Intune that needs to be installed. Click Yes in the prompt.


17. Wait for the extensions to be installed.


18. Once they’ve been installed, click Close.


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.

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 CU2 KB3100144 – server update – <site_code> package that the installation wizard has created, either on your CAS or Primary Site server, to a collection with all your Secondary Site servers. This package would need to be distributed to your Distribution Points before you go ahead and deploy the it. If you only have a few Secondary Site servers, you could just copy the installation file for the Cumulative Update to those servers and update them manually. If you decide to upgrade your Secondary Sites manually, the process will be familiar as for the CAS and Primary Site, except for that there are less pages to go through.

Verify Installation

Obviously the installation wizard will tell you if the installation was successful, but there are additional ways of verifying that the upgrade process was successful.


On your Site server check the following value called CULevel, found under HKLM\Software\Microsoft\SMS\Setup. It should contain the value of 2.


Site Properties

When you go to Administration -> Site Configuration -> Sites and right-click to select Properties of the Site server that you just upgraded, the Version number will show 5.00.8239.1000. That’s because the Site version is not changed when you apply a Cumulative Update. If you’ve verified that the CULevel value was set to the corresponding version of the Cumulative Update, your Site was successfully updated.



If you open the ConfigMgr console and click on the menu in the top left corner, select About Configuration Manager. The console version should show 5.0.8239.1301.


Upgrade systems with the ConfigMgr console

If you’ve installed the ConfigMgr console on any other servers or workstations than the site servers, create a collection with a Query membership rule as shown below. Create a deployment for the CU2 KB3100144 – 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.8239.1301"

Upgrade your Clients

When your whole hierarchy consisting of Site server are upgraded with Cumulative Update, you need to upgrade your Clients as well. Ronni Pedersen has created an excellent blog post that covers the Automatic Client Upgrade feature, which can be found here:

To enable this feature, go to Administration – Site Configuration and select Sites. Click on Hierarchy Settings and go to the Automatic Client Upgrade tab.


I highly recommend that you make use if this feature, unless that you want to create your custom Client Upgrade Package specifying the necessary parameters for ccmsetup.exe which are required in your environment, or manually deploy the CU2 KB3100144 – x64 client update – <Site Code> package including the x86 package. If you choose to use this feature, remember to not set the Automatically upgrade clients within days value too low, as it might cause an extra load on your Site servers when too many clients are trying to upgrade at the same time. If you for instance set the value to 2, all of your clients with a lower build number than the site that it’s assigned to will retrieve the policy and create a local task to run within a randomized time frame between 1-2 days.

Also remember that if you choose to create your own Client Upgrade package, ccmsetup.exe will automatically detect whether the Operating System architecture is 32-bit or 64-bit, so there’s no need to create collections that contains architecture specific clients.

If you still want to manually deploy the client update packages created by the installation wizard, here’s two collection queries to use:

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.7711.0000" and SMS_G_System_SMS_ADVANCED_CLIENT_STATE.Version = "5.00.8239.1301"
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.7711.0000" and SMS_G_System_SMS_ADVANCED_CLIENT_STATE.Version = "5.00.8239.1301"

Below is a query that you can use to create a collection containing all clients that has been upgraded to the latest version:

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 where SMS_R_System.Client is not null  and SMS_R_System.ClientVersion = "5.00.8239.1301"

Below is a screenshot of a client that has been upgraded with the Cumulative Update, showing version 5.00.8239.1301:



Nickolaj Andersen

Principal Consultant and Enterprise Mobility MVP since 2016. Nickolaj has been in the IT industry for the past 10 years specializing in Enterprise Mobility and Security, Windows devices and deployments including automation. Currently working for TrueSec as a Principal Consultant. Awarded as PowerShell Hero in 2015 by the community for his script and tools contributions. Creator of ConfigMgr Prerequisites Tool, ConfigMgr OSD FrontEnd, ConfigMgr WebService to name a few. Frequent speaker at conferences and user groups.

  • Mac
    Posted at 10:20 November 11, 2015

    Great article as always…. however, I having problems completing mine. The warning is the fact that “CU2 thinks the update is already installed on the computer. Only options to create deployments for this update are available.”

    When I get to the install part, it fails to create software update catalog…. no installation package is create and fails all together.

    hope you can assist as I really need the fix for the FOREST TRUST to work for the project I am working on…

    thanking you in advance.

    • Mac
      Posted at 11:37 November 11, 2015

      I got this sorted in the end… I think the reboot and removing the cu resolved it. thanks…

  • David Okeyode
    Posted at 12:26 November 24, 2015
    David Okeyode

    Excellent writeup!!! Thanks 🙂

  • Joe S.
    Posted at 17:17 November 24, 2015
    Joe S.

    The correct version should be 5.0.8239.1302, not 5.0.8239.1301, correct?

    Also, you mentioned: “you need to upgrade your Clients as well.” You don’t need to upgrade the clients. You can choose not to and they will still work. However, if you want to take advantage of the fixes mentioned in the “Description of CU 2…” blog on MS’s site, then you’ll have to upgrade. Same can be said for updating boot images and the SCCM Console.

  • Nickolaj
    Posted at 09:48 November 25, 2015

    Hi Joe,

    In fact my clients that were upgraded before the re-release of CU2 was 1301. I’ve not installed any new clients to verify that they’re now 1302, but you might be on to something there, since the console version is now 1302.

    I’d counter regarding the fact that you’re saying that you don’t need to upgrade the clients. It’s a general best practice to always run your clients aligned with the Site server version, meaning that if you install a Cumulative Update, you should also install that for your clients, whenever applicable.

  • Ruben Garcia
    Posted at 13:30 December 4, 2015
    Ruben Garcia

    Hi. Thanks for this information. It was very useful for me. I have one question. You said if I choose the option “upgrade clients automatically…” is not necessary to deploy the clients update packages. It works, at leas for me. But I was a little confused because you send us a link to another post where the author says: “It means that automatic client “Upgrade” will NOT automatically apply cumulative “Updates” to your clients! You must use the packages created by the CU installation process to update your clients”.

    The option suggested by you worked for me!!!.

    Finally I would like to ask about the query to obtain ConfigMgr console installed in another clients it should not be sign?

    Thanks again for taking your time for this post.

  • Cassie
    Posted at 23:27 December 8, 2015

    This actually answered my problem, thankyou!

  • Dwight
    Posted at 20:38 December 14, 2015

    Thanks for the great article. Is anyone else experiencing issues since the update to CU2? I have been seeing slowness in the system (spikes in CPU and memory) Additionally, I have clients who say they upgrade successfully but now will not run our monthly patch deployment. I ended up having to reinstall the client, uninstall it again, and then install it and let it upgrade again. It now appears to be working properly from what the logs say.

    Another issue is where we push updates or a software package and noone updates. We have to remove and recreate the deployment for any of the sites as they will stay at 0% compliant otherwise. This was kind of Post CU1 / Pre-CU2 really.


  • Brian
    Posted at 16:00 January 25, 2016


    The Query Deploy the Console update looks like it does not work.
    The issue is that even after the console update has been applied to a pc, it still shows as 5.00.8239.1000 in the version section of Add/Remove Control Panel.

    • Dwight Brookland
      Posted at 15:23 January 27, 2016
      Dwight Brookland

      Your Console version should be at 5.0.8239.1302 and your site version should stay the same. Open the console and look in about System Center Configuration Manager. If it still shows wrong then remove and reinstall manually from original install location to validate that your site server fully updated.

  • Eden Oliveira
    Posted at 16:04 March 17, 2016
    Eden Oliveira

    Hi Nickolaj. I would like to thank you one more time for all the support you provide to us, really appreciated.

    I have a question regarding MDT 2013 U2 and ConfigMgr 2012 R2 SP1 CU1.

    In my environment, I have MDT 2013 U1 Integrated with ConfigMgr 2012 R2 SP1 CU1. I deploy normally windows 7 and Windows 10.

    My question is: If I upgrade my MDT 2013 U2 and integrate it on my ConfigMgr 2012 R2 SP1 CU1 Server. Is MDT 2012 U2 compatible with my Old ConfigMgr 2012 R2 SP1 CU1 or in order to perform the MDT integration, I will need to have ConfigMgr 2012 R2 SP1 CU2 or 1511?

    Thank you

    Eden Oliveira

  • Leave a Reply

    This site uses Akismet to reduce spam. Learn how your comment data is processed.