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:
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:
- I use the path to the SCCM client package on the distribution points, make sure that domain computers have read to the package.
- I add the following lines to the Client Push installation proporties, in this case my server name is \\sccm01\:
5 thoughts on “Installing the SCCM hotfixes on the clients”
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?
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
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.”
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…
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.