Tuesday, June 30, 2015

Include ConfigMgr Client Cumulative Update during OSD

During deployment in ConfigMgr, you can install the ConfigMgr Client Cumulative Update immediately. There are multiple posts found where the PATCH= parameter is used. The Cumulative Update needs to be in a package or reference image (included for installation) for this. I see lots of times the PATCH= parameter is skipped, for different reasons. Let's have a look at another way to install the Cumulative Update. This one is not hard at all. It just works :-)

Just create ClientPatch folders in both ConfigMgr Client locations:
-Program Files\Microsoft Configuration Manager\Client\x64
-Program Files\Microsoft Configuration Manager\Client\i386
and copy the appropriate architecture (x64 and/or i386) from your hotfix to one of this folders. Do not forget to update your ConfigMgr Client Package to be sure using the Files with the Hotfixes.

That's it! No PATCH= parameter needed at all. It did work on my first try (CU4), so very easy to use if you ask me :-)

When using Client Push Installation it will be helpfull either. No need to apply the CU client update afterwards. It will be detected automatically:
-Detected 1 client patch files. Will apply them after client installation.
-Adding file 'configmgr2012ac-r2-kb3026739-x64.msp' to BITS job, saving as 'C:\Windows\ccmsetup\configmgr2012ac-r2-kb3026739-x64.msp'.
-C:\Windows\ccmsetup\configmgr2012ac-r2-kb3026739-x64.msp is Microsoft trusted.
-File C:\Windows\ccmsetup\configmgr2012ac-r2-kb3026739-x64.msp installation succeeded.
-Params to send FSP message '5.0.7958.1501 Deployment [DP]

Why this is a hidden/undocumented feature suprised me.
Can't be easier if you ask me :-)

Source: SCCMfaq.ch
Source: Systems Management and Automation

Update 6-7:
@jarwidmark - That method works for some, breaks for some, but either way, it is totally unsupported by Microsoft.
@rsjulsen - This method has totally worked for me :) But ofc.. Totally unsupported.. and totally, totally awsome :)

Update 24-8:
With Cumulative Update 1 for ConfigMgr 2012 R2 SP1 and 2012 SP2 this isn't needed anymore. Source: Automatically updating the Configuration Manager client


  1. That's totally unsupported and *will* cause issues! I don't recommend using that method even it might look easy.

  2. I tried creating the ClientPatch folder with CU1 for SCCM 2012 R2 SP1; the SCCM 2012 R2 clients only got upgraded to SP1 (5.00.8239.1000) I read elsewhere that the folder should now be called "ClientUpdate" - bit still didn't work for me.

    1. With ConfigMgr 2012 R2 SP1 this isn't needed anymore. CU1 can be upgraded with Automatic Client Upgrade as well. Don't use the ClientPatch folder for this.