Guide: Sysprep and Capture on Windows 10 with MDT 2013

With MDT 2013, it’s easy to do a Sysprep and Capture of your Windows client PC.  I will try to explain step by step how you create the task “Sysprep and Capture” and how you execute it on a client PC.

First, you need to create a Task Sequence with Sysprep and Capture. This is really easy. In the deployment workbench, just right-click in the Task Sequence list to create a new task sequence and create a Sysprep and Capture task. You will have to select an operating system when you create this task.

When this is done, you can run this task on any Windows operating system.
Go to a client PC in your network and open up your deployment Share folder with windows explorer: \\ServerName\DeploymentShare$. Now you should be in your deployment share. Go to the “Scripts” folder and find the “LiteTouch.vbs” file to start Litetouch.

When Litetouch has loaded, you have to select the “Sysprep and Capture” task you created earlier.

mdt_select_task_sequence

When selected, click Next and choose “Capture an image of this reference computer”.  Now you have to enter a name for the wim file you want to create.
Continue and the MDT should do everything for you. First, it will run Sysprep, then the computer will restart and boot to Litetouch and create a copy of your operating system.
If everything goes perfectly, you are finished and can import the wim file to your operating system in the deployment workbench. The captured file can be found in \\ServerName\DeploymentShare$\Captures\.

Typical problems
If something went wrong before or during the Sysprep, I have some fixes that may help you out.

A typical error looks like this: Expected image state is Image_State_Generalize_Reseal_to_OOBE, actual image state is Image_State_Complete, sysprep did not succeed. Failure 6192, Litetouch deployment failed, return code = -2147467259 0x80004005

First of all, I would try to do a change in the registry so open up “Regedit” and go to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\”
Now open  “ImageState” and change the value to “IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE”.

If the registry fix doesn’t work, try to remove any personal apps that are included in Windows 10.

If you just want to remove all apps, you can do this:
Run PowerShell and type in this command to remove all Windows 10 apps:
Get-AppXProvisionedPackage -online | Remove-AppXProvisionedPackage –online

Want to keep your drivers?
The default settings for Sysprep is to generalize your Windows 10 image by removing all drivers. If you don’t want this to happen and keep the drivers, you can edit this registry key in your client PC before you run sysprep:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Sysprep\Settings\sppnp set PersistAllDeviceInstalls to 1.

If you have any questions or want to share your knowledge, please leave a reply!

Leave a Reply