Microsoft has released another Cumulative Update for SCCM 2012. Learn how to update SCCM 2012 to the latest version by upgrading site components, deploying the new client, and managing consoles.

Joseph Moody

Joseph Moody is a network admin for a public school system and helps manage 5,500 PCs. He is a Microsoft Most Valuable Professional (MVP) in Cloud and Datacenter Management and blogs at DeployHappiness.com.

If you aren’t installing Cumulative Updates for SCCM 2012 SP1/R2, you are setting yourself up for a lot of extra work! Issues that you have with SCCM are likely fixed with one of these updates. This is especially true if you plan to start using a role in SCCM (for example, operating system deployments). Instead of spending hours troubleshooting a problem, keep your SCCM infrastructure updated and avoid the problem altogether!

Cumulative Updates should not be thought of as a standard single issue hotfix. Rather, they are a collection of fixes and feature enhancements. Today, we are going to install Cumulative Update (CU) 3 for SCCM 2012 R2. These steps are the same for 2012 SP1 and are identical for nearly all CU installations.

A SCCM 2012 R2 environment without the current Cumulative Update.

A SCCM 2012 R2 environment without the current Cumulative Update

Getting the correct SCCM Cumulative Update and installation checklist ^

CU3 for SCCM 2012 R2 can be downloaded from here. If you are unsure of the latest available CU for your product, check out the Configuration Manager Team Blog. All CUs are announced there.

Before installing the update, you need to check your site status, back up your database, and ensure all pending reboots are cleared. Launch the Configuration Manager console and navigate to Monitoring/System Status/Site Status. All roles should be normal. If you have any roles in a warning or error state, resolve those issues now.

Site Status showing a healthy Configuration Manager environment

Site Status showing a healthy Configuration Manager environment

Ensure that you have a recent backup of your SQL database, as this CU will make changes to the database. If you do not currently back up your SQL database, read more about backups in Configuration Manager 2012 here. Finally, check your servers for pending reboots, or reboot your servers manually. I use Server Manager to achieve this. Servers with a pending reboot will report their manageability as Online – Pending Reboot.

Using Server Manager to check for pending reboots

Using Server Manager to check for pending reboots

Installing a SCCM 2012 Cumulative Update ^

The SCCM Cumulative Update process has three major steps. First, you apply the update to the site server. Next, you install the updated console on administrative machines. Finally, you deploy the updated Configuration Manager client packages.

For safety, close the Configuration Manager console on any administrative machine. On your site server, launch the CU install and proceed through the wizard.

Server that is ready to install CU3 for SCCM 2012 R2

Server that is ready to install CU3 for SCCM 2012 R2

In most installs, you will accept all of the default options in a CU installation. To deploy the updated client/console, you will certainly want to update the site server’s console version. You will also want to update the site database during the CU installation.

The CU update will create new client and console packages for deployment. By default, these installs are stored in \\SITE-Server\SMS_SITECODE\hotfix\.

Creating packages for each update component in SCCM 2012.

Creating packages for each update component in SCCM 2012

In my environment, the install took about 15 minutes. If you have any issues, you can view the installation log in C:\Windows\Temp.

Site server that has been successfully updated to the current CU

Site server that has been successfully updated to the current CU

You will need to repeat this process for all site servers in your Configuration Manager hierarchy. Restart your site server(s) before proceeding to the next part of this guide. Once your server is back up, you can verify the installation by navigating to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Setup and checking the value of CULevel. For CU3, the value should be 3.

Updated server with a new version number

Updated server with a new version number

Updating the Configuration Manager console and clients ^

On your site server, launch the Configuration Manager console. Navigate to Software Library/Packages/Configuration Manager Updates. You should see four new packages: one for site servers, one for consoles, and two for clients.

R2 CU3 update packages

R2 CU3 update packages

Start by deploying the console update to any machine with the Configuration Manager console. You can use this query to create a collection that targets just those machines:

Be sure to edit the DisplayName line to reflect the console name used in your environment.

Successful deployment of the SCCM 2012 R2 CU3 console

Successful deployment of the SCCM 2012 R2 CU3 console

