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:
2) Copy the files from the hotfix/cu into a subfolder, I just named it “Patch”:
3) Create the package in SCCM:
Define Settings of the package:
Do not create a program:
Finish 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:
And 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.
blog.hosebei.ch 
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
You can add 2 Steps of Install Windows and ConfigMgr Client. Chose the right one depending on a WMI query or any other option.
See our new blog about this topc:
http://sccmfaq.wordpress.com/2013/09/24/sccm-2012-include-cu-in-osd/
Why not just use PATCH=”.Patchx64configmgr2012ac-sp1-kb2817245-x64.msp” seems like that ought to work.
I never tried this before. I older versions you have had to commit a Full Path, without a full path, it wouldn’t work. I test this now and will update the post if successfull.
/Edit: When I use this string, the client installation will fail. Could you provide a link, where i can see that this is supported and itz works?
See our new blog about this topc:
http://sccmfaq.wordpress.com/2013/09/24/sccm-2012-include-cu-in-osd/
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?
I found the information if multiple patches must be installed during OSD:
PATCH=”%_SMSTSMDataPath%OSDPatchx64Patch01.MSP”;”%_SMSTSMDataPath%OSDPatchx64Patch02.MSP”;”%_SMSTSMDataPath%OSDPatchx64Patch03.MSP”
That’s true, this will work. I used this in SCCM 2007 aswell.
See our new blog about this topc:
http://sccmfaq.wordpress.com/2013/09/24/sccm-2012-include-cu-in-osd/
[…] methods like to leverage the %_SMSTSMDataPath% variable as seen here. The issue I’ve had with this method is that while the value for %_SMSTSMDataPath% stays […]
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?
I use this package only for OSD, and there is no Programm needed.
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.