Build and Capture Windows 10


An updated post on how to build and capture Windows 10 is now located at the following link:

This update will show you, step by step, on how to do it with MDT 2013 Update 1, which is recommended. The below post is still somewhat relevant, but not 100% accurate!


Yesterday the Technical Preview of Windows 10 was released and of course this needs to be tested with Configuration Manager 2012! This guide will show you how to create a custom wim-file that can be used to deploy several computers.

To be noted is that this isn’t supported by Microsoft yet since it’s not the final product, just a preview. In my lab I have the latest version of SCCM installed, 2012 R2 CU3.

Now on to the interesting part! Start by downloading the ISO from Microsoft and extract the “install.wim” file to the source directory.


Next, add the wim file to ConfigMgr.


Enter the path to the wim-file as UNC. (Local paths are not supported)



Add the information required, name of image, version and description.


On the “Summary” page, click “Next” and check the progress.


When completed, click on “Close”



Do not forget to distribute the content to the distribution points!

The next step is to create the task sequence that will be used for building and capturing Windows 10 Technical Preview.

Right click on “Task Sequences” and select “Create Task Sequence”


On the first page, select to create a task sequence that will be used for “Build & Capture”
(Build and capture a reference operating system)



Enter the name of the task sequence and select a proper Boot-image.


Add the wim-file we just copied and select the image that will be used. (Also select if a password for local admin should be set or if the account should be disabled)
In this case we also need to provide the product key. Normally you would not enter it here, but since this is a preview you will be asked to enter it in the middle of the build if not specified here.


Since we are building a reference image, the client should be joined to a workgroup and not a domain.


Next, select the ConfigMgr package and specify the settings needed. (If any)


Again, since this is a preview, there are no updates to be installed, so select “Do not install any software updates”



Press next on “Install Applications”, or add if there are any you wan’t to try with.

On “System Preparation” press next.

Under “Image Properties”, enter the details needed.


Next, specify where the image should be saved and which account that has access to the share. (Note that the file name should be specified as well)


Press Next on the summary and verify the results when completed before clicking on “Close”



When completed, we need to deploy the task sequence to a device collection where we have a client that will be used to build on. This client should be a virtual client, otherwise we will get extra drivers in the image.

Right click on the newly created task sequence and select “Deploy”


In the wizard, select the collection that the task sequence should be deployed to.


Press next and select how the task sequence should be available. For build and capture I always select “Media and PXE only”.


Pres next until you get to summary and verify the settings. Then press Next again and verify the results.



When completed it’s time to start the client that should be used for the build and capture process. Boot it either from PXE or create a bootable media and select the task sequence we just created,


Press Next and watch the magic happen!






This entry was posted in SCCM, Windows 10 and tagged , , , , , , , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *