ConfigMgr client no longer installing during task sequence SCCM 2007

I've been trying to create an image and deploy an image of Dell Latitude E6430 laptops that while the deployment of the image works it does not install the SCCM client (configmgr client). This used to work in my environment but no longer does.
I can deploy the client manually either through the SCCM console or from the client itself. But during the task sequence deploying a captured image it does not install and thus and software I need installed as part of the TS does not get installed.
But the rest of the image works fine including driver deployment, sysprep, domain join, etc. If I watch the job run I do see it start downloading the SCCM client during the TS job but then reboots and that's it. Not sure where to look to see what
could be going on. I read somewhere about a possible driver issue but if the rest of the TS works and all drivers install then how could it be that? If anyone has any suggestions I would greatly appreciate it! Oh by the way I'm still using
SCCM 2007, haven't upgraded yet. Thanks!
Brian Stein

What's interesting is in the smsts.log file it shows that part of the TS completed successfully. So I'm going to try importing the cab files just to make sure I'm all set with that and I will change my TS to NOT auto apply drivers but rather I'll point
directly to the new driver package I created from the extracted cab and will follow up then. If interested a copy of the smsts.log file found inside the _SMSTaskSequence folder on the client machine (2/3 of the way down I 'bolded' the line where it seems
to say the configmgr client step succeeded:
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-ara.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-ara.exe ]LOG]!><time="13:49:12.259+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-chs.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-chs.exe ]LOG]!><time="13:49:12.305+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-cht.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-cht.exe ]LOG]!><time="13:49:12.337+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-csy.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-csy.exe ]LOG]!><time="13:49:12.352+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-dan.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-dan.exe ]LOG]!><time="13:49:12.368+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-deu.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-deu.exe ]LOG]!><time="13:49:12.399+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-ell.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-ell.exe ]LOG]!><time="13:49:12.415+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-enu.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-enu.exe ]LOG]!><time="13:49:12.446+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-esn.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-esn.exe ]LOG]!><time="13:49:12.508+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-fin.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-fin.exe ]LOG]!><time="13:49:12.539+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-fra.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-fra.exe ]LOG]!><time="13:49:12.555+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-heb.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-heb.exe ]LOG]!><time="13:49:12.586+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-hun.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-hun.exe ]LOG]!><time="13:49:12.602+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-ita.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-ita.exe ]LOG]!><time="13:49:12.633+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-jpn.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-jpn.exe ]LOG]!><time="13:49:12.649+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-kor.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-kor.exe ]LOG]!><time="13:49:12.680+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-nld.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-nld.exe ]LOG]!><time="13:49:12.695+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-nor.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-nor.exe ]LOG]!><time="13:49:12.727+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-plk.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-plk.exe ]LOG]!><time="13:49:12.758+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-ptb.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-ptb.exe ]LOG]!><time="13:49:12.773+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-ptg.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-ptg.exe ]LOG]!><time="13:49:12.805+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-rus.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-rus.exe ]LOG]!><time="13:49:12.820+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-sve.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-sve.exe ]LOG]!><time="13:49:12.851+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-trk.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-trk.exe ]LOG]!><time="13:49:12.867+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/client.msi to C:\_SMSTaskSequence\Packages\RPS00005\i386/client.msi ]LOG]!><time="13:49:13.756+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380"
file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/hotfix/KB977384/sccm2007ac-sp2-kb977384-x86-enu.msp to C:\_SMSTaskSequence\Packages\RPS00005\i386/hotfix/KB977384/sccm2007ac-sp2-kb977384-x86-enu.msp ]LOG]!><time="13:49:13.787+300"
date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/msrdcoob_x86.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/msrdcoob_x86.exe ]LOG]!><time="13:49:13.819+300" date="02-26-2014" component="OSDSetupHook" context="" type="1"
thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/msxml6.msi to C:\_SMSTaskSequence\Packages\RPS00005\i386/msxml6.msi ]LOG]!><time="13:49:13.881+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380"
file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/wimgapi.msi to C:\_SMSTaskSequence\Packages\RPS00005\i386/wimgapi.msi ]LOG]!><time="13:49:13.897+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380"
file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/windowsinstaller-kb893803-v2-x86.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/windowsinstaller-kb893803-v2-x86.exe ]LOG]!><time="13:49:14.084+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/windowsupdateagent30-x86.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/windowsupdateagent30-x86.exe ]LOG]!><time="13:49:14.302+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/wmirdist.msi to C:\_SMSTaskSequence\Packages\RPS00005\i386/wmirdist.msi ]LOG]!><time="13:49:14.318+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380"
file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/ia64/BITS25/windowsserver2003-kb923845-ia64-deu.exe to C:\_SMSTaskSequence\Packages\RPS00005\ia64/BITS25/windowsserver2003-kb923845-ia64-deu.exe ]LOG]!><time="13:49:14.427+300" date="02-26-2014"
component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/ia64/BITS25/windowsserver2003-kb923845-ia64-enu.exe to C:\_SMSTaskSequence\Packages\RPS00005\ia64/BITS25/windowsserver2003-kb923845-ia64-enu.exe ]LOG]!><time="13:49:14.505+300" date="02-26-2014"
component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/ia64/BITS25/windowsserver2003-kb923845-ia64-fra.exe to C:\_SMSTaskSequence\Packages\RPS00005\ia64/BITS25/windowsserver2003-kb923845-ia64-fra.exe ]LOG]!><time="13:49:14.583+300" date="02-26-2014"
component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/ia64/BITS25/windowsserver2003-kb923845-ia64-jpn.exe to C:\_SMSTaskSequence\Packages\RPS00005\ia64/BITS25/windowsserver2003-kb923845-ia64-jpn.exe ]LOG]!><time="13:49:14.661+300" date="02-26-2014"
component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/ia64/msrdcoob_ia64.exe to C:\_SMSTaskSequence\Packages\RPS00005\ia64/msrdcoob_ia64.exe ]LOG]!><time="13:49:14.692+300" date="02-26-2014" component="OSDSetupHook" context="" type="1"
thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/ia64/msxml6_ia64.msi to C:\_SMSTaskSequence\Packages\RPS00005\ia64/msxml6_ia64.msi ]LOG]!><time="13:49:14.911+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380"
file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/ia64/windowsupdateagent30-ia64.exe to C:\_SMSTaskSequence\Packages\RPS00005\ia64/windowsupdateagent30-ia64.exe ]LOG]!><time="13:49:15.316+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/sccm_client.bat to C:\_SMSTaskSequence\Packages\RPS00005\sccm_client.bat ]LOG]!><time="13:49:15.332+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380"
file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-chs.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-chs.exe ]LOG]!><time="13:49:15.363+300"
date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-cht.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-cht.exe ]LOG]!><time="13:49:15.394+300"
date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-deu.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-deu.exe ]LOG]!><time="13:49:15.410+300"
date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-enu.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-enu.exe ]LOG]!><time="13:49:15.535+300"
date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-esn.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-esn.exe ]LOG]!><time="13:49:15.566+300"
date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-fra.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-fra.exe ]LOG]!><time="13:49:15.597+300"
date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-ita.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-ita.exe ]LOG]!><time="13:49:15.613+300"
date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-jpn.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-jpn.exe ]LOG]!><time="13:49:15.675+300"
date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-kor.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-kor.exe ]LOG]!><time="13:49:15.706+300"
date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-ptb.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-ptb.exe ]LOG]!><time="13:49:15.737+300"
date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-rus.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-rus.exe ]LOG]!><time="13:49:15.769+300"
date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/msrdcoob_amd64.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/msrdcoob_amd64.exe ]LOG]!><time="13:49:15.784+300" date="02-26-2014" component="OSDSetupHook" context="" type="1"
thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/msxml6_x64.msi to C:\_SMSTaskSequence\Packages\RPS00005\x64/msxml6_x64.msi ]LOG]!><time="13:49:16.112+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380"
file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/windowsupdateagent30-x64.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/windowsupdateagent30-x64.exe ]LOG]!><time="13:49:16.377+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Download done setting progress bar to 100]LOG]!><time="13:49:16.377+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1182">
<![LOG[c:\_smstasksequence\packages\rps00005\i386 is a directory. Setting directory security]LOG]!><time="13:49:16.408+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="hashdir.cpp:653">
<![LOG[c:\_smstasksequence\packages\rps00005\ia64 is a directory. Setting directory security]LOG]!><time="13:49:16.408+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="hashdir.cpp:653">
<![LOG[c:\_smstasksequence\packages\rps00005\x64 is a directory. Setting directory security]LOG]!><time="13:49:16.408+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="hashdir.cpp:653">
<![LOG[c:\_smstasksequence\packages\rps00005\i386\bits20 is a directory. Setting directory security]LOG]!><time="13:49:16.814+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="hashdir.cpp:653">
<![LOG[c:\_smstasksequence\packages\rps00005\i386\bits25 is a directory. Setting directory security]LOG]!><time="13:49:16.814+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="hashdir.cpp:653">
<![LOG[c:\_smstasksequence\packages\rps00005\i386\hotfix is a directory. Setting directory security]LOG]!><time="13:49:16.829+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="hashdir.cpp:653">
<![LOG[c:\_smstasksequence\packages\rps00005\i386\hotfix\kb977384 is a directory. Setting directory security]LOG]!><time="13:49:17.297+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="hashdir.cpp:653">
<![LOG[c:\_smstasksequence\packages\rps00005\ia64\bits25 is a directory. Setting directory security]LOG]!><time="13:49:17.407+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="hashdir.cpp:653">
<![LOG[c:\_smstasksequence\packages\rps00005\x64\bits25 is a directory. Setting directory security]LOG]!><time="13:49:17.516+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="hashdir.cpp:653">
<![LOG[Content successfully downloaded at C:\_SMSTaskSequence\Packages\RPS00005]LOG]!><time="13:49:17.578+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="resolvesource.cpp:3131">
<![LOG[Copying SMS client package source from "C:\_SMSTaskSequence\Packages\RPS00005" to "C:\_SMSTaskSequence\OSD\RPS00005".]LOG]!><time="13:49:17.578+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="basesetuphook.cpp:1504">
<![LOG[Locating architecture-specific OSDGina.dll]LOG]!><time="13:49:17.687+300" date="02-26-2014" component="OSDSetupHook" context="" type="0" thread="1380" file="basesetuphook.cpp:428">
<![LOG[Successfully copied file OSDSETUPHOOK.EXE to C:\WINDOWS\SYSTEM32]LOG]!><time="13:49:17.703+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="basesetuphook.cpp:364">
<![LOG[Successfully copied file TSProgressUI.exe to C:\WINDOWS\SYSTEM32\_SMSOSDSetup]LOG]!><time="13:49:17.703+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="basesetuphook.cpp:364">
<![LOG[Successfully copied file tsres.dll to C:\WINDOWS\SYSTEM32\_SMSOSDSetup\1033]LOG]!><time="13:49:17.703+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="basesetuphook.cpp:364">
<![LOG[Saving desktop wallpaper information.]LOG]!><time="13:49:17.703+300" date="02-26-2014" component="OSDSetupHook" context="" type="0" thread="1380" file="basesetuphook.cpp:1553">
<![LOG[Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\RPS00005]LOG]!><time="13:49:17.719+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="resolvesource.cpp:3431">
<![LOG[reference count 1 for the source C:\_SMSTaskSequence\Packages\RPS00005 before releasing]LOG]!><time="13:49:17.719+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="resolvesource.cpp:3438">
<![LOG[Delete source directory C:\_SMSTaskSequence\Packages\RPS00005]LOG]!><time="13:49:17.719+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="resolvesource.cpp:3461">
<![LOG[Released the resolved source C:\_SMSTaskSequence\Packages\RPS00005]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="resolvesource.cpp:3471">
<![LOG[Exiting ConfigureEx: 0x00000000]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupHook" context="" type="0" thread="1380" file="basesetuphook.cpp:1592">
<![LOG[Process completed with exit code 0]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupWindows" context="" type="1" thread="2032" file="commandline.cpp:1102">
<![LOG[Installing hook to 'C:\WINDOWS']LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupWindows" context="" type="0" thread="2032" file="setupwindows.cpp:785">
<![LOG[Command line for extension .EXE is "%1" %*]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupWindows" context="" type="0" thread="2032" file="commandline.cpp:229">
<![LOG[Set command line: "X:\sms\bin\i386\OSDSETUPHOOK.EXE" "/install:C:\WINDOWS" /version:6.1]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupWindows" context="" type="0" thread="2032" file="commandline.cpp:707">
<![LOG[Executing command line: "X:\sms\bin\i386\OSDSETUPHOOK.EXE" "/install:C:\WINDOWS" /version:6.1]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupWindows" context="" type="1" thread="2032" file="commandline.cpp:805">
<![LOG[Installing OSD setup hook]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1392" file="osdsetuphook.cpp:276">
<![LOG[Setup hook install completed successfully]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1392" file="vistasetuphook.cpp:111">
<![LOG[Process completed with exit code 0]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupWindows" context="" type="1" thread="2032" file="commandline.cpp:1102">
<![LOG[OfflineRegistry::Init("C:\WINDOWS")]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupWindows" context="" type="0" thread="2032" file="offlineregistry.cpp:168">
<![LOG[Loading offline registry hive "C:\WINDOWS\system32\config\software" into HKLM\OfflineRegistry1]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupWindows" context="" type="0" thread="2032" file="offlineregistry.cpp:60">
<![LOG[Loading offline registry hive "C:\WINDOWS\system32\config\system" into HKLM\OfflineRegistry2]LOG]!><time="13:49:18.545+300" date="02-26-2014" component="OSDSetupWindows" context="" type="0" thread="2032" file="offlineregistry.cpp:60">
<![LOG[CurrentControlSet is mapped to ControlSet001]LOG]!><time="13:49:19.169+300" date="02-26-2014" component="OSDSetupWindows" context="" type="0" thread="2032" file="offlineregistry.cpp:215">
<![LOG[SMS Client is not installed]LOG]!><time="13:49:19.185+300" date="02-26-2014" component="OSDSetupWindows" context="" type="1" thread="2032" file="setupwindows.cpp:1633">
<![LOG[Unloading offline SOFTWARE registry hive]LOG]!><time="13:49:19.185+300" date="02-26-2014" component="OSDSetupWindows" context="" type="0" thread="2032" file="offlineregistry.cpp:270">
<![LOG[Unloading offline SYSTEM registry hive]LOG]!><time="13:49:19.263+300" date="02-26-2014" component="OSDSetupWindows" context="" type="0" thread="2032" file="offlineregistry.cpp:284">
<![LOG[Exiting with code 0x00000000]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="OSDSetupWindows" context="" type="1" thread="2032" file="setupwindows.cpp:1751">
<![LOG[Process completed with exit code 0]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="commandline.cpp:1102">
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="instruction.cxx:3010">
<![LOG[Successfully complete the action (Setup windows and ConfigMgr) with the exit win32 code 0]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="instruction.cxx:3036">
<![LOG[Sending status message . . .]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utility.cxx:292">
<![LOG[Send a task execution status message SMS_TSExecution_ActionCompleteInfo]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utility.cxx:314">
<![LOG[MP server SCCM1.ROSNET.ROSLYNSCHOOLS.ORG and port 80. SSL=false. CRL=false.]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utility.cxx:458">
<![LOG[Site code: RPS]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utility.cxx:489">
<![LOG[Client machine name: new6430]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utility.cxx:494">
<![LOG[Client Identity: GUID:EBA20587-9DCD-4F19-B999-F6FA0E56D6CD]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utility.cxx:496">
<![LOG[Advertisement ID: RPS20136]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utility.cxx:505">
<![LOG[Package ID: RPS000E1]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utility.cxx:507">
<![LOG[Sending StatusMessage]LOG]!><time="13:49:19.325+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="libsmsmessaging.cpp:3806">
<![LOG[Formatted header:]LOG]!><time="13:49:19.325+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="libsmsmessaging.cpp:1500">
<![LOG[<Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>727ba42b-9664-4eea-8690-e285a795b870</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2014-02-26T18:49:19Z</SentTime><Protocol>http</Protocol><Body
Type="ByteRange" Offset="0" Length="4220"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
]LOG]!><time="13:49:19.325+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="libsmsmessaging.cpp:1501">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80 CCM_POST /ccm_system/request]LOG]!><time="13:49:19.325+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="libsmsmessaging.cpp:7446">
<![LOG[The request has succeeded. 200 OK]LOG]!><time="13:49:19.341+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="libsmsmessaging.cpp:7734">
<![LOG[Set a global environment variable _SMSTSLastActionRetCode=0]LOG]!><time="13:49:19.341+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:668">
<![LOG[Set a global environment variable _SMSTSLastActionSucceeded=true]LOG]!><time="13:49:19.341+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:668">
<![LOG[Expand a string: %_SMSTSMDataPath%\Logs]LOG]!><time="13:49:19.341+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:782">
<![LOG[Clear local default environment]LOG]!><time="13:49:19.341+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:807">
<![LOG[The action (Setup windows and ConfigMgr) requested a retry]LOG]!><time="13:49:19.403+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="engine.cxx:263">
<![LOG[Reboot to local harddisk]LOG]!><time="13:49:19.403+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="engine.cxx:458">
<![LOG[_OSDGinaIsConfigured variable set to TRUE]LOG]!><time="13:49:19.403+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="engine.cxx:537">
<![LOG[_SMSTSServiceStartType variable set to ]LOG]!><time="13:49:19.403+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="engine.cxx:549">
<![LOG[Calling RebootSystem()]LOG]!><time="13:49:19.403+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="engine.cxx:567">
<![LOG[OSD type of task sequence. ignore the service window setting]LOG]!><time="13:49:19.403+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="engine.cxx:669">
<![LOG[Updated security on object C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca.]LOG]!><time="13:49:19.403+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utils.cpp:829">
<![LOG[Updated security on object C:\_SMSTaskSequence.]LOG]!><time="13:49:19.419+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utils.cpp:829">
<![LOG[Set a global environment variable _SMSTSNextInstructionPointer=9]LOG]!><time="13:49:19.435+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:668">
<![LOG[Set a TS execution environment variable _SMSTSNextInstructionPointer=9]LOG]!><time="13:49:19.435+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:386">
<![LOG[Set a global environment variable _SMSTSInstructionStackString=8]LOG]!><time="13:49:19.435+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:668">
<![LOG[Set a TS execution environment variable _SMSTSInstructionStackString=8]LOG]!><time="13:49:19.435+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:414">
<![LOG[Save the current environment block]LOG]!><time="13:49:19.435+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:833">
<![LOG[Expand a string: %_SMSTSMDataPath%\Logs]LOG]!><time="13:49:19.450+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:782">
Brian Stein

Similar Messages

Latest client 1401 not getting installed during task sequence

Created a new Configuration Manager client package that includes the client hotfixes from KB2994331.
Created a subfolder named ConfigMgr Client with Hotfixes.
Using File Explorer, copied the contents of C:\Program Files\Microsoft Configuration Manager\Client to the newly created folder (K:\SCCM\ConfigMgr Client with Hotfixes).
In K:\SCCM\ConfigMgr Client with Hotfixes, created a folder named Hotfix.
Using File Explorer, navigated to the C:\Program Files\Microsoft Configuration Manager\hotfix\KB2994331\Client folder and copied the i386 and x64 subfolders to K:\SCCM\ConfigMgr Client with Hotfixes\Hotfix.
Using the Configuration Manager Console in the Software Library workspace in the Application Management / Packages node, created a new package with the following settings:
a. Name: Configuration Manager Client with Hotfixes
b. Source folder: K\SCCM\Configuration Manager Client with Hotfixes
c. Select Do not create a program
Make a note of the new package ID. In this example, it is Package ID: P01000053
Distributed the new ConfigMgr Client with Hotfixes package to the distribution point.
PATCH="C:\_SMSTaskSequence\OSD\P01000053\Hotfix\x64\Configuration Manager2012ac-r2-kb2994331-x64.msp"
Added the Windows 8.1 Image in operating System Images.
Created new task sequence Deploy Windows 8.1 X64
Deployed the task sequence to All Unknown Computers collection.
The client didn't get installed. There is no ccm or ccmsetup folder.
Any suggestions!!!!!!!!

See smsts.log and/or status message if Setup Windows and ConfigMgr was executed at all. You should see ccmsetup.log if it ran.
Torsten Meringer | http://www.mssccmfaq.de

SCCM 2012 Offline Servicing used, but still installed during Task Sequence

I have a SCCM 2012 SP1 CU4 environment and I updated my Windows 7 Enterprise x64 image install.wim with all security patches using Offline Servicing..a nice feature...works perfectly.
But when using this new updated image in my Task Sequence I noticed that still 150+ patches are installed during the Install Updates phase in my task sequence. More then 130 of them are already added using Offline Servicing so why are they added again
What is going wrong here....what am i missing....

I am having a similar issue, however I have updated my dp and it still occurs. I am doing an offline service of Windows 8.1. The update status shows a bunch of updates that have been installed, yet when deploying my TS it sill installs about 70 or 80 updates.
I have compared and the updates that are being installed are listed in the updates status window. I have checked the OfflineServicingMgr.log and the only error is:
Deleting file \\?\C:\ConfigMgr_OfflineImageServicing\UCO00121\ImageMountDir\Admin Desktop Wallpaper.JPG, FAILED, Win32 Error = 1168
Failed to remove the staging folder C:\ConfigMgr_OfflineImageServicing, GLE = 1168
It seems everything else completes fine so i cannot determine if this is causing my issues? Has anyone else had this problem before? I haven't tried with Windows 7 as we are no longer using it.

Applications failing to install during task sequence

Hello All:
I am having a major issue deploying applications through task sequence. The errors in the smsts.log are useless and every single one of my 7 applications I have assigned to the task sequence fail with the same error. Here is a snippet...
Policy Evaluation failed, hr=0x87d00269 InstallApplication 12/5/2013 2:24:36 PM 1876 (0x0754)Setting TSEnv variable 'SMSTSAppPolicyEvaluationJobID__ScopeId_A8C9B482-A47E-433C-914C-DEDEE5465DFD/Application_72ba1d7c-710f-48e5-9295-bcdc07f5cdca'='' InstallApplication 12/5/2013 2:24:36 PM 1876 (0x0754)EvaluationJob complete InstallApplication 12/5/2013 2:24:36 PM 1876 (0x0754)MP list missing in WMI, sending message to location service to retrieve MP list and retrying. InstallApplication 12/5/2013 2:24:36 PM 1876 (0x0754)m_hResult, HRESULT=87d00269 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\installapplication.cpp,1065) InstallApplication 12/5/2013 2:25:50 PM 1876 (0x0754)Step 4 out of 7 complete InstallApplication 12/5/2013 2:25:50 PM 1876 (0x0754)Install application action failed: 'GoToMeeting'. Error Code 0x87d00269 InstallApplication 12/5/2013 2:25:50 PM 1876 (0x0754)
The OS deploys, the Config Mgr client deploys, everything else appears to work except the applications.
All applications are silent installers that deploy perfectly through regular deployment.
Here is a link to my smsts.log - http://sdrv.ms/1kg8fiP
Any help on this is greatly appreciated.
Brad
-Brad

Sorry about that previous post, I probably got distracted by a cat meme or something shiny ;)
I took at look at the full smsts logfile, and it seems to me that the detection method for the appmodel apps is failing. we aren't doing appmodel via TS as yet, so I don't know what "normal/expected" looks like when invoked via TS.
but it looks to me, that the detection methods is returning 0x87d00215 "app failed to evaluate" (which I'd expect at the time of a refresh), but it then returns 0x87d00269 "required MP not found", which seems very out-of-context
to me.
are there appenforce.log and other appmodel logs that coincide with this smsts.log?
I fear I'm misunderstanding what this log is saying, the language/terminology of DCM is still foreign to me.
does "app failed to evaluate" mean, "the app detection markers were not found" (i.e. the app is not present), or, does it mean "the methods crashed so cannot determine if the app is present or absent" ?
if all of this is based on generic DCM concepts, then we should be looking for a condition, and getting a present/absent or true/false or something plain like that.
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Disable SCCM Install During Task Sequence

Hello,
We have the SCCM client installed on the WIM. We'd like to disable the SCCM client install as part of the OSD process as it is taking additional time to run and discover it is already installed. How might this be accomplished?

No, it certainly doesn't save time. It's not about time though, it's about functionality.
Why does the image build process time matter? That's a process you do maybe once every month at the most so time should not matter here.
Are you instead referring to the deployment process being time sensitive? If so, then this isn't a place where you will save time. You'll need to look at other things like network speeds, DP placement, tasks within the deployment TS and how long each is
taking, and perhaps even moving longer running items into the image itself. Honestly though, most time requirements for OS deployment are arbitrary and based on a technician sitting there baby-sitting the process. With OSD, if done correctly, it's fire and
forget -- no baby-sitting needed so does it really matter if it take 45 minutes instead of 40?
Jason | http://blog.configmgrftw.com | @jasonsandys

OSD: install software DURING task sequence based upon collection membership

Hi,
I'd like to refer to my
previous post as a starting point.
Below again the background of my question. But please advise on a powershell script that runs at the end of a task sequence that:
*enumerates the pc's collection memberships and based upon that lists the software available
*puts this software in a variable and does the installation DURING the task sequence
J.
Background:
At this time, software in our deployment (of Windows 7) is installed AFTER the task sequence is finished.
The software is deployed based upon the computer membership of collections (which get their info from AD groups).
Problem is that users see their pc as finished but don't have all their software. It even takes sometimes more then an hour even when we refresh computer policy after final reboot of the system. That's why we really need a bulletproof solution = installation
of software DURING task sequence.
Jan Hoedt

I found some time to adjust the script. Now I've created something similar for a device. Basically it finds the collections of which the device is a member, finds the targeted applications and creates task sequence variables for those applications.
See for more information:
http://www.petervanderwoude.nl/post/install-computer-targeted-application-during-os-deployment-via-powershell-and-configmgr-2012/
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Applications Installed through task sequence not showing up in Software Center

In the task sequence we use for our OSD Windows 7 machine build, we have Custom-Install Application steps which install a number of of our Applications. Each of these Applications has the "Allow this application to be installed from the Install
Application task sequence action without being deployed" checkbox checked. All of the Applications have the following properties set:
Installation behavior: Install for system
Logon requirement: Whether or not a user is logged in
Installation program visibility: Hidden
When a machine is built using this task sequence, all of the Applications install successfully - they show up in Control Panel\Programs and Features, and they run correctly. However, none of them show up in the Software Center. I'm not seeing anything in
any of the logs that indicates a problem, and the Software Center remains empty even after running all the client evaluation cycle actions
Interestingly, if I add a couple of the newly build machines to a collection, then target deployments for the already installed Applications to that collection, after running the Machine Policy Retrieval and Evaluation Cycle the Applications immediately
show up in Software Center as installed.
Does anyone know if Applications installed through a task sequence do not show up in the Software Center by default, or could you give me some troubleshooting tips if this is not normal?
Thanks for any suggestions!
SCCM 2012 SP1, Single site, W7 clients

Why you deploy applications through task sequences? Task sequences are built and meant to be used with OSD, not application deployment.
To my knowledge, if you have application install step in a task sequence and you deploy that task sequence to a collection of machines, the software center on those machines only sees the task sequence itself, not the applications inside the task sequence.
If you want your applications to be shown in the software center, change the method of deploying stuff and deploy applications as they're are meant to.

Applications installed via Task sequence

Hi,
Before my time on SCCM someone previous to me decided to deploy a group of applications using a SCCM Task Sequence. Essentially all this does is install Applications in a certain order. The time has come to uninstall this group of applications.
I've managed to uninstall everything successfully by deploying each of the applications at a Uninstall Collection with the Uninstall Action. However, if I need to rollback and re-install the task sequence on a machine I have just removed all the applications
from, SCCM seems to think it is still installed?
I can't see any detection method on the Task sequence, and I've cleared the SCCM Cache. The PC is not in the install collection.
Is there something else on the client that tells it what task sequences have been deployed against it?

You might want to run some PowerShell instead then.
The following three commands will force a re-run of a TS
Get-WmiObject -Namespace "root\ccm\scheduler" -Class ccm_scheduler_history | where {$_.ScheduleID -like "*<PackageID of Task Sequence>*"} | ft ScheduleID
Get-WmiObject -Namespace "root\ccm\scheduler" -Class ccm_scheduler_history | where {$_.ScheduleID -like "*<PackageID of Task Sequence>*"} | Remove-WmiObject
Get-Service | where {$_.Name -eq "CCMExec"} | Restart-Service
Obviously set <PackageID of Task Sequence> to the actual PackageID such as 'CMR000A2'
Cheers
Paul | sccmentor.wordpress.com

Allow this application to be installed from the install software task sequence action without being deployed

What functionality does this setting enable when checked? The only thing I find in product documentation (CM2012_Web.chm, 2/1/2014) states:
For applications to be installed by using a dynamic variable list, the following setting must be enabled on the
General tab of the application’s Properties dialog box:
Allow this application to be installed from the Install Application task sequence action instead of deploying manually
Note - My ConfigMgr 2012 R2 CU1 Application Properties now displays a tab labeled "General Information". I do not find one labeled "General". The configuration setting also reads "Allow this application to be installed
from the install software task sequence action without being deployed" instead of "Allow this application to be installed from the Install Application task sequence action instead of deploying manually"
Is application installation using a dynamic variable list the only time this configuration setting is used and functions?

Yes, you only have to check that when using the dynamic variable list(s).
Torsten Meringer | http://www.mssccmfaq.de

Applications not being deployed during task sequence - MDT 2013 + SCCM 2012 R2

Hi everyone,
I have recently integrated MDT2013 with my SCCM 2012 R2 and I am trying to move away from OSD in SCCM and switch to MDT. I managed to get a blank image deployed and now I am trying to tweak CustomSettings.ini to install applications based on the default
gateway and model. For some reason, the apps are getting pulled but not deployed. Here is what I have in the files:
Settings Package - CustomSettings.ini
[Settings]
Priority=DefaultGateway, Model, Default
Properties=MyCustomProperty
[OptiPlex 9020]
Applications001=Mozilla Firefox
[DefaultGateway]
192.168.XXX.254=Poland
192.168.XXX.254=London
[Poland]
Applications001=ESET
[Default]
DoCapture=No
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=NO
SkipProductKey=YES
Administrators001=myDomain\adminGroup
Applications001=Skype
Applications002=Office Professional Plus 2010
When the TS runs, I can see it's getting all the apps from the list, here is a snippet from ZTIGather.log
Using from [Settings]: Rule Priority = DEFAULTGATEWAY, MODEL, DEFAULT
------ Processing the [DEFAULTGATEWAY] section ------
Match found for default gateway 192.168.XXX.254, retrieving settings.
------ Processing the [Poland] section ------
Property APPLICATIONS001 is now = ESET
Added value from [Poland]: APPLICATIONS = ESET
------ Processing the [OptiPlex 9020] section ------
Property APPLICATIONS001 is now = ESET
Property APPLICATIONS002 is now = Mozilla Firefox
Added value from [OptiPlex 9020]: APPLICATIONS = Mozilla Firefox
------ Processing the [DEFAULT] section ------
Property OSINSTALL is now = Y
Using from [DEFAULT]: OSINSTALL = Y
Property DOCAPTURE is now = No
Using from [DEFAULT]: DOCAPTURE = No
Property SKIPCAPTURE is now = YES
Using from [DEFAULT]: SKIPCAPTURE = YES
<Message containing password has been suppressed>
<Message containing password has been suppressed>
Property SKIPPRODUCTKEY is now = YES
Using from [DEFAULT]: SKIPPRODUCTKEY = YES
Property APPLICATIONS001 is now = ESET
Property APPLICATIONS002 is now = Mozilla Firefox
Property APPLICATIONS003 is now = Skype
Added value from [DEFAULT]: APPLICATIONS = Skype
Property APPLICATIONS001 is now = ESET
Property APPLICATIONS002 is now = Mozilla Firefox
Property APPLICATIONS003 is now = Skype
Property APPLICATIONS004 is now = Office Professional Plus 2010
Added value from [DEFAULT]: APPLICATIONS = Office Professional Plus 2010
Property ADMINISTRATORS001 is now = myDomain\adminGroup
Added value from [DEFAULT]: ADMINISTRATORS = myDomain\adminGroup
------ Done processing CustomSettings.ini ------
So the settings do get picked up and selected. ZTICoalesce.log also shows the apps picked up:
Coalesce pattern to be used: Applications
Coalesce base variable to use: CoalescedApps
Added value ESET-KRKLON from APPLICATIONS001 to the list
Added value Mozilla Firefox from APPLICATIONS002 to the list
Added value Skype from APPLICATIONS003 to the list
Added value Office Professional Plus 2010 from APPLICATIONS004 to the list
Property CoalescedApps01 is now = ESET
Property CoalescedApps02 is now = Mozilla Firefox
Property CoalescedApps03 is now = Skype
Property CoalescedApps04 is now = Office Professional Plus 2010
ZTICoalesce processing completed successfully.
Now when I go to the smsts.log file, I can see this:
App policy for 'ESET' not received. Make sure the application is marked for dynamic app install
Policy download failed, hr=0x80004005
and later
Failed to run the action: Install Application.
Unspecified error (Error: 80004005; Source: Windows)
After that, no other apps are mentioned and seems like the failure on ESET drops the whole sequence and moves forward. I can see later the default admin being added correctly.
Any ideas what I may be missing here? Especially on the failed policy download?
Thanks
Jakub

HI,
"App policy for 'ESET' not received. Make sure the application is marked for dynamic app install"
Is the ESET application deployed? it sounds like it could be the check box on the application "Allow this application to be installed from install application task sequence action without beeing deployed" that is missing? If the application isn't
deployed this checkbox must be ticked.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

How can we get the prompt to enter IP Address, Subnet Mask , gateway and DNS Server during Task Sequence?

How can we get the prompt to enter IP Address, Subnet Mask , gateway and DNS Server during Task Sequence?

This is for 2007 but may still be relevant for 2012
http://hexdump.net/?p=391
Cheers
Paul | sccmentor.wordpress.com

"Applications Installed" tab - Is it possible to fill list from "Install Application" task sequence?

Hello!
I am using Configuration Manager 2012 with MDT 2012 Update 1.
All of my application installations are done via the "Install Application" task sequence step (some as a list, and some with variable).
I know the "Applications Installed" tab on the summary is specifically for the UDI, but is it possible to fill with applications that were installed using the "Install Application" step instead?

No. This is for Applications installed by the UDI Wizard only.
But you can add all you Application to the UDI Wizard, and make them mandatory, so the user wont uncheck them.
Thanks for the suggestion, but we will not be using the UDI for applications. We have a script that dynamically builds an application list (variable) and installs the software based on what the user has access to via deployments.
I am still holding out hope for this to be possible though. It's all based on various scripts, so my feeling is that somehow I should be able to populate that list by some other means.
My disadvantage is that I'm not very good with vb scripts, so I'm having a hard time figuring out where the "Applications Installed" tab gets its data from.

Driver Pack No Longer Being Applied During Task Sequence

Hi all,
So... this week a really strange issue manifested itself. I've been trawling through logs for the last day and I don't seem to be getting anywhere.
A task sequence, which has been working for months and hasn't been changed, all of a sudden decided to start throwing error code 0x87D00269 yesterday. It was at the stage where applications that are installed during the task sequence started to
install.
So after a looking into the error, it seems the machines are unable to download the packages, possibly through not being joined to the domain. At this stage in the task sequence, the machine should definitely be joined to the domain. We have
the command support console enabled, so I hit F8 and tried to ping the MP and the DP. Nothing. Ran ipconfig, nothing listed under the adapter. Very odd. So I checked the NIC on the back of the machine and it was up, so I booted from the task sequence
media USB stick again and hit f8. Ran ipconfig and the machine had picked up an address from DHCP no problem and shortly after, the task sequences available to the machine loaded. So I started the task sequence again and it started fine, formatted
the disk, downloaded the W7 pro x86 image, applied it, downloaded the driver pack and seemingly applied the drivers (according to the task sequence), then the machine rebooted. It started to go through the installing drivers phase (the black screen
with the sunrise), which seemed to take a longer than normal. The machine rebooted and sat at the applying settings stage for a long while, which also seemed odd and I remarked the graphics drivers didn't seem to be installed because the screen resolution
was set really low. Of course at this stage, F8 doesn't work so I waited until just before the applications started to install again. Pressed F8, ran ipconfig and no IP address. So rather than wait for the task sequence to fail again, I manually powered off
the machine and powered it back on.
So the machine boots, still with the low resolution, comes to the login screen and at this point, it's clear the machine hasn't joined the domain. I logged in with local admin account and it became clear none of the drivers had installed from the driver
pack. This is a driver pack that has run absolutely fine for months and as far as I'm aware, nothing has changed so I'm a little bit confused as to why it would just stop working.
I can't see anything in the smsts log that would explain what's happening and I've looked through the dism log but I can't find anything relevant in there.
Any ideas on where to go? This is happening on multiple machines of the same type.

Hi,
0x87D00269 CCM_E_REQ_MP_NOTFOUND
Ran ipconfig, nothing listed under the adapter.
These evidence indicate that no network driver in boot image. Is this a customized boot image? Is the machine a new model?
Press F8, run wpeinit to initialize network. If this is not working, re-add driver to boot image and try again.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]
Hi Daniel,
The boot image hasn't been modified and this machine is the exact same model as one built just a few weeks ago, with the exact same hardware. I know this because I've compared the hardware IDs of the devices side by side and they're identical.
I'm sorry but I don't follow. This issue only occurs after the driver pack downloads and (allegedly) applies. Up to that point, the machine has connectivity to the DP/MP and downloads and runs the first sections of the task sequence without issue. If I hit
F8 prior to the drivers being applied, I have my adapter listed and, of course, an IP address. That to me suggests the generic drivers already in the boot image work fine and don't need to be altered.

Sequence of events after ConfigMgr Client has successfully installed

So, I was just wondering is there anything official documented about exactly what happens after the Client has successfully installed and in particular the timings involved in these events?
For instance, My clients in my test lab will always receive their patches and applications after the client is installed - but sometimes it could take 5 mins for the process to start other times it could take 45 mins before I see anything starting to happen.
(I'm not talking about app and patch download and install times).
I know the general answer is that ConfigMgr "needs time" - but I would just like to be able to know exactly what happens in case I ever need to explain it.
Thanks!

Hi,
Theoretically, client will try to retrieve policy after SMS Agent Host service startup. But there are some processes lead to the time is undetermined, such as communicate with MP etc.
Best Regards,
Joyce Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Add PC to Collection During Task Sequence

I would like to automatically add an Unknown PC to a specific collection during a task sequence. I came across a VBScript that does this on the following site:
http://blogs.msdn.com/b/vinpa/archive/2010/09/01/how-to-add-a-known-unknown-computer-to-a-specified-collection-during-os-deployment.aspx
According to the explanation you run the script as a 'Run Command Line' task in the Task Sequence specifying the following Command line:
cscript AddMeToCollection.vbs sccmservername collectionID %_SMSTSClientIdentity%
I run this script with an account that has full admin rights on the SCCM Server. It is my understanding that you can not use a command line step that uses a specific account during the Windows PE phase, therefore I run this task after a reboot that restarts
the PC with the installed Operating System. This task is run after the Setup Windows and ConfigMgr step.
Although the task completes successfully with a 0 exit code, the PC does not get added to the specified collection. Looking at the logs the output of the script is as below:
===================================
ADDING COMPUTER TO COLLECTION
===================================
Site Server specified: mysccmserver
Collection ID specified: SMSxxxxxx
SMS Client GUID:xxxxx
Computer Name: myPC
SMS Provider Namespace = \\mysccmserver\root\sms\site_XXX
Successfully Connected to the SMS Provider Namespace.
Looking at the script it seems if the script were to execute successfully some further messages would be output:
WScript.Echo "Resource ID = " & strResourceID
WScript.Echo strComputerName & " successfully added To " & strCollID
Has anyone successfully used this script or a similar script to add a PC to a specific collection during the Task Sequence? Any advice as to where I may be going wrong would be greatly appreciated. I am using SCCM 2007 R3 and deploying Windows 7
Enterprise 64 Bit.

It is not recommended that you use domain admin to run the command. You can use a regular domain account. Notice that you need to allow the account to manage the SMS provider in site database.
1.From the Start menu, click Run and type Dcomcnfg.exe.
2.In Component Services, click Console root, expand Component Services, expand Computers, and then click My Computer. On the Action menu, click Properties.
3.In the My Computer Properties dialog box, on the COM Security tab, in the Launch and Activation Permissions section, click Edit Limits.
4.In the Launch Permissions dialog box, click Add.
5.In the Select User, Computers, or Groups dialog box, in the Enter the object names to select (examples): box, type SMS Admins and click OK.
6.In the Permissions for SMS Admins section, select the check box to allow Remote Activation.
7.Click OK twice, and then close Computer Management.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

ConfigMgr client no longer installing during task sequence SCCM 2007

Similar Messages

Maybe you are looking for