Microsoft has now released the Cumulative Update 2 for System Center 2012 Configuration Manager SP1. If you havn’t install the update yet, follow my installation guide which you can find here: http://www.scconfigmgr.com/2013/06/25/install-configmgr-2012-sp1-cu2-in-your-hierarchy/

Once you’ve installed the CU2, it’s time to deploy the update to your ConfigMgr 2012 SP1 clients. This blog post will cover the steps needed. I assume that you’ve followed the instructions above, or atleast have the packages created from the installation wizard.

Overview

  • Install the CU2
  • Locate the CU2 Client upgrade packages
  • Distribute the packages to your DP’s
  • Create a collection with ConfigMgr 2012 SP1 clients for targeting the deployment
  • Deploy the CU2 to your ConfigMgr 2012 SP1 clients

Install the CU2

As mentioned previously, please refer to this blog post: http://www.scconfigmgr.com/2013/06/25/install-configmgr-2012-sp1-cu2-in-your-hierarchy/

Locate the CU2 Client upgrade packages

1. Open your Configuration Manager console and navigate to Software Library.
2. Expand Application ManagementPackages and Configuration Manager Updates.
3. If the installation wizard of CU2 was successfull, you should see two packages for Client upgrade. They are called:

  • SP1 Cumulative update 2 – x64 client update – <site_code>
  • SP1 Cumulative update 2 – x86 client update – <site_code>

39_1

Distribute the packages to your DP’s

1. Select package SP1 Cumulative update 2 – x64 client update – P01, right-click and choose Distribute Content. Click Next.
2. Click Add and choose your preferred method of distributing the packages. I’m using a Distribution Point Group.
3. Click Next and Next again. When the wizard is finished, click Close.
4. Repeat the step 1-3 for the SP1 Cumulative update 2 – x86 client update – P01 package.

Create a collection with ConfigMgr 2012 SP1 clients for targeting the deployment

1. Navigate to Assets and Compliance.
2. Select Device Collections, right-click and choose Create Device Collection.
3. In the Name field, type Systems with ConfigMgr 2012 SP1 Clients and choose All Systems as the Limiting collection. Click Next.

39_2

4. In the Membership Rules page, click Add Rule and choose Query Rule.
5. In the Name field, type Systems with ConfigMgr 2012 SP1 Clients.

39_3

6. Click on Edit Query Statement.
7. Select the Criteria tab and click the yellow star.

39_4

8. Click on Select.
9. In the Attribute class drop down menu, choose System Resource.
10. In the Attribute drop down menu, choose Client Version. Click on OK.

39_5

11. Click on Value and choose 5.00.7804.1000. Click OK.

39_6

12. Click on OK until you get back to the Create Device Collection Wizard.
13. Change the schedule the collection membership will be updated on, so that it fits your environment. Click Next.
14. Click Next and Close when the wizard is completed.

NOTE! If you’ve already deployed the Cumulative Update 1, create a collection for those clients as well. The attribute for the Client Version should be 5.0.7804.1202 instead. It’s always a good idea to make sure you don’t miss any clients.

Deploy the CU2 to your ConfigMgr 2012 SP1 clients

1. Navigate to Software LibraryApplication ManagementPackages and Configuration Manager Updates.
2. Select the SP1 Cumulative update 2 – x64 client update – P01 package. Right click and choose Deploy.
3. Click Browse next to the Collection field.
4. Locate and select the Systems with ConfigMgr 2012 SP1 Clients collection. Click OK.
5. Click Next and Next again.
6. Leave the default settings on the Deployment Settings page. Click Next.

39_7

7. On the Scheduling page, click New.
8. Determine when you’d like to deploy this package to your clients. In this blog post, we’ll be deploying it by choosing Assign immediately after this eventAs soon as possible. But if you’d like to schedule the deployment according to your maintenance windows, choose Assign to the following schedule and configure the schedule by clicking on Schedule. Click OK.
9. Leave the rest of the settings on the Scheduling page by their defaults. Click Next.

39_8

10. On the User Experience page, configure what’s gonna be allowed when the assignment schedule time is reached. For the purpose of demonstration and since the environment is using maintenance windows, we’ll be selecting Software installation. Click Next.

39_9

11. Leave the defaults on the Distribution Points page, click Next.
12. Click Next on the Summary page.
13. Click Close.
14. If you’ve x86 clients in your environment, repeat steap 1-13 for the SP1 Cumulative update 2 – x86 client update – P01 package.

Check client version

1. Log on to a client.
2. Open Control Panel, click on System and Security and then Configuration Manager.
3. On the General tab under Client Properties, you’ll see which version the local client is running.

ConfigMgr 2012 SP1 – 5.00.7804.1000
ConfigMgr 2012 SP1 CU1 – 5.00.7804.1202
ConfigMgr 2012 SP1 CU2 – 5.00.7804.1300

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.

(119)

