Install KB977384 for R3 Support During OSD Fails
Hello, I am having a problem installing the R3 Update for ConfigMgr SP2 clients during my OSD process. The update works just fine when upgrading existing clients in the field that are already deployed, but when trying to do it as part of the OSD task sequence, it goes bad. I am using the default package the the hotfix creates. I get the following error in my SMSTS.log: Failed to run action: Install ConfigMgr 2007 R3 Update (KB977384). Unknown error (Error: 80040215). Thoughts? Thanks!
October 29th, 2010 12:18pm

Hi, From the program (KB977384 - Advanced Client Patch Install) and under Properties/Advanced have you checked "Allow this program to be installed from the Install software task ..." ??
Free Windows Admin Tool Kit Click here and download it now
October 29th, 2010 2:07pm

Hey thanks for the reply! yes, I do have the box checked, but it doesn't help. Thoughts?
October 29th, 2010 2:35pm

Why not use the method recommended in KB977203 for deploying hotfixes during OSD (http://support.microsoft.com/?id=977203) or if you are using MDT use the script and process as document by Michael Murgolo: http://blogs.technet.com/b/deploymentguys/archive/2010/08/13/automatically-populate-the-patch-property-for-the-configmgr-2007-client-installation.aspx.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
October 29th, 2010 5:35pm

Hi, I think this error is related to the ConfigMgr client which stops during the patch installation and not start after. Can you try to add a reboot task or a client service start one (net start ccmexec) after that of KB977384 and see the result ?
October 29th, 2010 5:51pm

Hi, I think this error is related to the ConfigMgr client which stops during the patch installation and not start after. Can you try to add a reboot task or a client service start one (net start ccmexec) after that of KB977384 and see the result ? It is easier to just set the client hotfix step in the Task Sequence to "Continue on error", and the fix installs fine without stopping the TS.
Free Windows Admin Tool Kit Click here and download it now
November 1st, 2010 10:23am

Thanks for the replies! Yes it does appear the root cause is the ccmexec service is restarting during the TS which blows it up. I tried to set "Continue on error" and it does allow the TS to complete succesfully, but the fix is never applied. I tried using the PATCH parameter as Jason suggested and it appears that works! It looks like it might be impossible to update the configmgr client during the Install Software step. Thanks for help!
November 1st, 2010 11:54am

Thanks for the replies! Yes it does appear the root cause is the ccmexec service is restarting during the TS which blows it up. I tried to set "Continue on error" and it does allow the TS to complete succesfully, but the fix is never applied. I tried using the PATCH parameter as Jason suggested and it appears that works! It looks like it might be impossible to update the configmgr client during the Install Software step. Thanks for help! Strange, works 100% of the time for me with the continue on error stipulation. Good luck.
Free Windows Admin Tool Kit Click here and download it now
November 1st, 2010 12:22pm

Interesting, its good to know that is another option to explore if I have issues once I have multiple patches at some point. Thx!
November 1st, 2010 1:22pm

Why not use the method recommended in KB977203 for deploying hotfixes during OSD (http://support.microsoft.com/?id=977203) or if you are using MDT use the script and process as document by Michael Murgolo: http://blogs.technet.com/b/deploymentguys/archive/2010/08/13/automatically-populate-the-patch-property-for-the-configmgr-2007-client-installation.aspx. Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys This does not work.
Free Windows Admin Tool Kit Click here and download it now
November 10th, 2010 12:52pm

I found if my OSD build sequence contains multiple drive partitions (for example, building a machine for use with bitlocker), then I can't use %_SMSTSMDataPath% but I have to instead hard code to the C:\. If I do that, it works.
November 19th, 2010 2:25pm

I've had the same experiance as bcehr above. The variable _SMSTSDataPath didn't work, nor did %SystemDrive%. Fully hardcoding the path to the .msp worked. I don't like having a hardcoded path, but it works. Like bcehr I have multiple drive partitions due to BitLocker. PATCH="C:\_SMSTaskSequence\OSD\XXX100011\i386\hotfix\KB977384\sccm2007ac-sp2-kb977384-x86-enu.msp" Remember to refresh/update the Configuration Manager client package used in your TS to ensure your distributions points contain the hotfix.
Free Windows Admin Tool Kit Click here and download it now
December 14th, 2010 2:37am

Yeah, I really don't like having to hard code either, but right now I don't have any other choice :( If you happen to find another option, let me know!
December 14th, 2010 8:17am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics