so i've got a windows xp custom image i'm applying in an offline media scenario. all works well, drivers inject, .wim is applied but when its done applying the image, the task sequence says to restart but it doesn't. it just sits there in the winpe environment with the command prompt window open and does not reboot. If i type exit and push enter, it restarts the machine and continues the install & all is well.. im trying to keep my images as lite touch as possible and this a large hinderer in keeping it that way..
anyone know why this happens and how to fix it.. ?
- Edited by Kevin R Whelan Monday, March 12, 2012 4:06 PM
In my instance, Server 2012, MDT 2012 Update 1, standard task sequence to deploy Windows 8. I boot to LiteTouch, run through the wizard, it applies the image and you can watch the task sequence window state that it is going to restart but it does not. The TS window closes, and I'm left with a command window. If I type "Exit" it will reboot and finish the TS but not until I do so.
Not trying to thread jack here but I figure it's the same situation.
Work out why the cmd window is opening in the first place and you'll be most of the way to finding out the problem.
By default, an unmodified MDT deployment does not present you with a CMD window during a deployment so something must have changed to make it appear. Does the CMD window appear as soon as you boot up to PE without you clicking any buttons, does it appear near the end, does it appear after you press a particular key (F8 in particular), does it appear when running a certain action in the task sequence