Restarting task sequence after reboot - MDT 2013 (self.sysadmin). My guess would revolve around the way your capturing your image. Here is the way I setup and capture mine and it works great every time. Setup MDT on a workstation that you can setup vmware workstation on. (You want your base image to be done in a virtual machine so it has no.
Posted by4 years ago
Archived
Hi /r/sysadmin, I threw myself into learning MDT/WDS/Server 2012 this week. I'm working on deploying images to multiple types of machines. I've made my master image, stripped all the GPO and reset the local security policy on the machine and captured an image from it.
I can successfully 'deploy' the image to any machine, but after the reboot, my task sequence doesn't continue, meaning the final task sequence deployment box doesn't open. No applications install, none of the post-WIM installation sequence is called. It works when I use a premade image, so I imagine it has something to do with that... Here's what I've done so far to check:
- Made a new, unedited task sequence to just apply a WIM with no additional steps
- Enabled AdminAutoLogon, disabled CTRL-ALT-DEL to log on, and disabled the Windows notice after CTRL-ALT-DEL
BDD.log, SMSTS.log
![Image capture by handle failed. uopilot for sale Image capture by handle failed. uopilot for sale](/uploads/1/2/5/7/125749892/347793785.jpg)
- Both glanced over with Trace32 - no glaring errors.
_SMSTaskSequence, MININIT, %windir%Panther
- All removed from image before sysprep and verified gone with DISM after WIM generation.
WindowsTemp
- Completely cleared, DeploymentLogs doesn't generate after WIM is added to the machine and it restarts.
LTIBootstrab.vbs
- Deletes itself a second or two after running (as per the last 5-10 lines in the script), it squelches the error that LiteTouch.wsf throws (Unable to find the SMS Task Sequencer. The deployment will not proceed. )
- Tried to launch LiteTouch.wsf by itself (unable to find SMS Task Sequencer as above)
- Tried to launch Wizard.hta with the definition file
The majority of the things I read referred me to two things, one, making sure the image didn't have MININIT or _SMSTaskSequence already on it, and two, making sure I was writing to disk 0 partition 1. I double verified all of these things, with no luck. I added a custom diskpart into the sequence to set up my disk and clean it properly (I'm installing to a single drive and I want a single partition), but still nothing. I've verified that my Unattend.xml in the image has a call to wscript the LiteTouch file in MININTScripts, but it's still giving that error when called manually, and it doesn't do anything at all if you don't navigate to it and click on it.
No errors are coming up when I check over the logs, so I'm grasping at straws trying to generate errors to move in the right direction. Since my task sequence works with a premade image, I can only imagine that there's an issue with the image I took, but I don't know where to go to figure out the issue. I remember reading previously when I was first looking into this that it was recommended to delete something out of a sysprepped WIM's Unattend.xml, but I can't find the post that I read, nor can I remember what the package was I would be deleting.
The only other thing I was running into was an issue while sysprepping initially where this error was being thrown (http://i.imgur.com/K50zUFJ.jpg), so in order to resolve that I added two keys into my sysprep section of the Capture task sequence - HKLMSystemSetpCloneTag=0. I don't know if this is messing up my WIM or not, but I couldn't get it to capture period without that.
Thanks for any help ahead of time, I'm at a complete loss with this.
tl;dr: Task sequence not continuing after reboot with sysprep'd image, none of the obvious logs are showing any errors, and no idea what to do since it works with a premade image.
Edit: I'm pushing Windows 7 SP1 over a LAN, which is completely isolated from the internet.
10 comments