Finally, deploy the client packages to their correct architecture. If needed, you can use this query to create a collection for x64 clients or to modify it for x86 clients:

With your client updates being deployed, you have successfully updated your Configuration Manager infrastructure to the latest Cumulative Update! If you ran into any issues or have any other update tips, be sure to post a comment below.

Win the monthly 4sysops member prize for IT pros

Share
0

Related Posts

19 Comments
  1. dan 3 years ago

    Thank you for this article. I wish Microsoft would do such good "plain-english" instructions for their products. After following your steps outlined in this article, let's say I set up a new windows 7 client and want to install the SCCM client onto it for the first time ever. Do I just right-click "Install Client" in the SCCM console and does this install the CU3 SCCM client? Or does this install the old pre-CU3 SCCM client and then I have to upgrade it to CU3 using your method? That seems like a pain. How do you just make sure all new Win7 clients going forward just get the CU3 SCCM client first-time? Thanks.

    0

  2. Author
    Joseph Moody 3 years ago

    No problem Dan!

    That would not install the new updated client. I get the updated client on the machine during the imaging process. You can use this command:

    PATCH="C:\_SMSTaskSequence\OSD\WC10003B\Hotfix\x64\configmgr2012ac-r2-kb2994331-x64.msp"

    The WC10003B is the ID of your client package. Let me know if you still have questions.

    0

  3. RJ 3 years ago

    I did Cu3 update on sccm2012 r2 everything updated but perform database update step shows warning. How can I manually update database using update.sql file since site already shows updated with cu3. Please advise steps to perform on sql server 2012 management studio to update as I hv tried n it give plenty of errors.

    Thanks in advance

    Rj

    0

  4. Author
    Joseph Moody 3 years ago

    Look in C:\Windows\Temp for the log file for the update. Can you post the exact warning that you received?

    0

  5. RJ 3 years ago

    Hi Joseph, here are errors from log file...

    Starting task 'Perform Database Update'. Update Setup 07/11/2014 9:48:50 AM 3148 (0x0C4C)
    The timeout for each SQL operation is set to 90 seconds. Update Setup 07/11/2014 9:48:50 AM 3148 (0x0C4C)
    Connecting to database CM_RET Update Setup 07/11/2014 9:48:50 AM 3148 (0x0C4C)
    Successfully connected to SQL server version 11.00.3000 Update Setup 07/11/2014 9:48:50 AM 3148 (0x0C4C)
    SQLScriptExecution: Reading SQL script from 'D:\Program Files\Microsoft Configuration Manager\hotfix\KB2994331\update.sql'. Update Setup 07/11/2014 9:48:50 AM 3148 (0x0C4C)
    D:\Program Files\Microsoft Configuration Manager\hotfix\KB2994331\update.sql contains 47 commands, starting execution. Update Setup 07/11/2014 9:48:50 AM 3148 (0x0C4C)
    Executing SQL script ... Update Setup 07/11/2014 9:48:50 AM 3148 (0x0C4C)
    Running SQL operation 1 of 47... Update Setup 07/11/2014 9:48:50 AM 3148 (0x0C4C)
    Task status detail added: A SqlException occurred, Line Number: 159 Error: 229 Message: The EXECUTE permission was denied on the object 'fnIsPrimary', database 'CM_RET', schema 'dbo'. Update Setup 07/11/2014 9:48:50 AM 3148 (0x0C4C)

    Task 'Perform Database Update' completed, state is 'warning' LastStatus: A SqlException occurred, Line Number: 159 Error: 229 Message: The EXECUTE permission was denied on the object 'fnIsPrimary', database 'CM_db', schema 'dbo'.

    Update Setup 07/11/2014 9:48:51 AM 2588 (0x0A1C)

    Task 'Perform Database Update' completed, state is 'warning' LastStatus: A SqlException occurred, Line Number: 159 Error: 229 Message: The EXECUTE permission was denied on the object 'fnIsPrimary', database 'CM_db', schema 'dbo'.

    Microsoft SQL Server 2012

    0

  6. Author
    Joseph Moody 3 years ago

    First - make sure the account you are using has the sysadmin role for the sql server.

    Second- run the SQL server update from Program Files\Microsoft Configuration Manager\hotfix\KBOFCU\update.sql

    1+

  7. Pavel 3 years ago

    Hey guys!
    I installed a clear SCCM R2 on my server, then i installed CU3 but still have a problem with slow downloads during OSD TS (boot image downloads quickly, but windows image downloads very slow) Can you explain what to do – also install a 2905002 hotfix? If yes, is there necessity to patch client package with this hotfix? I thought that CU3 includes all past fixes.

    0

  8. Author
    Joseph Moody 3 years ago

    CU3 will include all past fixes. First, did have an earlier version of SCCM running with OSD configured? If so - about how fast did OSD take place? Are you currently multicasting or unicasting?

    0

  9. M. Fricke 3 years ago

    To resolve slow downloads during TS remember to rebuild (update distribution points) the boot Image.
    Also be sure that you integrate the Client patch .msp in the deployment.
    This is done by adding installationproperties of "Setup Windows and confguration Manager", add something like this:

    PATCH="%OSPARTITION%\_SMSTaskSequence\OSD\CAS00194\Hotfix\configmgr2012ac-r2-kb2970177-i386.msp"

    Be sure you added the .msp to you Client package and verify packagename and path.

    1+

  10. Jane D. 3 years ago

    We successfully upgraded to the 2012 r2 CU3 update, but for some reason, the Client Push Install feature isn't working. It pulls the correct files for the CCMSetup.exe to the c:\windows\ccmsetup folder, but it still installs the old version 5.0.7958.1000 vs the new version 5.0.7958.1401....

    Also, on the automatic client upgrade feature it shows the incorrect version. The Site Server is sitting with 5.0.7958.1000 (old version) and wont upgraded.

    0

  11. Author
    Joseph Moody 3 years ago

    From my understanding, the automatically upgrade client push settings will only upgrade between major versions - not CUs. You will need to deploy the CU client update separately.

    0

  12. Jane D. 3 years ago

    Gotcha. For OSD (To create the patch for new deployments) I don't see anything in my _SMSTaskSequence folder on my PXE server. How do I get the patch file from "c$\Program Files\Microsoft Configuration Manager\hotfix\KB2994331\Client\x64" so that it can be used in my OSD Task Sequence?
    ---
    Also, sorry to be a bug, but I have noticed that a few of our DPs have not finished the autoupgrade process. They don't show error under monitoring > distribution status > dp config status... Is there a way that I can manually get this process started so that they can be upgraded? Or log files that I can review to see what the error was/is so that it can be remedied? We have quite a few DPs, so im not sure if this log would have been truncated by now or not.

    Thank you.

    0

  13. Author
    Joseph Moody 3 years ago

    You will want to copy the hotfixes into the config mgr client folder. Then create a new package and use that folder as the source.

    In your task sequence, add the following installation property to the Setup Windows and Configmgr task:

    PATCH="C:\_SMSTaskSequence\OSD\WC10003B\Hotfix\x64\configmgr2012ac-r2-kb2994331-x64.msp"

    0

  14. Lon 3 years ago

    Thank you SO much for plain a simple details on exactly what all needs to be done!
    However, I have a question about the x64 and x86 boot images. Do I need to do anything to update those, or does this CU (actually, I used your guild to install CU 5) take care of that?
    I am unsure how I would check to see, or how to manually update the versions if needed.

    Thanks!
    -=Lon=-

    0

  15. M. Fricke 3 years ago

    Rebuilding (updating) the boot Images is done by choosing "Update Distribution Point" on every boot Image..

    0

  16. Lon 3 years ago

    Thanks M. Fricke!

    -=Lon=-

    0

  17. Joel Thibeault 2 years ago

    Great article once again Joseph. Clearly explanation of the whole picture not just pieces of updates.

    0

  18. Author
    Joseph Moody 2 years ago

    Thank you Joel! 🙂

    0

Leave a reply

Your email address will not be published. Required fields are marked *

*

CONTACT US

Please ask IT administration questions in the forum. Any other messages are welcome.

Sending
© 4sysops 2006 - 2017

Log in with your credentials

or    

Forgot your details?

Create Account