SCCM 2012 SP1 – Include Client CU1 in OSD

Please refer to our new Blog Post about including Cumulative Updates:

https://blog.hosebei.ch/2013/09/24/sccm-2012-include-cu-in-osd/


In this post, I would like to show, how to integrate the Client hotfix cumulative update 1 in the operating System deployment Task sequence. First, CU1 is released and it will create update packages for Site Server, console and client (x64 & x86) installations when you apply this cumulative update to your System Center 2012 Configuration Manager SP1 Environment.

In SCCM 2007 an hotfix usually copied the patchfiles inside the existing Client Installation package Directory (<sccm install Directory>Client). This no longer happens with SCCM 2012, so you can modify the built-in package, or create an newone. I decided to create a new SCCM Client package, here is what i’ve done:
1) Take all files from <sccm install Directory>Client and copy it to your package:
create package2) Copy the files from the hotfix/cu into a subfolder, I just named it “Patch”:

insert patch3) Create the package in SCCM:

add packageDefine Settings of the package:
define settingsDo not create a program:
create no programFinish the wizard, and do not forget to distribute the package Content on a Distribution Point!

4) Use the new package in your Task sequence
Click on browse, and chose your newly created SCCM Client Package:
modify task sequenceAnd add the PATCH property to your Installation properties. I’am using the following command:
PATCH="%_SMSTSMDataPath%OSD<YOUR PACKAGE ID>Patchx64configmgr2012ac-sp1-kb2817245-x64.msp"
In earlier Versions, Microsoft does not recommend using the “%_SMSTSMDataPath% variable (http://support.microsoft.com/kb/977384/en-us), but I never experienced a Problem with that.

15 thoughts on “SCCM 2012 SP1 – Include Client CU1 in OSD

  1. Hi

    a qucik question. We have a couple of 32-Bit systems WXP,W7. We still have to install the new clients on both platforms. The solutions flying around but are all platform dependent. Is there a cance to build a platform independent solution, so the installtion is pulling the right patch x86,x64 for the right paltform during the installation or do I have to create two different packages?

    Thanks in advance

  2. We have the situation, that we need first to install CU2 and after that another hotfix. Can I just add another PATCH=”%_SMSTSMDataPath%OSD\Patchx64xxx.MSP” with a space?

  3. I found the information if multiple patches must be installed during OSD:
    PATCH=”%_SMSTSMDataPath%OSDPatchx64Patch01.MSP”;”%_SMSTSMDataPath%OSDPatchx64Patch02.MSP”;”%_SMSTSMDataPath%OSDPatchx64Patch03.MSP”

  4. Why wouldn’t you use a program in this instance? I tried it the way you laid out but the client has no site code assigned. And since you can’t set the SMSSITECODE in the installation properties in the task sequence, where else are you supposed to do it?

  5. That’s where I’m using it, and when I do the client has no configured site code. I can’t figure out how to make that happen. Any suggestions?

    • No sorry, can not Image why it’s not working. But you definately not Need a program when using this package on OSD.
      I would suggest you to ask your question in the TechNet Forum or similar.

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