How To Create A Custom Windows 10 Image For Deployment

Skip to principal content

Create a custom Windows PE boot prototype with Configuration Managing director

Article
03/xvi/2022
four minutes to read

Applies to

Windows x

In Microsoft Endpoint Configuration Manager, y'all can create custom Windows Preinstallation Surround (Windows PE) kick images that include extra components and features. This topic shows yous how to create a custom Windows PE 5.0 kick image with the Microsoft Deployment Toolkit (MDT) wizard. You tin besides add the Microsoft Diagnostics and Recovery Toolset (Dart) 10 to the boot prototype as role of the boot image creation process.

The boot image that is created is based on the version of ADK that is installed.

For the purposes of this guide, nosotros will use i server computer: CM01.

CM01 is a domain member server and Configuration Manager software distribution bespeak. In this guide CM01 is a standalone principal site server. CM01 is running Windows Server 2019. Still, an before, supported version of Windows Server can also be used.

An existing Configuration Director infrastructure that is integrated with MDT is used for the post-obit procedures. For more information about the setup for this article, come across Prepare for Zippo Affect Installation of Windows 10 with Configuration Manager.

Add together DaRT 10 files and ready to brand the boot paradigm

The steps below outline the process for adding DaRT 10 installation files to the MDT installation directory. You lot as well copy a custom groundwork epitome to be used afterward. These steps are optional. If yous do not wish to add DaRT, skip the steps beneath to copy DaRT tools and later skip calculation the Dart component to the boot image.

Nosotros assume y'all take downloaded Microsoft Desktop Optimization Pack (MDOP) 2015 and copied the x64 version of MSDaRT100.msi to the C:\Setup\Sprint 10 folder on CM01. We also assume you have created a custom background image and saved it in C:\Setup\Branding on CM01. In this section, we use a custom background epitome named ContosoBackground.bmp.

On CM01:

Install DaRT 10 (C:\Setup\Sprint 10\MSDaRT100.msi) using the default settings.
Using File Explorer, navigate to the C:\Program Files\Microsoft Dart\v10 folder.
Copy the Toolsx64.cab file to the C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\Tools\x64 folder.
Re-create the Toolsx86.cab file to the C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\Tools\x86 folder.
Using File Explorer, navigate to the C:\Setup folder.
Copy the Branding folder to D:\Sources\OSD.

Create a boot image for Configuration Manager using the MDT sorcerer

By using the MDT wizard to create the boot image in Configuration Managing director, yous proceeds boosted options for adding components and features to the boot image. In this section, you create a kick paradigm for Configuration Managing director using the MDT sorcerer.

On CM01:

Using the Configuration Manager Console, in the Software Library workspace, aggrandize Operating Systems, correct-click Kick Images, and select Create Boot Image using MDT.
On the Parcel Source page, in the Parcel source folder to exist created (UNC Path): text box, type \\CM01\Sources$\OSD\Boot\Zero Touch WinPE x64 and click Side by side.

Note

The Zero Touch WinPE x64 folder does not yet exist. The folder will be created after past the sorcerer.
On the General Settings page, assign the name Zero Touch WinPE x64 and click Side by side.
On the Options page, select the x64 platform, and click Side by side.
On the Components page, in addition to the default selected Microsoft Data Access Components (MDAC/ADO) support, select the Microsoft Diagnostics and Recovery Toolkit (DaRT) bank check box and click Side by side.

Add together the DaRT component to the Configuration Manager kicking paradigm.

Note: Another common component to add together hither is Windows PowerShell to enable PowerShell support within Windows PE.
On the Customization page, select the Use a custom background bitmap file check box, and in the UNC path: text box, scan to \\CM01\Sources$\OSD\Branding\ContosoBackground.bmp and and so click Side by side twice. Wait a few minutes while the boot epitome is generated, and then click End.
Distribute the boot prototype to the CM01 distribution point by selecting the Kick images node, right-clicking the Zero Touch WinPE x64 kick image, and selecting Distribute Content.
In the Distribute Content Sorcerer, add together the CM01 distribution point, and complete the wizard.
Using Configuration Manager Trace, review the D:\Program Files\Microsoft Configuration Managing director\Logs\distmgr.log file. Practice not continue until you can see that the boot epitome is distributed. Look for the line that reads STATMSG: ID=2301. You lot also can monitor Content Status in the Configuration Managing director Console at \Monitoring\Overview\Distribution Condition\Content Status\Nil Touch WinPE x64. See the following examples:

Content status for the Aught Bear upon WinPE x64 boot image
Using the Configuration Director Console, in the Software Library workspace, under Boot Images, right-click the Cipher Touch WinPE x64 kick paradigm and select Properties.
On the Data Source tab, select the Deploy this boot image from the PXE-enabled distribution indicate check box, and click OK.
Using Configuration Manager Trace, review the D:\Program Files\Microsoft Configuration Manager\Logs\distmgr.log file and look for this text: Expanding PS100009 to D:\RemoteInstall\SMSImages.
Review the D:\RemoteInstall\SMSImages binder. Yous should run across 3 folders containing boot images. Two are from the default kick images, and the third folder (PS100009) is from your new boot paradigm with DaRT. See the examples below:

Note: Depending on your infrastructure and the number of packages and boot images present, the Image ID might exist a unlike number than PS100009.

Next, meet Add together a Windows x operating organization epitome using Configuration Manager.

Set for Zero Impact Installation of Windows 10 with Configuration Director
Add a Windows 10 operating organization image using Configuration Director
Create an application to deploy with Windows x using Configuration Manager
Add drivers to a Windows x deployment with Windows PE using Configuration Director
Create a task sequence with Configuration Director and MDT
Deploy Windows 10 using PXE and Configuration Manager
Refresh a Windows seven SP1 client with Windows 10 using Configuration Manager
Supervene upon a Windows 7 SP1 client with Windows 10 using Configuration Manager

Feedback

Submit and view feedback for