Update Configuration Manager 2012 SP1 client with Cumulative Update 3


Hi all,

Today I’m going to talk about the Cumulative Update 3 of Configuration Manager 2012 SP1 and how to install the updated client to all Configuration Manager Clients. As you all might know this CU3 fixes some issues with Configuration Manager. For a detailed list, I recommend you to read the following Microsoft documentation: http://support.microsoft.com/kb/2882125/en-us

First of all the CU3 should be installed on the primary site server.

The installation generates a couple of packages that should be appropriately deployed:

-          Package to update the console
–          Package to update the server
–          Package to update clients (x86)
–          Package to update clients (x64)

The focus today is on  the client update and how to get it installed throughout the environment.

02102013_1

We first have to look at the different deployment scenario’s:

-          Upgrade existing Configuration Manager Client (example for x86 clients)

1. Create a collection called All x86 Systems with client using the following query:

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_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_G_System_COMPUTER_SYSTEM.SystemType = “x86-based PC”

This collection has a limiting collection called “All Systems with Client”, this collection was created previously

2. Deploy the x86 client update to the “All x86 Systems with Client” collection using a required deployment

The same can be done for x64 clients

-          Integrating CU3 client with Operating System Deployment

In previous versions of SCCM when a cumulative update was installed, the update was added to the client installation source. Which means that the original client package only needed an update distribution points to include the update + add an additional parameter to the Setup Windows & Configmgr step in the task sequence.

Now the update is stored elsewhere, so a new client package should be created which contains the original client installation source and the cumulative update (.msp file)

1. Create an empty folder in your datastore where packages, applications, etc. are stored (eg. \\[fileserver]\DSL\Microsoft\SCCM_Client\2012_CU3\ML\MSI)

2. Copy the content from the installation folder of SCCM (eg. D:\Program Files\Microsoft Configuration Manager\Client into the new folder

02102013_2
3. Create an extra folder. Eg. Patches

02102013_3
4. Copy the contents of the folder where the update was installed (eg. D:\Program Files\Microsoft Configuration Manager\hotfix\KB2882125\Client) into the Patches folder

02102013_4
5. Create a package in Configuration Manager with the newly created folder as source (\\[fileserver]\DSL\Microsoft\SCCM_Client\2012_CU3\ML\MSI), No need to create a program for this package.

02102013_7
6. Copy the package to the distribution points available within your environment

7. Edit the task sequence where you want to apply the updated version of the Configuration Manager Client. Edit the existing “Setup Windows & Configuration Manager “ step and point it to the newly created package

02102013_5
8 Fill in the following command line at the installation properties field:

PATCH=”%_SMSTSMDataPath%\OSD\[PKGID]\Patches\i386\configmgr2012ac-sp1-kb2882125-i386.msp”

02102013_6

This is for the x86 client Operating Systems being deployed, for the x64 operating systems this is the right command line:

PATCH=”%_SMSTSMDataPath%\OSD\[PKGID]\Patches\x64configmgr2012ac-sp1-kb2882125-x64.msp”

From now on clients being deployed with the edited task sequence will receive the latest version of the Configuration Manager Client

For future updates, the same way of working can be used.

Hope this helps!

Cheers,

B

About these ads

9 Responses to Update Configuration Manager 2012 SP1 client with Cumulative Update 3

  1. Adam says:

    Thank you for this! This is very helpful as I’m preparing for our CU3 update.

    You mentioned that in previous versions of SCCM when a cumulative update was installed, the update was added to the client installation source. So the original client package only needed an update distribution points to include the update + add an additional parameter to the Setup Windows & Configmgr step in the task sequence. You mentioned that now the update is stored elsewhere, so a new client package should be created which contains the original client installation source and the cumulative update (.msp file). In your steps above, you created a new directory, copied the contents of the original installation folder, added the patches folder, and created a brand new package. Just curious why you chose this route vs. adding the patches folder to the original installation location and update the original client package.

    Thanks again!

    • Bert Pinoy says:

      Adam,

      It’s nothing more then a personal preference :). I prefer creating new packages over messing around with existing one especially for applying updates. Mostly because I want to test my packages before I use them in any task sequence. But if you prefer updating the existing client package, that will also work fine. Keep in mind that you have to make the difference between applying the client to x86 and x64 systems.

      Regards,

      B

      • Adam says:

        Makes sense. Thanks again for the detailed article and kudos to you and the other site staff on a great SCCM resource for admins like myself :) Great job.

  2. Ricky Isbell says:

    I have tried copying and pasting the query to create the collection for the different clients and I am getting a syntax error every time. Is something missing?

    • Bert Pinoy says:

      Ricky,

      Have you tried replacing the double qoutes(“) in the query you have pasted? (just delete and retype them)
      It seems that copy / paste ‘breaks’ the double quotes. This is causing the syntax error.

      Kind Regards,

      Bert

  3. Paul says:

    Hi B,

    What can we do for client push installations started from SCCM Console?

    I would have thought that, after deploying SCCM SP1 CU3, any new clients that have SCCM client “pushed” to them would have the CU3 version.

    It seems that is not the case and the original SP1 client is pushed instead. Do you know any different as I might be missing something!

    Cheers,

    Paul

  4. Al says:

    Hi B,

    A easy way to use the the Variable %Processor_Architecture% instead of using x86 or x64 can be found here:

    http://sccmfaq.wordpress.com/2013/09/24/sccm-2012-include-cu-in-osd/

    Cheers
    Al

  5. Walid AlMoselhy says:

    Hi B,
    This is an unrelated question, but how do you manage the comment, I have my own wordpress blog (www.almoselhy.com) and I get tons of spam comments everyday that it’s becoming too hard to find real comments, is there a plugin or something that you would recommend.

    • Bert Pinoy says:

      Hi,

      We also get alot of spam comments. I don’t know of a plugin that can be used to “filter” comments.
      I’m sorry. We manually process all comments to approve them, it’s some work but that is the only way to go I think.

      Kind regards,
      Bert

Leave a Reply

Fill in your details below or click an icon to log in:

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

Get every new post delivered to your Inbox.

Join 671 other followers