Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
MDT 2012 - Unexpected Restart after Processing Boot Strap Settings (No Login Window)

Answered MDT 2012 - Unexpected Restart after Processing Boot Strap Settings (No Login Window)

  • Friday, December 07, 2012 2:35 PM
     
     
    Sign In to Vote
    0

    All of a sudden I am trying to deploy an x86 image from my Deployment share. When I boot from the ISO on multiple devices, it loads all the files and processes bootstrap settings. Once it is complete, the Login window would normally popup.

    However the window doesn't popup and causes the device to reboot.

    if I use the x64 ISO that is on the same deployment share it works fine (shares same custom settings and bootstrap)

    I have deleted everything x86 in the boot folder and regenerated the images multiple times.

    any ideas?

     

All Replies

  • Friday, December 07, 2012 2:55 PM
     
     
    Sign In to Vote
    0

    This usually happen when you try to automate the process but when a critical driver (disk, mass sotrage, nic) is missing.

    try to hit f8 to bring up a command prompt and interrupt the reboot then check

    • if you have an IP address
    • if you can access the disks
    • the log files in X:\minint\smsosd\osdlogs

    David Sebban | Nelite North America | My Blog | Follow me on twitter : @davidsebban

     
  • Friday, December 07, 2012 3:05 PM
     
     
    Sign In to Vote
    0

    I have an IP, I can access the disks, all the log files show everything 100% fine.

    only thing I can see in the logs is propertywizardcomplete goes from N to Y.

     
  • Friday, December 07, 2012 3:08 PM
     
     
    Sign In to Vote
    0
    could you please share the logs ? paste the content using the code tool or upload it to skydrive

    David Sebban | Nelite North America | My Blog | Follow me on twitter : @davidsebban

     
  • Friday, December 07, 2012 3:11 PM
     
      Has Code
    Sign In to Vote
    0
     
    <![LOG[------ Done processing \\SERVER\DeploymentShare\Control\Bootstrap.ini ------]LOG]!><time="09:51:38.000+000" date="12-07-2012" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Remapping variables.]LOG]!><time="09:51:38.000+000" date="12-07-2012" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property TaskSequenceID is now = ]LOG]!><time="09:51:38.000+000" date="12-07-2012" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property DeploymentType is now = NEWCOMPUTER]LOG]!><time="09:51:38.000+000" date="12-07-2012" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Finished remapping variables.]LOG]!><time="09:51:38.000+000" date="12-07-2012" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[ZTIGather processing completed successfully.]LOG]!><time="09:51:38.000+000" date="12-07-2012" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Command completed, return code = 0]LOG]!><time="09:51:38.000+000" date="12-07-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property WizardComplete is now = Y]LOG]!><time="09:51:39.000+000" date="12-07-2012" component="Wizard" context="" type="1" thread="" file="Wizard">

     
  • Friday, December 07, 2012 3:28 PM
     
     
    Sign In to Vote
    0

    It looks like the log file is truncated, a lot of informations are missing.
    I also had similar issues (rebooting) when a MININT folder or _SMSTaskSequence Folder was left over from a previous deployment.

    could you try to run lticleanup and try again. if it still reboots, try to find log files in other locations :

    • c:\minint
    • c:\windows\temp
    • c:\_SMSTaskSequence

    David Sebban | Nelite North America | My Blog | Follow me on twitter : @davidsebban

     
  • Friday, December 07, 2012 3:30 PM
     
     
    Sign In to Vote
    0

    I just pulled out all the extra information. its able to map and execute all the needed scripts. I have tried new HDD's. deleting partitions and doing all the cleanup already.

     
  • Friday, December 07, 2012 3:36 PM
     
     
    Sign In to Vote
    0
    We'll need more logs than that I'm afraid.
     
  • Friday, December 07, 2012 3:38 PM
     
     
    Sign In to Vote
    0

    as David said, you are probably not hitting the share. Can you check the bootstrap.ini and make sure it points to the right place?


    • Edited by Amnon Feiner Friday, December 07, 2012 3:38 PM
    •  
     
  • Friday, December 07, 2012 3:52 PM
     
     
    Sign In to Vote
    0

    what logs do you want? just the bdd.log?

     
  • Friday, December 07, 2012 3:58 PM
     
     
    Sign In to Vote
    0
    Try to post the logs somewhere they can be downloaded from, like skydrive or dropbox.
     
  • Friday, December 07, 2012 5:38 PM
     
     
    Sign In to Vote
    0

    at this time I cant upload the full logs, just snippets due to our policies. However its not a network share issue, as I can make the share to upload the files.

    it seems to be an issue executing the litetouch.vbs because the log is showing wizardcomplete property is Y causing it to not launch the wizard.

    our 64bit instance shares the same deploymentshare and boot strap so I know it has to be something stupid. as to why the 32bit iso wont launch the wizard.

     
  • Friday, December 07, 2012 5:59 PM
     
     
    Sign In to Vote
    0

    When the wizard starts and you press F8, it prevents a reboot. So right after you log on to your share, at the prompt type net use. Do you get any mapping? Does it point to the intended deployment share? Can you list the mapping here?


    • Edited by Amnon Feiner Friday, December 07, 2012 6:00 PM
    •  
     
  • Friday, December 07, 2012 6:01 PM
     
     
    Sign In to Vote
    0
    yes the drive is mapped. I know its something to do with something telling the log wizardcomplete is Y, so the wizard never pops up. ive gone through all my standard troubleshooting so I may need to open a ticket with MS. however I am trying to not have to do that.
     
  • Friday, December 07, 2012 6:15 PM
     
     Answered
    Sign In to Vote
    0

    Issue is now resolved. I had DaRT integration enabled, however I guess I never configured for x86 images. I disabled DaRT in PE and rebuilt the ISO's. I now have no issues.

    the funny thing is the dart failure showed up in absolutely no logs.

    • Marked As Answer by David Stamen Friday, December 07, 2012 6:15 PM
    •