Solved

MDT 2013 Sysprep and Capture

Posted on 2016-11-16
1
78 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
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

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

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

Our Group Policy work started with Small Business Server in 2000. Microsoft gave us an excellent OU and GPO model in subsequent SBS editions that utilized WMI filters, OU linking, and VBS scripts. These are some of experiences plus our spending a lo…
There's a better way to communicate time sensitive or critical info.
Established in 1997, Technology Architects has become one of the most reputable technology solutions companies in the country. TA have been providing businesses with cost effective state-of-the-art solutions and unparalleled service that is designed…
I've attached the XLSM Excel spreadsheet I used in the video and also text files containing the macros used below. https://filedb.experts-exchange.com/incoming/2017/03_w12/1151775/Permutations.txt https://filedb.experts-exchange.com/incoming/201…

821 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