When advertising this client hotfix to systems only it will works fine, but when adding this client hotfix to a Task Sequence for deploying multiple applications it goes wrong. The Task Sequence will simply fails after installing the client hotfix, and installation will stop working.
In the SMSTS.log there will be the following errors seen:
- The sms client service is not running
- Install Software failed, hr=0x80040215
- Failed to run the action: Install <software package>
- Unknown error (Error: 80040215; Source: Unknown)
This because of the following issue:
When installing the client hotfix, it will shutdown the existing ConfigMgr client and WMI. After installation of the new client hotfix, it doesn't look like the ConfigMgr client or WMI service are restarting. Without these essential parts, installation will not working again. This is the reason why the Task Sequence will fail.
Update: Best practice from Microsoft is to not use the hotfix as single step in the task sequence. Just put it in the default "Setup windows and ConfigMgr" step. In the Installation properties box, type the following: PATCH="%_SMSTSMDataPath%\OSD\<var><Package_ID></var>\i386\hotfix\KB977384\SCCM2007AC-SP2-KB977384-x86-enu.msp"
Then installation will continue working.
Just use the PATCH option in the Configuration Manager Setup part in the task sequence. That works fine and is recommended by Microsoft.
ReplyDeleteThanks for mentioning. I have corrected it in the blog now.
ReplyDeleteIts still failing. ANy other ideas?.
ReplyDeleteThe machine does not install the sccm client and exits out of the task sequence. Package is on the DP.
Once the msi has been run on the SCCM server, update the Configuration Manager Client Installation package on the DP. I forgot to do this. With the PATCH="%_SMSTSMDataPath%\OSD\\i386\hotfix\KB977384\SCCM2007AC-SP2-KB977384-x86-enu.msp", make sure the Package ID that you select is with the same Configuration Manager package and not the Package ID that was created with the hotfix.
ReplyDelete