Strategy for applying post SP2 ConfigMgr client hotfixes

Recently I performed perhaps the last SCCM2007 installation that I’ll ever do and ended up applying approximately thirty post-SP2 hotfixes. Where possible, I elected for the installer to create a package for me for any client side hotfix components. I ended up with the following list of client-side hotfixes:

  • sccm2007ac-sp2-kb977384-x86-enu.msp
  • sccm2007ac-sp2-kb2509007-x86-enu.msp
  • sccm2007ac-sp2-kb977176-x86.msp
  • sccm2007ac-sp2-kb978754-x86.msp
  • sccm2007ac-sp2-kb2309968-x86-enu.msp
  • sccm2007ac-sp2-kb2516517-x86-enu.msp
  • sccm2007ac-sp2-kb2261172-x86.msp
  • sccm2007ac-sp2-kb2528650-x86-enu.msp
  • sccm2007ac-sp2-kb2276865-x86.msp
  • sccm2007ac-sp2-kb2278119-x86-enu.msp
  • sccm2007ac-sp2-kb979199-x86.msp
  • sccm2007ac-sp2-kb2659258-x86-enu.msp

When the above hotfixes were included in the PATCHES= option, the SCCM 2007 Client installer returned with a 1603 error. An examination of the log files revealed the following:

  • KB977384 obsoleted by KB2516517
  • KB977176 obsoleted by KB2276865
  • KB2261172 obsoleted by KB2528650
  • KB2528650 obsoleted by KB2659258
  • KB979199 obsoleted by KB2659258

My initial strategy was to rearrange the hotfixes by taking this information into account. Unfortunately this strategy did not lead to any type of success. I decided to rethink my strategy and looked for a way of obtaining more information from the hotfix installation logs. My new strategy was to install the hotfixes manually one by one in the order that I had originally chosen.

The command to install a particular hotfix was based on the following example syntax:

msiexec.exe /p sccm2007ac-sp2-kb977384-x86-enu.msp /L*v %TEMP%\sccm2007ac-sp2-kb977384-x86-enu.msp.LOG /q REINSTALL=ALL REINSTALLMODE=mous

During testing I received a “Attempting to install downlevel patch for feature UpdatesAgent” failure message for the following hotfixes:

  • sccm2007ac-sp2-kb2309968-x86-enu.msp
  • sccm2007ac-sp2-kb2278119-x86-enu.msp
  • sccm2007ac-sp2-kb979199-x86.msp

What I did next was to simply place these three hotfixes at the start of my patching list. This led to a successful installation.

My final patching order was as follows:

  • sccm2007ac-sp2-kb2309968-x86-enu.msp
  • sccm2007ac-sp2-kb2278119-x86-enu.msp
  • sccm2007ac-sp2-kb979199-x86.msp
  • sccm2007ac-sp2-kb977384-x86-enu.msp
  • sccm2007ac-sp2-kb2509007-x86-enu.msp
  • sccm2007ac-sp2-kb977176-x86.msp
  • sccm2007ac-sp2-kb978754-x86.msp
  • sccm2007ac-sp2-kb2516517-x86-enu.msp
  • sccm2007ac-sp2-kb2261172-x86.msp
  • sccm2007ac-sp2-kb2528650-x86-enu.msp
  • sccm2007ac-sp2-kb2276865-x86.msp
  • sccm2007ac-sp2-kb2659258-x86-enu.msp

Note: There is a documented dependency that sccm2007ac-sp2-kb977384-x86-enu.msp MUST be installed before sccm2007ac-sp2-kb2509007-x86-enu.msp

Advertisements
This entry was posted in Uncategorized. Bookmark the permalink.

One Response to Strategy for applying post SP2 ConfigMgr client hotfixes

  1. Martin says:

    Thank you for this helpful guide. One hint for the Push Installation:
    I only install the recommenden patches and found in the installation log that the installation tried to lookup a folder \Client\ClientPatch on the Site Server. I created this folder on the Site Server and copied all my patches (11 recommended) to that directory.
    I noticed that the Push Installation then tried to install these patches in alphabetical order. So you have to rename sccm2007ac-sp2-kb977384-x86-icp1.msp (and all other patches with only 6 digits) to sccm2007ac-sp2-kb0977384-x86-icp1.msp to prevent them to be installed after the leter fixes with 7 digits.
    I never saw a hint on this around the web so I think I leave my insight here.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s