Solved

MDT 2013 Sysprep and Capture

Posted on 2016-11-16
1
99 Views
Last Modified: 2016-11-16
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
Comment
Question by:Chris Christensen
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 

Accepted Solution

by:
Chris Christensen earned 0 total points
ID: 41890701
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

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Learn how ViaSat reduced average response times for IT incidents from 10 minutes to 30 seconds.
Why pager replacement is still an issue OnPage has what some might call a “hate/hate” relationship with pagers. Not much room for love. As we see it, pagers are an antiquated bit of technology. Pagers are dinosaurs which, like most dinosaurs, sho…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

738 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question