{"id":1448,"date":"2014-03-14T00:00:09","date_gmt":"2014-03-13T23:00:09","guid":{"rendered":"http:\/\/sccmfaq.wordpress.com\/?p=1448"},"modified":"2014-03-14T00:00:09","modified_gmt":"2014-03-13T23:00:09","slug":"sccm-2012-r2-include-client-hotfix-or-cumulative-update-while-on-osd","status":"publish","type":"post","link":"https:\/\/blog.hosebei.ch\/?p=1448","title":{"rendered":"SCCM 2012 R2 &#8211; Include Client Hotfix or Cumulative Update while on OSD"},"content":{"rendered":"<p>Refer to this Blog <a href=\"http:\/\/blog.hosebei.ch\/2013\/09\/24\/sccm-2012-include-cu-in-osd\/\" title=\"(Link)\" target=\"_blank\">post<\/a>, I decided to create a new one about including Hotfixes in OSD. Specially the new Release of SCCM 2012 R2 brings an annoying issue with extremly slow Downloads while on OSD (http:\/\/support.microsoft.com\/kb\/2910552 ; this Hotfix superseding the <a href=\"http:\/\/support.microsoft.com\/kb\/2905002\" title=\"KB2905002\" target=\"_blank\">KB2905002<\/a> which was first used in this blog).<\/p>\n<p>There are two nice ways, how to apply Hotfixes like this to the Client while on OSD, one is documented and thus supported, the other one does just work \ud83d\ude42<!--more--><br \/>\nThe one that works, but neither documented or supported, is quite simple and already explained in this blogpost (http:\/\/www.m4ttmcg.com\/2013\/05\/sccm-2012-client-push-including.html). Just create the folders:<br \/>\n<code>C:\\Program Files\\Microsoft Configuration Manager\\Client\\x64\\ClientPatch<br \/>\nC:\\Program Files\\Microsoft Configuration Manager\\Client\\i386\\ClientPatch<\/code><br \/>\nand copy the appropriate architecture from your hotfix to one of this Folder. Do not Forget to update your Client Package to be sure using the Files with the Hotfixes.<\/p>\n<p>The other way is to create a package, and copy the files with a package to the Client. First. create a package Location for the hotfix files and create two Folders named AMD64 and X86:<br \/>\n<a href=\"http:\/\/hosebei.wordpress.com\/wp-content\/uploads\/2014\/03\/osd_cu01.png\"><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/hosebei.wordpress.com\/wp-content\/uploads\/2014\/03\/osd_cu01.png?w=300\" alt=\"Create Package location\" width=\"300\" height=\"62\" class=\"aligncenter size-medium wp-image-1451\" srcset=\"https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2014\/03\/osd_cu01.png 823w, https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2014\/03\/osd_cu01-300x62.png 300w, https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2014\/03\/osd_cu01-768x160.png 768w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/a><\/p>\n<p>Now navigate to the hotfix Folder and open the Client Folder:<br \/>\n<code>C:\\Program Files\\Microsoft Configuration Manager\\hotfix\\KB2910552\\Client<\/code><br \/>\nCopy the appropriate architecture to the Package Folder, mind to delete the architecture from the file Name:<br \/>\n<code>\"\\\\servershare\\Deployment\\Packages\\Microsoft\\SCCM Client\\2012 R2\\CU0\\AMD64\\configmgr2012ac-r2-kb2910552.msp\"<br \/>\n\"\\\\servershare\\Deployment\\Packages\\Microsoft\\SCCM Client\\2012 R2\\CU0\\X86\\configmgr2012ac-r2-kb2910552.msp\"<\/code><br \/>\nAs example, the x64 Folder:<br \/>\n<a href=\"http:\/\/hosebei.wordpress.com\/wp-content\/uploads\/2014\/03\/osd_cu02.png\"><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/hosebei.wordpress.com\/wp-content\/uploads\/2014\/03\/osd_cu02.png?w=300\" alt=\"Patch package\" width=\"300\" height=\"91\" class=\"aligncenter size-medium wp-image-1454\" srcset=\"https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2014\/03\/osd_cu02.png 780w, https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2014\/03\/osd_cu02-300x92.png 300w, https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2014\/03\/osd_cu02-768x234.png 768w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/a><\/p>\n<p>Now it is time to create the package, well, it\u2019s that easy with this powershell command:<br \/>\n<code>New-CMPackage -Name \"SCCM Client 2012 R2 CU0\" -Language \"MUI\" -Manufacturer \"Microsoft\" -Path \"$PATH_TO_YOUR_PACKAGE\" -Version \"2012 R2 CU0\"<\/code><br \/>\nAnd we don\u2019t need to create a program, because we only use this package within our Task Sequence, but don&#8217;t forget Distribute the Package to your Distribution Points.<\/p>\n<p>Make sure, that you set a Variable when formatting your System Drive, on BIOS an UEFI:<br \/>\n<a href=\"http:\/\/hosebei.wordpress.com\/wp-content\/uploads\/2013\/09\/integrate_cu04.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-medium wp-image-915\" alt=\"Set Disk Variable\" src=\"http:\/\/hosebei.wordpress.com\/wp-content\/uploads\/2013\/09\/integrate_cu04.png?w=300\" width=\"300\" height=\"215\" srcset=\"https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2013\/09\/integrate_cu04.png 897w, https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2013\/09\/integrate_cu04-300x215.png 300w, https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2013\/09\/integrate_cu04-768x551.png 768w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/a>Then use this variable also to deploy Windows on the correct Drive:&nbsp;<a href=\"http:\/\/hosebei.wordpress.com\/wp-content\/uploads\/2013\/09\/integrate_cu05.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-medium wp-image-916\" alt=\"Apply Operating System\" src=\"http:\/\/hosebei.wordpress.com\/wp-content\/uploads\/2013\/09\/integrate_cu05.png?w=300\" width=\"300\" height=\"73\" srcset=\"https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2013\/09\/integrate_cu05.png 443w, https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2013\/09\/integrate_cu05-300x74.png 300w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/a><br \/>\nNow create a simple &#8220;Run Command Line&#8221; step in your Task Sequence, right before the step &#8220;Setup Windows and Configuration Manager&#8221; where you copy the file to a Folder on the System Drive. This Folder and the Content will remain after the Installation, so you have to delete them with another step, or leave it in the temp Directory. Here is my step:<br \/>\n<code>cmd.exe \/c xcopy %PROCESSOR_ARCHITECTURE%*.* %OSD_System%windows\\temp\\SCCMHotfix \/E \/H \/C \/I \/Q \/Y<\/code><br \/>\n<a href=\"http:\/\/hosebei.wordpress.com\/wp-content\/uploads\/2014\/03\/osd_cu03.png\"><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/hosebei.wordpress.com\/wp-content\/uploads\/2014\/03\/osd_cu03.png?w=300\" alt=\"OSD TS Step 01\" width=\"300\" height=\"271\" class=\"aligncenter size-medium wp-image-1456\" srcset=\"https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2014\/03\/osd_cu03.png 711w, https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2014\/03\/osd_cu03-300x271.png 300w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/a><\/p>\n<p>Now, the last step, add the Patch to the SCCM Agent Installation, this is my Installation properties::<br \/>\n<code>SMSCACHEFLAGS=PERCENTDISKSPACE;NTFSONLY SMSCACHESIZE=10 SMSMP=$FQDN_MP FSP=$FQDN_FSP PATCH=C:\\windows\\temp\\SCCMHotfix\\configmgr2012ac-r2-kb2910552.msp<\/code><br \/>\n<a href=\"http:\/\/hosebei.wordpress.com\/wp-content\/uploads\/2014\/03\/osd_cu04.png\"><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/hosebei.wordpress.com\/wp-content\/uploads\/2014\/03\/osd_cu04.png?w=300\" alt=\"Installation properties\" width=\"300\" height=\"269\" class=\"aligncenter size-medium wp-image-1458\" srcset=\"https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2014\/03\/osd_cu04.png 711w, https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2014\/03\/osd_cu04-300x270.png 300w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/a><\/p>\n<p>If this is not working, you named the subdirectories wrong in your package, or you forgot to remove the architecture from the files.<br \/>\nHope this helps, Martin<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Refer to this Blog post, I decided to create a new one about including Hotfixes in OSD. Specially the new Release of SCCM 2012 R2 brings an annoying issue with extremly slow Downloads while on OSD (http:\/\/support.microsoft.com\/kb\/2910552 ; this Hotfix superseding the KB2905002 which was first used in this blog). There are two nice ways, [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11,27,35],"tags":[],"class_list":["post-1448","post","type-post","status-publish","format-standard","hentry","category-client-agent","category-operating-system-deployment","category-sccm-2012"],"_links":{"self":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts\/1448","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1448"}],"version-history":[{"count":0,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts\/1448\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1448"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1448"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1448"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}