MDT: Capture and sysprepped reference image

  1.    04 Jul 2018 #1

    MDT: Capture and sysprepped reference image

    Hello All,

    This is my first post in this forum. However I have already followed the excellent tutorials about Windows 10 customization and used some tricks. Now I need some help.

    I use MDT 8450 to create a reference image for Windows 10 Pro 1803 with Sysprep. After installing the reference image with a MDT deploy task sequence - task most things are automated.

    I run sysprep /generalize /oobe /shutdown

    Log in in audit mode and customize the Administrator profile. After that I run sysprep again.

    sysprep /generalize /oobe /shutdown /unattend:C:\folder/copyprofile.xml

    the unattend xml file has only the copyprofile true switch in it.

    Once the system is shut down (VM) I boot into PXE and start the standard capture task of MDT. I switched off the Syspre section of the MDT task since I already ran Sysprep. The wim file is created fine.

    After that re-start the VM (not the captured wim file) and now it comes what iritates me. Windows 10 starts a bit slower and ends up at the login screen and not with the OOBE process. I see the same if I replace instal.wim of the Windows 10 ISO with the captured WIM and start the ISO in a VM it installs Windows 10, but ends up at the login screen too and not going through OOBE process.

    I would expect after I captured a WIM file, the VM would start with the OOBE process since sysprep run with shutdown option. The only thing between was I PXE booted and captured it. It seems during the capture process something has happened which might Windows think OOBE process is already done. I have to revert to last snapshot and then Windows does the OOBE process.


      My ComputerSystem Spec

  2.    05 Jul 2018 #2

    I resolved it, it was an issue with the unattend.xml file, but not the unattend.xml I used for copyprofile.

    In MDT the capture task also has an unattend file from the OS and this caused the trouble. I edited that unattend.xml file and deleted section 7 OOBE.

    Once the capture process was finsihed, Windows 10 started the OOBE process.
      My ComputerSystem Spec


Related Threads
All I customized my reference pc to which I was happy to make a WIM file. Took the image via DISM and wanted to install a new pc. I have made 3 partitions: 1. BOOT 500MB 2. Windows 100GB 3. Datadisk 50GB Weird part is that i don't know...
I've hit quite a snag here.I booted from WINPE5.1 and ran DISM and captured a Windows 10 golden instance image and the UEFI System Partition (what I traditionally knew as system partition) saved to external hard drive. It seems that I did not image...
Hi All, I've got some new DELL AIO Optiplex 3240s that are now running W10 Pro after successful clean installs. I am needing to set one up as a reference computer and then deploy that image to the rest of them. This is for the small library I...
Capture an image by saving it in a file esd in Installation and Upgrade
Hi Using Windows 10 ADK v1511, how do I capture an image directly by saving it in an esd file? Also, how do I add an image volume, to an esd file? Thanks Bye
Fall Update and Reference image in Installation and Upgrade
We use MDT 2013 for our image deployment. As of now my current directions have been to explore if we can utilize Windows 10 Professional for fiture upgrades and I have a virtual lab setup for testing and working out the methodology. Our...

Tags for this Thread

Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 12:41.
Find Us