SCCM 2012 Client Push – Including hotfixes / CU patches in Client Push

By | May 29, 2013

There are lots of methods for including hotfixes in your SCCM client deployment.

One neat trick that worked (although not officially supported) was to add the MSP patch files to a “ClientPatch” subfolder of the Client folder.

The CCMSETUP msi installer looks for this folder, and applies any patches in alphabetical order.

Inspecting the CCMsetup log, you will find the following line

PROPFIND 'http://PRI.domain.local/SMS_DP_SMSPKG$/PRI00002' ccmsetup 30/05/2013 11:11:52 PM 2676 (0x0A74)
No client patches are detected. ccmsetup 30/05/2013 11:11:52 PM 2676 (0x0A74)
PROPFIND 'http://PRI.domain.local/SMS_DP_SMSPKG$/PRI00002' ccmsetup 30/05/2013 11:11:52 PM 2676 (0x0A74)

In SCCM 2012, this trick still works, although you need to place the ClientPatch folder in each architecture folder of the Client folder

So, create a ClientPatch folder inside each of the x64 and i386 folders of the Client folder on your site server.

Next, copy the MSP patch files to the respective folders (for my testing I used the CU1 update files)

You will need to update all distribution points with the new client package.

Verify the client package update has distributed. Now perform a client push installation. No need to add any PATCH=xxx command line parameters to the client push command line, and if you already have them, remove them for this test.

Inspect the ccmsetup log file. You should see that the client patch detection has found your patch.

Notice that the patch is not installed as a property addition to the actual client msi. It is installed at the end.

One of the very last lines in the log will be

(this is the CU1 msp file)

Checking the client properties after installation, and the version number is indeed correct for CU1.

This works for OSD as well as client push installs. No need to alter your OSD Task sequences when there are client patches.

Please be aware that this was not supported in SCCM 2007, due to complications with some command line parameters of CCMSETUP.exe and the patches applying. (See

I’m not sure if its supported in SCCM 2012 either, but the mechanism still exists, and I have not found issues in my testing.


Leave a Reply

Your email address will not be published. Required fields are marked *