comments
  • egarcia
    Posted at 17:56 July 9, 2013
    egarcia
    Reply
    Author

    Very good article, thanks!
    What components of the client are updated? Mostly I see 4 components. I’ve see when all of the components are updated to 5.00.7804.1300. Thanks.

    • Nickolaj
      Posted at 15:52 July 10, 2013
      Nickolaj
      Reply
      Author

      Hi Egarcia,

      The components that gets upgraded on my clients are these:

      CCM Framework
      Operating System Deployment Components
      Software Updates
      Task Sequence Components

      That’s from a client that was running 5.00.7804.1000 prior to the upgrade.

      Regards,
      Nickolaj

  • Steve
    Posted at 23:31 July 16, 2013
    Steve
    Reply
    Author

    Nice article. Very helpful. One question… we are going to be going to SP1 and wanted to go to CU2 at the same time. Can I use the auto-client update feature after the SP1/CU2 installation to get the clients to the CU2 version or can I only use the auto-update to get to SP1 client version and then have to circle back and deploy the CU2 client package?

    So we’d be going from RTM client to SP1/CU2 and skipping the SP1 client version. Make sense?

    Thanks!

    • Nickolaj
      Posted at 00:42 July 17, 2013
      Nickolaj
      Reply
      Author

      Hi Steve,

      I’d go to SP1 first and then upgrade all the clients to the same version. I’d then think about upgrading the hierarchy to CU2. Why I’d go to SP1 first is explained here:

      http://configmgrblog.com/2012/12/03/how-to-update-configmgr-clients-automatically-in-sp1/

      Apparently the Automatic Client Upgrade feature did not work completely in the RTM version. Since I never tried it in RTM, I can’t be sure if the RTM clients will work.

      So the work flow would be:

      1. Upgrade your hierarchy to SP1.
      2. Upgrade your clients to SP1 (distributing the new Client Package created by the SP1 upgrade installation).
      3. Upgrade your hierarchy to CU2.
      4. Upgrade your clients to CU2 (either by following this guide or by enabling Automatic Client Upgrade).

      Before you upgrade to CU2, I’d read this KB article and determine if it applies to your environment:

      http://support.microsoft.com/kb/2867422

      I hope it all makes sense, otherwise let me know!

      /Nickolaj

  • Steve
    Posted at 17:41 July 17, 2013
    Steve
    Reply
    Author

    Thanks for the feedback.

    So it sounds like we can achieve the client upgrade to SP1/CU2 version with one automatic deployment.

    We are doing SP1 and CU2 installs at the same time.

    My concern is having to do an automatic client upgrade to get to SP1 client version and then another seperate client upgrade deployment to get to SP1/CU2 version.

    Thanks,
    Steve

  • Steve
    Posted at 16:54 July 19, 2013
    Steve
    Reply
    Author

    So I tested this in my lab and the CU2 update needs to be deployed seperately. The Auto-Update feature doesn’t recognize the CU2 client update (5.00.7804.1300).

    Thanks!

    • Nickolaj
      Posted at 17:04 July 19, 2013
      Nickolaj
      Reply
      Author

      That’s strange that it didn’t pick it up. Will have to look into that just for the fun of it.

      Good luck with the upgrade!

      /Nickolaj

      • Steve
        Posted at 03:16 August 14, 2013
        Steve
        Reply
        Author

        Hey, wanted to circle back after doing some more digging. Turns out I was able to get the SP1/CU2 client installed in one fell swoop after all.

        1.) I created a copy of the SCCM SP2 Client Upgrade Package that was created dring SP1 installation – just to leave it intact (and because I was testing).

        2.) Copied the SP/CU2 client MSP to a DFS share.

        3.) In my newly created package, set the command line as: ccmsetup.exe /noservice PATCH:”\\UNC_PATH_TO_CU2_PATCH\SHARE\Patch.msp”

        Simply deploy this and the clients are upgraded and patched to 5.00.7804.1300 (SP1/CU2) in one deployment.

        I am still having issues getting CM to not report the installation as “Failed” due to ccmexec being bounced mid-stream, but I may just live with it and use the collections to take care of that aspect.

        It was actually quite easy, I think I was just trying to make it harder than it should have been. 🙂

        Anyway, hope this may help someone and thanks again for the writeups.

        Regards,
        Steve

        • Nickolaj
          Posted at 12:34 August 16, 2013
          Nickolaj
          Reply
          Author

          Hi Steve,

          I’m glad that you got it working! I’m sure this will help someone, thanks for sharing it.

          Regards,
          Nickolaj

        • Russel
          Posted at 20:10 August 26, 2013
          Russel
          Reply
          Author

          Steve –

          “I am still having issues getting CM to not report the installation as “Failed” due to ccmexec being bounced mid-stream, but I may just live with it and use the collections to take care of that aspect.”

          I haven’t tried this in CM2012, but in 2007 the issue with the deployment being reported as failed can be addressed by configuring your program’s restart settings. On the program’s properties page, on the General tab, there is a drop-down titled “After Running.” Set this to “Program controls restart.” In 2007, this addressed the issue, but as I’ve said, I haven’t tried it in 2012.

          Best regards,

          –Russel

  • Leave a Reply