Unanswered Strange MDT Issue - Bootstrap.ini freeze

  • Thursday, August 02, 2012 12:35 PM
     
     

    Hi

    When deploying Windows 7 with MDT I have encountered this strange issue

    PXE boot - loads up into MDT wizard – “processing bootstrap.ini settings” progress bar - freezes at this point. But if I hit enter (there are no buttons to interactive with - just a progress bar) the wizard continues correctly with the next stage of deployment. Without hitting enter, it stays at this bootstrap.ini initializing stage all day. It doesn't get to the phase of choosing the task sequence. 

    The strange this is, this problem has only started to appear recently (previous deployments were fine).

    Things I have done to trouble shoot: I have "completely regenerated" new boot.wim images and loaded these into WDS. Stripped out all but essential code from bootstrap.ini. Created a new task sequence leaving most settings as default. I have cleaned the disk using diskpart to remove any old files lingering from a bad deployment. Tested on another computer.  I have checked logs for obvious errors but because it doesn't error out at any point (it just sits there) there are no obvious errors that i can see.

    Bootstrap.ini:

    [Settings] Priority=Default

    [Default] SKIPBDDWELCOME=YES

    DeployRoot=\\servername\DeploymentShare$

    USERDOMAIN=mydomain

    USERID=adminuser

    SkipBDDWelcome=YES

     

    Its not the end of the world because I can just hit enter but its really annoying me and would rather it to be automated

    If anyone has any suggestions that would be fantastic

    Thanks


    • Edited by Tee-Eff Thursday, August 02, 2012 12:35 PM
    •  

All Replies

  • Thursday, August 02, 2012 1:07 PM
     
     

    Hi,

    Really weird :( I never had this issue, but based on your input, the issue appears before the wizard so I don't think it has anything to do with the task sequences, OSes or Applications. Here's what I would do to investigate further :

    1. Check UnattendPE_x86/64.xml to verify if there is a step running before litetouch.vbs that could cause this issue
    2. Check WinPE log files (Netsetup.log, wpeinit.log) for additional info
    3. If possible Try without drivers on a Hyper-V VM (Hyper-V additions are already part of the core Win7 image, so no need to add drivers)

    Good luck, if you find anything, please share the solution here :)


    David Sebban | Nelite North America | http://www.nelite.com/community/b/dsebban/default.aspx

  • Friday, August 03, 2012 12:16 PM
     
     
    Thanks David. Where will I find those logs?
  • Friday, August 03, 2012 1:20 PM
     
     
    when you're in WinPE, they should be in X:\windows\Debug\Netsetup.log and X:\windows\System32\wpeinit.log

    David Sebban | Nelite North America | http://www.nelite.com/community/b/dsebban/default.aspx