Create the MDT build lab deployment share Because reference images will be deployed only to virtual machines during the creation process and have specific settings (rules), you should always create a separate deployment share specifically for this process.

This section will show you how to create and configure the MDT Build Lab deployment share to create a Windows 10 reference image. However, to reduce the time needed for deployment, you might want to create a reference image that contains a few base applications as well as all of the latest updates. With Windows 10, there is no hard requirement to create reference images. Set up the MDT build lab deployment share

The image is easy to move between lab, test, and production.

To ensures that you won't have unwanted applications that could be installed as part of a driver install but not removed by the Sysprep process.

You simply get the best possible image, and if you have a problem, it's not likely to be hardware related.

To reduce development time and can use snapshots to test different configurations quickly.

The reasons for creating the reference image on a virtual platform are the following: However, the reference image is typically created on a virtual platform, before being automatically run through the System Preparation (Sysprep) tool process and captured to a Windows Imaging (WIM) file. The reference image described in this guide is designed primarily for deployment to physical devices.

HV01 is a Hyper-V server that will be used to build the reference image.Ĭomputers used in this topic.

DC01 is a domain controller for the domain.

See Prepare for deployment with MDT for more information about the server, client, and network infrastructure used in this guide.įor the purposes of this topic, we will use three computers: DC01, MDT01, and HV01.

Image capture update