Freigeben über

Patch ConfigMgr 2012 x86 and x64 clients during a task sequence using the PATCH property

  • Artikel

In this post, I'm go to show a method to patch the client during a task sequence using the PATCH property in the Setup Windows and Configuration Manager step.

Step 1. Create a folder for a new package. This package will be used to store any hotfixes you would like to deploy during a task sequence. In my lab, I used \\cm12pr1\Sources\Operating System Deployment\CCMHotfixes for my source folder.

image

Step 2. Copy the client hotfixes (.MSP Files) you want to install from the hotfix folder on the site server <InstallDirectory>\hotfix\<KBNumber>\Client into the CCMHotfixes folder.

image

Step 3. Create a package that references the folder you created. You do not need to create any programs for this package.

image

Step 4. Add a run command line step in the task sequence directly before the Setup Windows and Configuration Manager. Ensure you reference the ClientPatches package in this step.

Use the following command line:

cmd /c xcopy *.* %OSDTargetSystemDrive%\windows\CCMHotfixes /E /H /C /I /Q /Y

This command will copy the patches (.MSP Files) to %WinDir%\CCMHotfixes.

image

Step 5. Add the PATCH command in the Setup Windows and ConfigMgr Step. Here’s a few examples:

ConfigMgr 2012 R2 Cumulative Update 5 x64:

PATCH="C:\windows\CCMHotfixes\configmgr2012ac-r2-kb3054451-x64.msp"

ConfigMgr 2012 R2 Cumulative Update 5 x86:

PATCH="C:\windows\CCMHotfixes\configmgr2012ac-r2-kb3054451-i386.msp"

image

You will need to change the filename as appropriate based on the update you are applying. If you add additional patches for a future hotfix, don’t forget to update the distribution point for the ClientPatches package.

Disclaimer: The information on this site is provided "AS IS" with no warranties, confers no rights, and is not supported by the authors or Microsoft Corporation. Use of any included script samples are subject to the terms specified in the Terms of Use

Comments

  • Anonymous
    January 01, 2003
    Yes, I have tested it.
  • Anonymous
    March 31, 2015
    I don't think that the %PROCESSOR_ARCHITECTURE% variable works in an SCCM task sequence? I tested using it in a batch file in a legacy package and it does not resolve.

    Have you tested and verified this works with SCCM 2012?
  • Anonymous
    July 30, 2015
    The comment has been removed
  • Anonymous
    September 23, 2015
    This is working great for devices that are newly imaged but I am having an issue with devices being reimaged that will not get the patch installed unless I first remove the device from SCCM. I watch the task sequence and the steps run the way they are supposed to but when the image is complete, the version is still 5.00.8239.1000 instead of 5.00.7958.1501 for the CU4 patch.

    Any ideas as to why this might be happening?
  • Anonymous
    July 22, 2016
    Hi,It the Patch still required for SCCM 2012 R2 SP1 CU2 (KB30100144)
  • Anonymous
    December 12, 2017
    Your post is full of spelling and grammar errors. It doesn’t speak well of you to judge others and brag about your education in this manner. It sounds as if you are very defensive. If what you are doing works for your family, then, by all means, go with it. Other parents choosing something differentl doesn’t make their parenting skills less than yours.ballon bleu or rose faux http://www.repliquemontrecartier.com/