• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 201
  • Last Modified:

MDT 2013 Sysprep and Capture

I have searched around quite a bit and have come up empty. Here is what is happening. I have MDT 2013 Update set up and working. Back in May of this year I build a source image, ran windows updates, captured and have been deploying. We have no issues with deploying.
I should state that we are attempting to capture win 8.1 pro x64.

We are at a point where I would like to update the image itself with windows updates, so I go back to our snapshot in was taking 5/2016 (this is running in hyper-v). Run windows updates, this takes a few hours but completes just fine. I create another snapshot, map the z:\ drive to the \mdt\deploymentshare$ and go to run the litetouch.wsf. This is where I the first issue popped up. It would just sit there with the screen stating it was "Processing Bootstrap settings". Did a little digging and found site stating that to get around this just create a batch file that maps the drive, then calls the litetouch.wsf script. Easy enough, this works and I can finally select my sysprep and capture task sequence.

Here is what I have been dealing with for the last few days. The sysprep and capture task sequence runs without any errors, then starts the reboot, but instead of booting into winPE and continuing with the capture it just reboot the vm back into windows.
I have checked my bdd and smsts logs and I do not see any errors. I however do have each sysprep and capture attempt showing up in the monitor pane of the Deployment Workbench and they're all "stuck" at 65% complete, on step 16 of 23.

Things I have tried. Recreating a new source vm, reimporting the source OS, then recreating/deploying a new source vm and attempting to capture, created a new deployment share imported the source OS, deployed a VM from this source OS, then attempted to sysprep and catpure. All of these have failed with the same result. The machine just reboots back into windows instead of booting in winPE to complete the capture.

Any ideas?
0
Chris Christensen
Asked:
Chris Christensen
1 Solution
 
Chris ChristensenAuthor Commented:
So i got this figured out and it really was ridiculous. There was apparently a pending reboot on the snapshot I had which was cause my issue.

After rebooting and resnapshotting the task sequence worked.
1

Featured Post

What Security Threats Are We Predicting for 2018?

Cryptocurrency, IoT botnets, MFA, and more! Hackers are already planning their next big attacks for 2018. Learn what you might face, and how to defend against it with our 2018 security predictions.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now