OSD - Failure message - The step (insert name) must be running in full OS - Error 80070032
I am trying to capture a Windows 7 image with the base components I think I will need on all systems. Stuff like .net 4.0 full (ie extended), Microsoft Office 2007 professional, etc. I am not sure if it has anything to do with it but I have a
message about "(packagename) must be running in full OS." I ahve the install software setups with several reboots in between. I was told that the process would just pick back up where it left off before the reboot but I am wondering what I am doing
wrong... I also cannot get Windows Updates to install in any capture I do so I am wondering if things are misconfigured somehow. Installing updates on an actual deploy from image works, just not in capture and this is a time waster as far
as I am concerned. I should be able to do both. HELP!! Thanks in advance.
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="10:06:48.455+000" date="04-25-2011" component="TSManager" context="" type="1" thread="1884" file="instruction.cxx:2957">
<![LOG[Expand a string: FullOS]LOG]!><time="10:06:48.455+000" date="04-25-2011" component="TSManager" context="" type="0" thread="1884" file="executionenv.cxx:782">
<![LOG[!bInWinPE, HRESULT=80070032 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\instruction.cxx,2725)]LOG]!><time="10:06:48.455+000" date="04-25-2011" component="TSManager" context="" type="0" thread="1884" file="instruction.cxx:2725">
<![LOG[The step (Install "Visual FoxPro Drivers-Visual FoxPro ODBC Driver") must be running in full OS]LOG]!><time="10:06:48.455+000" date="04-25-2011" component="TSManager" context="" type="3" thread="1884" file="instruction.cxx:2725">
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="10:06:48.455+000" date="04-25-2011" component="TSManager" context="" type="1" thread="1884" file="instruction.cxx:2979">
<![LOG[Failed to run the action: Install "Visual FoxPro Drivers-Visual FoxPro ODBC Driver".
The request is not supported. (Error: 80070032; Source: Windows)]LOG]!><time="10:06:48.455+000" date="04-25-2011" component="TSManager" context="" type="3" thread="1884" file="instruction.cxx:2981">
<![LOG[Sending status message . . .]LOG]!><time="10:06:48.455+000" date="04-25-2011" component="TSManager" context="" type="1" thread="1884" file="utility.cxx:292">
<![LOG[Send a task execution status message SMS_TSExecution_ActionFailError]LOG]!><time="10:06:48.470+000" date="04-25-2011" component="TSManager" context="" type="1" thread="1884" file="utility.cxx:314">:2725">Anything worth doing is worth doing right.
April 25th, 2011 1:42pm
When trying to do an install of visual fox pro, i assume you have a reboot step before that? in that reboot step you can change whether to boot to the PE or currently installed windows mode. I would make these your last steps in the task sequence so everything
that needs to be installed in PE mode can be installed before this step.
With the windows updates are you installing all approved updates? do you have them also advertised to the same collection where your systems is receiving the task sequence from (IE: unknown computers)? The computer needs to be a member of the collection
where the updates are advertised.
I have an updates advertisement to the same collection where I have my os deployments.
Kind Regards, Tom Ziegler http://www.sccmguy.com | Twitter @Tom_Ziegler
Free Windows Admin Tool Kit Click here and download it now
April 25th, 2011 2:00pm
The "install software" and "install update" actions are done by the SCCM client, which is only available in Full OS (not in WinPE).
If you have any application that requires a reboot, make sure that the application itself does not do the reboot. Instead, it should return a reboot error code, or that you add a reboot step. This reboot step should be a reboot to the full OS and not to
WinPE.
April 25th, 2011 2:42pm
Thanks for Jogging my memory Tom and Kerwin! I am going to change that and try it now. I remember seeing that before and wondering what the difference was. That makes sense, will update after I try it!
Anything worth doing is worth doing right.
Free Windows Admin Tool Kit Click here and download it now
April 25th, 2011 2:48pm
1) No reboot step before FoxPro, but I think what I was seeing were errors in the event log AFTER the product was installed and subsequently rebooted and it was parsing back through the task sequences. So, I "THINK" it was installed OK at that point,
but after making the changes mentioned to the restart properties it fixed it so I am not going to try to figure out if I am right in my theory. My main problem is fixed.
2) With the windows updates, I think I was running into this buzzsaw of a problem here:
http://support.microsoft.com/kb/2009754
The install takes quite a while but its something I can ignore now while I go about other business and it completes and captures in the background.
Anything worth doing is worth doing right.
April 26th, 2011 9:51am
Right. Well, turns out it was an EBKAC. Needed to specify the:
SMSSLP, SMSMP, and FSP
in the Setup Windows and ConfigMgr section, as described here, just short of halfway down the page:
http://www.windows-noob.com/forums/index.php?/topic/3102-build-and-capture-windows-7-sample-task-sequence/
Now its closed :)
Anything worth doing is worth doing right.
Free Windows Admin Tool Kit Click here and download it now
April 27th, 2011 9:04am