locked
Install Operating system does not reboot - mdt 2012 RRS feed

  • Question

  • Greetings,

       I am running the default task sequence installing a w2k3 server. It gets to the install operating system task sequence step and copies the necessary files to the c: drive, then basically throws up a command prompt and stops.

    The last few lines in the TS log are as follows:

    ===============================================================================================================

    <![LOG[Successfully complete the action (Restart computer) with the exit win32 code 0]LOG]!><time="08:11:10.712+000" date="05-17-2013" component="TSManager" context="" type="1" thread="1744" file="instruction.cxx:3036">
    <![LOG[Sending status message . . .]LOG]!><time="08:11:10.712+000" date="05-17-2013" component="TSManager" context="" type="1" thread="1744" file="utility.cxx:292">
    <![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="08:11:10.712+000" date="05-17-2013" component="TSManager" context="" type="1" thread="1744" file="utility.cxx:302">
    <![LOG[Set a global environment variable _SMSTSLastActionRetCode=0]LOG]!><time="08:11:10.712+000" date="05-17-2013" component="TSManager" context="" type="0" thread="1744" file="executionenv.cxx:668">
    <![LOG[Set a global environment variable _SMSTSLastActionSucceeded=true]LOG]!><time="08:11:10.728+000" date="05-17-2013" component="TSManager" context="" type="0" thread="1744" file="executionenv.cxx:668">
    <![LOG[Expand a string: %_SMSTSMDataPath%\Logs]LOG]!><time="08:11:10.728+000" date="05-17-2013" component="TSManager" context="" type="0" thread="1744" file="executionenv.cxx:782">
    <![LOG[Deleting file without retry]LOG]!><time="08:11:10.728+000" date="05-17-2013" component="TSManager" context="" type="1" thread="1744" file="ccmfile.cpp:1015">
    <![LOG[Clear local default environment]LOG]!><time="08:11:10.728+000" date="05-17-2013" component="TSManager" context="" type="0" thread="1744" file="executionenv.cxx:807">
    <![LOG[Updated security on object C:\_SMSTaskSequence.]LOG]!><time="08:11:10.774+000" date="05-17-2013" component="TSManager" context="" type="1" thread="1744" file="utils.cpp:829">
    <![LOG[Set a global environment variable _SMSTSNextInstructionPointer=47]LOG]!><time="08:11:10.783+000" date="05-17-2013" component="TSManager" context="" type="0" thread="1744" file="executionenv.cxx:668">
    <![LOG[Set a TS execution environment variable _SMSTSNextInstructionPointer=47]LOG]!><time="08:11:10.784+000" date="05-17-2013" component="TSManager" context="" type="0" thread="1744" file="executionenv.cxx:386">
    <![LOG[Set a global environment variable _SMSTSInstructionStackString=40]LOG]!><time="08:11:10.784+000" date="05-17-2013" component="TSManager" context="" type="0" thread="1744" file="executionenv.cxx:668">
    <![LOG[Set a TS execution environment variable _SMSTSInstructionStackString=40]LOG]!><time="08:11:10.784+000" date="05-17-2013" component="TSManager" context="" type="0" thread="1744" file="executionenv.cxx:414">
    <![LOG[Save the current environment block]LOG]!><time="08:11:10.784+000" date="05-17-2013" component="TSManager" context="" type="0" thread="1744" file="executionenv.cxx:833">
    <![LOG[Successfully save execution state and environment to local hard disk]LOG]!><time="08:11:10.799+000" date="05-17-2013" component="TSManager" context="" type="1" thread="1744" file="engine.cxx:255">
    <![LOG[Reboot to local harddisk]LOG]!><time="08:11:10.799+000" date="05-17-2013" component="TSManager" context="" type="1" thread="1744" file="engine.cxx:458">
    <![LOG[Skipped RebootSystem()]LOG]!><time="08:11:10.799+000" date="05-17-2013" component="TSManager" context="" type="1" thread="1744" file="engine.cxx:587">
    <![LOG[The action (Restart computer) initiated a reboot request]LOG]!><time="08:11:10.799+000" date="05-17-2013" component="TSManager" context="" type="1" thread="1744" file="engine.cxx:278">
    <![LOG[Sending status message . . .]LOG]!><time="08:11:10.799+000" date="05-17-2013" component="TSManager" context="" type="1" thread="1744" file="utility.cxx:292">
    <![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="08:11:10.799+000" date="05-17-2013" component="TSManager" context="" type="1" thread="1744" file="utility.cxx:302">
    <![LOG[****************************************************************************]LOG]!><time="08:11:10.815+000" date="05-17-2013" component="TSManager" context="" type="1" thread="1744" file="tsmanager.cpp:768">
    <![LOG[Execution engine result code: 2 (Success=0, Failure=1, RebootInitiated=2)]LOG]!><time="08:11:10.815+000" date="05-17-2013" component="TSManager" context="" type="1" thread="1744" file="tsmanager.cpp:770">
    <![LOG[Process completed with exit code 2147945410]LOG]!><time="08:11:10.815+000" date="05-17-2013" component="TSMBootstrap" context="" type="1" thread="1936" file="commandline.cpp:1102">
    <![LOG[Exiting with return code 0x80070BC2]LOG]!><time="08:11:10.815+000" date="05-17-2013" component="TSMBootstrap" context="" type="1" thread="1936" file="tsmbootstrap.cpp:1118">
    <![LOG[==========[ TsProgressUI started in process 1300 ]==========]LOG]!><time="08:11:10.862+000" date="05-17-2013" component="TsProgressUI" context="" type="1" thread="1400" file="winmain.cpp:327">
    ==============================================================================================================

    Any idea on what I might be missing to initiate the auto reboot after the files have been copied across please?

    Thanks

    Thursday, May 16, 2013 11:46 PM

All replies


  • <![LOG[Successfully save execution state and environment to local hard disk]LOG]!><time="08:11:10.799+000" date="05-17-2013" component="TSManager" context="" type="1" thread="1744" file="engine.cxx:255">
    <![LOG[Reboot to local harddisk]LOG]!><time="08:11:10.799+000" date="05-17-2013" component="TSManager" context="" type="1" thread="1744" file="engine.cxx:458">
    <![LOG[Skipped RebootSystem()]LOG]!><time="08:11:10.799+000" date="05-17-2013" component="TSManager" context="" type="1" thread="1744" file="engine.cxx:587">

    Good Evening David,  It looks as if there is an error with you task Sequence, DUH!?!?! You may have removed an option or disabled it. Check you task sequence configuration after the OS install. If that doesn't work, Create a vanilla task sequence to install the OS. If that works, then disable unwanted features one by one. That's about the best I can give you without reviewing your task sequence. I hope this helps.

    IT Support " Scripting Noob "


    Monday, May 20, 2013 10:39 PM
  • Thanks. I have used the standard server template task sequence without modification. If there is an error it would be with the microsoft supplied standard task sequence. I note that after the "install operating system" it has a "next phase" task. Should there be a "restart computer" before the "next phase" Im thinking there shouldnt as we have other task sequences that do automatically reboot after the 'install operating system"

    Cheers

    David Z

    Tuesday, May 21, 2013 12:22 AM
  • So as the standard template has the "install operating system" task followed by next phase, what is it in the actual "install operating system" that triggers the reboot?
    Monday, May 27, 2013 2:59 AM
  • I don't think that the reboot is initiated by MDT and it is native to standard OS Install - that a reboot is initiated. MDT should just read the last action on LiteTouch.wsf and proceed to the next one once successful.

    Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"

    Tuesday, May 28, 2013 10:45 AM
  • Still cannot work out why the system wont automatically reboot.

    In watching the screen it says - Performing action : Install operating system

    It does that for a while then it applies the unattend.xml.

    At the end of that it goes through a few actions fairly quickly like inject drivers and the last thing I see in "performing actions" is reboot.

    Thats when it stops at the command prompt. I can run wpeutil reboot and it continues with the OS install. So the reboot seems to be a task sequence thing that is magically buried within the install operating system task sequence?

    Monday, June 3, 2013 11:29 PM
  • In a standard Task Sequence (Client or Server), MDT does initiate the Reboot.  It does so under the "Postinstall" group.  See the below picture and make sure your Task Sequence has the same.


    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    Monday, June 3, 2013 11:41 PM
    Answerer
  • So the install operating system task doesnt actually install the operating system? It appears to copy the operating system files or image to the local drive.

    I have the restart computer task sequence as above.

    I created the task sequence from the standard server template and have only made two mods to inject the drivers and specify the OS installation disk partition.

    It appears this restart computer TS is failing but I dont know why.

    Tuesday, June 4, 2013 12:50 AM
  • "Install Operating System" can either install the OS (if using full media) or lay the image onto the drive (if using a custom .WIM).  But that step doesn't force a reboot.

    Can you post your full bdd.log or smsts.log to a cloud storage so we can see more than the snippet you provided above?


    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    Tuesday, June 4, 2013 1:04 AM
    Answerer
  • Thanks...ill try and find a cloud. Surely a simple reboot cannot be that hard to troubleshoot?
    Tuesday, June 4, 2013 2:33 AM
  • Shouldn't be, but sometimes the simple things are the worst.  The hard part is, I compare your log snippet against one of my own from a "Known Good" image and they are the same.  Your log indicates that it goes to reboot, the reboot was initiated, and that it was successful.  But you said it's not actually rebooting.

    Just curious, are you using WAIK or ADK?


    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    Tuesday, June 4, 2013 2:54 AM
    Answerer
  • Im using MDT 2012 update 1 and ADK.
    Tuesday, June 4, 2013 4:52 AM
  • Let use know when you have the full bdd.log or smsts.log loaded up somewhere so we can take a look.

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    Tuesday, June 4, 2013 2:32 PM
    Answerer
  • Hopefully this link will work...

    https://www.dropbox.com/sh/92oqfwr59w0r2l9/c3JrRiwrlw

    Tuesday, June 4, 2013 9:34 PM
  • I've reviewed both logs and didn't see any issue (other than the logs didn't continue after the reboot was initiated).  Everything in the logs indicate it installed the OS, did the next few steps, called for a reboot, and was told it was successful at rebooting.  Since I didn't see any logs after the reboot, that would normally indicate that the network driver didn't get loaded correctly and the machine didn't continue the Task Sequence.  After you manually force WinPE to shut down, does the machine have all appropriate drivers (specifically network)?  Maybe it's a problem with your WinPE boot image... do you have lots of drivers in WinPE?  Did you enable other features beyond the defaults?  Does the same boot image handle reboots correctly for other OSs?

    Just to be clear, though... your original statement said you were trying to deploy w2k3 server, but the WIM being used in the logs is from a folder titled "Windows Server 2008 R2 SP1 x64".


    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    Wednesday, June 5, 2013 5:51 AM
    Answerer