News and Updates
- Microsoft Deployment Toolkit appears to be largely abandoned in favour of ConfigMgr and Auto Pilot - both of which are paid solutions. I intend to use MDT until it becomes unfeasible and then I have a few ideas of where to move to after that. There are some Open Source solutions that I’d like to look into and I plan to write about them.
- Please check out my MDT-Setup script which will automatically install and configure MDT the same as using this guide. A major time saver if you don’t want to do it manually.
- We must use the older Windows 10 2004 ADK and WinPE because MDT expects x86 support for WinPE. There are workarounds for this but currently deploying Windows 10 works with this older ADK and WinPE.
In this guide we will walk through installing and configuring Microsoft Deployment Toolkit to build and capture a reference image of Windows 10 22H2 using a Hyper-V Virtual Machine. It’s assumed that you have a server or PC ready to install MDT and create a file share for MDT to build the image with.
Here are the links to the software we’ll be using:
- Windows 10 version 2004 Assessment and Deployment Kit (ADK)
- Windows PE add-on for ADK 2004
- Microsoft Deployment Toolkit (8456)
- Microsoft Deployment Toolkit (8456) Update KB4564442
- Windows 10 Download from Microsoft | Volume Licensing Service Center
Installing Microsoft Deployment Toolkit and Dependencies
- First, we’ll install the Windows 10 ADK. During setup additional files will need to be downloaded, so it may take some time depending on your internet connection
- On the “Select the features you want to install” screen, select the following:
- Deployment Tools
- Imaging And Configuration Designer (ICD)
- Configuration Designer
- User State Migration Tool (USMT)
- WinPE is a separate install. Install the WinPE add-on by running the adkwinpesetup.exe, there is no specific configuration during the install wizard
- Now install MDT by running the setup file downloaded earlier. There is no specific configuration during the install wizard
- Finally, extract the files from MDT_KB4564442, and copy them to
%ProgramFiles%\Microsoft Deployment Toolkit\Templates\Distribution\Toolsreplacing the existing files
Creating the Deployment Share
- Open the Deployment Workbench from the Start Menu
- Right click on Deployment Shares
- Select New Deployment Share
- Enter the path for the Deployment Share:
- Enter the Share name: Build$
- Give the share a description
- On the Options screen, accept the defaults as you can change them later
- Complete the wizard to create the share
- By default, the share permissions are set the local administrators group. We’ll revisit this later
Adding an Operating System
- Mount the Windows 10 22H2 ISO in File Explorer
- Go to Deployment Workbench > Operating Systems
- Right click and select New Folder
- Enter the name Windows 10 22H2 and click through the wizard to create the folder
- Right click again and select Import Operating System
- In the wizard, select Full set of source files and then enter the root of the mounted ISO as the Source directory
- For the destination directory name enter Windows 10 22H2 and complete the wizard
- Go to the Operating Systems > Windows 10 22H2 node and rename the new entries added to Windows 10 22H2 Edition for ease of use
Creating Package Folder for Future Updates
- Go to Deployment Workbench > Packages
- Create a folder named Windows 10 22H2
Now we’ll create a selection profile so that the Task Sequence only attempts to install updates for Windows 10 22H2 that we make available through MDT.
Creating A Selection Profile
- Expand the Advanced Configuration node
- Right click on Selection Profiles and select New Selection Profile
- Name it Windows 10 22H2
- On the Folders page, tick the Windows 10 22H2 folder under Packages and complete the wizard
If you want to add some applications to be a part of your reference image, here I’ll cover how to add VLC as an example application. It is also possible to use a package manager to grab applications from the internet and silently install them. I’ve written a guide on how to use Chocolatey to do this. Using the guide you can install Chocolatey and then use it to install applications as part of a Task Sequence, provided you have internet access.
- Go to Deployment Workbench > Deployment Share > Applications
- Right click on Applications and select New Application
- In the New Application Wizard, choose Application with source files
- Give the application the name: VLC
- Enter the Source directory of the installation files
- Enter the Destination directory: VLC
- For the Command line enter anything, we’ll revisit this later
- On the summary page, click Next and after the files are copied click Finish to complete the wizard
- Right click on VLC, go to the Details tab
- Enter the following for the quiet install command:
VLC is now set up to be installed silently by the Task Sequence.
To add other software, you’ll need to repeat the steps above, with the relevant Command line to silently install them. Below are a few command lines for some software I frequently install silently, along with the links to the ‘offline’ installers.
msiexec /I googlechromestandaloneenterprise64.msi /qn
We now need to create a new Task Sequence to create a reference image.
Creating a Task Sequence
- In Deployment Workbench, go to Task Sequences
- Right click and select New Task Sequence
- For the ID enter: W10-22H2
- Name it Build Windows 10 22H2
- Select Standard Client Task Sequence
- Select the Operating System Windows 10 22H2
- Select Do not specify a product key at this time
- Enter an Organization name
- Select Do not specify an Administrator password at this time
- Complete the wizard
Now we’ll configure the Task Sequence.
Configuring the Task Sequence
- Right click on the Task Sequence just created and select Properties
- Go to the Task Sequence tab on the Properties window of the Task Sequence
- Expand the Preinstall folder and select the Apply Patches item
- Change the Selection Profile to Windows 10 22H2
- Go to the State Restore folder and select Windows Update (Pre-Application Installation)
- On the right side of the Properties window, go to the Options tab
- Uncheck the Disable this step tick box and do the same with Windows Update (Post-Application Installation)
- If you skipped the Importing Applications section, please disable the Install Applications item and go to step 16, if not please continue
- Go to the Install Applications item
- In the right side of the Properties box, select the Install a single application option and click the Browse… button
- Select Google Chrome and change the name Install Applications to Google Chrome
- Install other Applications, copy and paste the Install Applications item and repeat steps 13 - 15 for the applications of your choice
- Click Apply and close the Task Sequence
Next, we’ll create a domain user account for MDT for use as a service account.
Creating a service account for MDT in Active Directory
- Go to Active Directory Users and Computers
- Create a user called
mdt_adminand give it a complex password
- Go to the Server or PC where the Deployment Share is hosted
- Give the user
mdt_adminFull Control share permissions and Full Control permissions to all the files and folders in the Deployment Share
Next, we need to configure the Bootstrap.ini and the CustomSettings.ini files to control certain aspects of the deployment environment. The settings below enable auto log in and skip the welcome screen, so these should only be used for lab or closed development environments.
- In Deployment Workbench, right click the Deployment Share and select Properties
- Select the Rules tab and click the Edit Bootstrap.ini button
- Add the settings below to the Bootstrap.ini
- Close and Save the Bootstrap.ini
On the Rules tab of the Deployment Share properties window, add the settings below.
We now need to create the boot media to boot the VM into the deployment environment.
Creating the Boot Media
- In Deployment Workbench, right click on the Deployment Share
- Select Update Deployment Share
- Select Completely regenerate the boot images
- Complete the wizard. It will take some time to create the boot images
Testing and Capturing a Reference Image
To test everything, we need to copy the ISO file that we just generated. It is in the Boot folder in the Deployment Share. Go to the Server or PC that is hosting the deployment share and navigate to the boot folder. Inside there should be a file named
LiteTouchPE_x64.iso. Copy this file to a location where a Hyper-V Virtual Machine will be able to access it.
Create a new VM in Hyper-V with the following configuration:
- For Hyper-V Only: Generation 1, not 2. I’ve had issues reported with Gen2 VMs
- At least 2x vCPUs
- At least 4GB of RAM
- Network Adaptor with access the local network
- Virtual Hard Drive of at least 40GB, preferably on fast media
- Boot from CD using the
- Make sure Use Automatic Checkpoints is disabled
Start the VM and it will boot from the
LiteTouchPE_x64.iso into the deployment environment. You will be presented with a screen with the name of the Task Sequence you created earlier. Select your Task Sequence and click Next and the task sequence will begin. The Task Sequence will install Windows 10 22H2, update from the internet/WSUS server, install the optional applications if you added them, and then run Windows Update from the internet/WSUS server again. It will then run SysPrep and attempt to reboot back into the deployment environment from the local disk and send the image to the MDT server.
When this process completes the VM will be shutdown and a file named
W10-22H2_YEAR_MONTH_DAY_HOUR_MINUTE.wim will be in the Captures folder in the Deployment Share.
You now have a reference image for Windows 10 22H2 and a Microsoft Deployment Toolkit installation, with a deployment share specifically configured for building and capturing reference images. We’ll cover setting up a deployment share and focus on tasks to support deploying Windows to real hardware in this article: Deploy Windows 10 22H2 Reference Image.
Support My Work
If you would like to support me, please check out the links below.
If you have any questions or comments please leave them below.