Menu
CCMEXEC.COM – Enterprise Mobility
  • Home
  • General
  • Configuration Manager
  • Windows 10
  • Intune
  • GitHub
  • Windows 11
  • About the author
CCMEXEC.COM – Enterprise Mobility

Installing the SCCM hotfixes on the clients

Posted on December 26, 2010February 13, 2012 by Jörgen Nilsson

When doing a new installation of System Center Configuration Manager there are a number of hotfixes I always install as I mentioned earlier on my blog. A couple of them includes a client hotfix which needs to be installed on all the client either during OS deployment or another way of deploying the client for instance client push.

Installing the hotfixes in the OSD task sequence

To include multiple client in the OSD task sequence I use the PATCH= command, when deploying multiple patches they are separated with “;”. The Setup Windows and Configuration Manager step would look like this where the packageID of the SCCM Client in this case is 00100005 which must be replaced with the SCCM Client package in your environment:

PATCH=”%_SMSTSMDataPath%\OSD\00100005\i386\hotfix\kb977384\sccm2007ac-sp2-kb977384-x86-enu.msp;%_SMSTSMDataPath%\OSD\00100005\i386\hotfix\KB2263826\sccm2007ac-sp2-kb2261172-x86.msp;%_SMSTSMDataPath%\OSD\00100005\i386\hotfix\kb978754\sccm2007ac-sp2-kb978754-x86.msp”

And don’t forget to update the SCCM Client Package with new source files after installing the hotfixes so the files are actually present on the DP.

If you are using more than one partition on the clients you deploy, then you should hardcode the path to C:\ instead of using the variable, then the command line would look like this instead. PATCH=”C:\_SMSTaskSequence\OSD\00100005\i386\hotfix\kb977384\sccm2007ac-sp2-kb977384-x86-enu.msp

Installing the hotfixes with Client Push

I always configure Client Push even if I don’t use it to push out the client automatically, I use it to reinstall broken client by using the install client action in the console. My server is called SCCM01 and the path to my client package is \\SCCM01\SMSPKGE$ and they need to be changed to reflect your environment.
To install the hotfixes in the client push dialog I configure the following:

  1. I use the path to the SCCM client package on the distribution points, make sure that domain computers have read to the package.
  2. I add the following lines to the Client Push installation proporties, in this case my server name is \\sccm01\:
    PATCH=”\\sccm01\smspkge$\00100005\i386\hotfix\kb977384\sccm2007ac-sp2-kb977384-x86-enu.msp;\\sccm01\smspkge$\00100005\i386\hotfix\kb978754\sccm2007ac-sp2-kb978754-x86.msp;\\sccm01\smspkge$\00100005\i386\hotfix\KB2263826\sccm2007ac-sp2-kb2261172-x86.msp

/Jörgen

5 thoughts on “Installing the SCCM hotfixes on the clients”

  1. Joshua Morgan says:
    July 18, 2011 at 11:04 pm

    I am having a failure due to some drive reference issue. my task formats the hard drive into 3 partitions, 300mb for the system reserve, 85% for windows and applications and 15% for the user to have as temp. looking at the logs it refers to D: for the location but the data is being stored on the C: partition. any suggestions on how i could resolve this?

    Thanks,

    JM

    Reply
  2. Ang says:
    January 6, 2012 at 11:25 pm

    Jorgen,

    This is in reply to the post over at windowsnoob that you gave me some feedback on which I replied to along with an image and wanted to know if you can take a look?

    I checked out your post here and it makes sense. I wanted to know before I make the changes is in the screenshot where I would add in the changes for the default client push installation? I see that all it states is the site code which I don’t want it to break. Also if I add in those changes do I have to include all of the entries including the default one for the KB977384 which I believe it had already included but since were modifiying we have to also add back in?

    On a seperate note by default in the package for my KB977384 – advanced client hotfix – test the program command line calls
    msiexec.exe /p sccm2007ac-sp2-kb977384-x86-enu.msp /L*v %TEMP%\sccm2007ac-sp2-kb977384-x86-enu.msp.LOG /q REINSTALL=ALL REINSTALLMODE=mous

    Reply
  3. Mike C says:
    January 25, 2012 at 3:42 pm

    According to Microsoft:

    “We do not recommend that you use the variable _SMSTSMDataPath in the path because the drive letter in this path can enumerate differently in Windows PE than in the full Windows operating system.”

    http://support.microsoft.com/kb/977384

    Reply
  4. danovich says:
    February 13, 2012 at 6:58 am

    I think you mean PATCH= , not PATH=. Be aware that the task sequence installation properties field has a limit of about 1000 characters, which is quite easily reached when you are doing 12 or so hotfixes…

    Reply
  5. Fritz says:
    July 3, 2013 at 4:50 pm

    Have you been able to duplicate this process within CM12, mainly the part where you can add this string to the client push installation propterties.

    Reply

Leave a Reply Cancel reply

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.

My name is Jörgen Nilsson and I work as a Senior Consultant at Onevinn in Malmö, Sweden. This is my blog where I will share tips and stuff for my own and everyone elses use on Enterprise Mobility and Windows related topics.
All code is provided "AS-IS" with no warranties.

Tweets by ccmexec

Recent Posts

  • Windows Servicing, Personal Teams and Success.cmd
  • Windows MDM Security Baseline – Settings Catalog
  • Configuring MS Edge Security Baseline v107 using Settings Catalog
  • Configuring Desktop App Installer using CSP and script?!
  • Customizing Taskbar and Start in Windows 11 22h2 with PowerShell

©2023 CCMEXEC.COM – Enterprise Mobility | WordPress Theme by Superb Themes
This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish.Accept Reject Read More
Privacy & Cookies Policy

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Non-necessary
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
SAVE & ACCEPT