Microsoft Deployment Toolkit for the Enthusiast, Home or Small Business

This article is directed towards enthusiasts, IT professional’s for small businesses, or anyone who wants to create custom images and doesn’t have volume licensing, an Active Directory domain, or a lot of server infrastructure. I have also recently published a video walkthrough covering this to my YouTube channel.

I hope this article is useful to you, if it is please consider supporting my work by checking out my Patreon, or by donating with PayPal, or Ko-fi.

In this walkthrough we’re going to cover:

  • Installing Microsoft Deployment Toolkit and its dependencies on Windows 10 Home/Pro Edition.
  • Creating a Task Sequence to create a custom Windows 10 Home/Pro Edition image.
  • Creating a bootable USB drive containing the custom Windows 10 image.

What you’ll need:

  • A PC running at least Windows 10 Home Edition.
  • A Virtual Machine to create the custom image.

Here are the links to the software we’ll be using:

 

Installing Microsoft Deployment Toolkit and Dependencies

  1. First, we’ll install the Windows 10 1903 ADK. During setup additional files will need to be downloaded, so it may take some time depending on your internet connection.
  2. On the Select the features you want to install screen select:
  • Deployment Tools
  • Imaging and Configuration Designer (ICD)
  • Configuration Designer
  • User State Migration Tool (USMT)
  1. Install WinPE by running the adkwinpesetup.exe. There is no specific configuration during the install wizard.
  2. Install MDT by running the MicrosoftDeploymentToolkit_x64.msi. There is no specific configuration during the install wizard.

 

Install the Windows System Image Manager Update

  1. Unzip the archive containing the WSIM 1903 fix.
  2. Copy the two files: ImageCat.exe and ImgMgr.exe to the location the ADK is installed to. The default location is: C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\WSIM.

 

Creating the Deployment Share

  1. Open the Deployment Workbench from the Start Menu.
  2. Right click on Deployment Shares.
  3. Select New Deployment Share.
  4. Under Deployment share path enter the path: C:\DeploymentShare
  5. Under Share name, you can leave it as DeploymentShare, just remove the ‘$’ on the end so the share is not hidden.
  6. Enter a description in the Deployment share description text field.
  7. On the Options screen, accept the defaults as we’ll change them later.
  8. Complete the wizard to create the share.
  9. Browse to C:\DeploymentShare and right-click on the folder and go to Properties > Sharing > Advanced Sharing > Permissions.
  10. Add the Administrators and Users groups and check Allow Full Control permissions.

 

Obtaining the Windows 10 ISO

  1. Run the Media Creation Tool that we downloaded earlier.
  2. After accepting the EULA, choose the Create installation media for another PC option.
  3. Choose the language, edition and architecture of Windows to download.
  4. On the Choose with media to use screen, choose ISO.
  5. Browse to the location where you wish to save the ISO. Give it a descriptive name.
  6. The ISO will download.

 

Converting the ESD to a WIM

  1. Mount the Windows 10 ISO in File Explorer.
  2. Create a folder on the root of the C:\ drive called w10-src and copy all the files from the ISO to it.
  3. Open up an elevated command prompt.
  4. Change directory to the sources directory of the Windows 10 files: cd C:\w10-src\sources
  5. Now we’re going to convert the install.esd file to a WIM file as ESD files are not compatible with MDT.
  6. But first we need to know which index to export. To do this run the following command in the elevated command prompt: dism /Get-WimInfo /WimFile:install.esd
  7. A list of Windows 10 editions will be displayed, each with their own index number. Choose which one you want and make a note of the index number.
  8. Now we’re going to convert the ESD to a WIM. Run the following command, but substitute the index number for the edition you wish to install: dism /export-image /SourceImageFile:install.esd /SourceIndex:[x] /DestinationImageFile:install.wim /Compress:max /CheckIntegrity
  9. We now have a WIM file for MDT to work with.

 

Adding an Operating System to MDT

  1. Go to Deployment Workbench > Operating Systems.
  2. Right click and select Import Operating System.
  3. In the wizard, select Full set of source files and then enter the folder that we copied the Windows 10 files to from the ISO – in this case it was: C:\w10-src\ as the Source directory.
  4. For the destination directory name enter Windows 10 and complete the wizard.

 

Importing Applications

If you want to add some applications to be a part of your custom image, here I’ll cover how to add them into MDT.

  1. Download or copy the files needed for installation. For an example, let’s use VLC.
  2. Using File Explorer browse to C:\DeploymentShare\Applications.
  3. Create a folder called VLC and copy the installation file to it.
  4. Go to Deployment WorkbenchDeployment Share > Applications.
  5. Right click on Applications and select New Application.
  6. In the New Application Wizard, choose Application without source files.
  7. Give the application the name: VLC.
  8. For the Command line enter the exact name including the extension of the VLC installation file, and then add a /S for a silent install. Make sure it is a capital S. For example: vlc-3.0.8-win64.exe /S
  9. In the Working directory text box, enter: .\Applications\VLC
  10. On the summary page, click Next and after the files are copied click Finish to complete the wizard.

This will create an application entry for VLC, which will silently install VLC using the command line that we entered. You will need to do this for each application you want to install. Different applications have different ‘silent’ or ‘quiet’ install methods. They can be found online, and I go over some in the video walkthrough that this article is based on.

Here’s are some command lines for other software:

Google Chrome – Enterprise Installer

msiexec /I googlechromestandaloneenterprise64.msi /qn

Adobe Reader – Enterprise Installer

AdobeReaderDC.exe /sAll

 

Creating a Task Sequence

  1. In Deployment Workbench, go to Task Sequences.
  2. Right click and select New Task Sequence.
  3. For the ID enter an ID such as: W10-1909-H.
  4. Name it Build Windows 10 1909 x64 <Edition>.
  5. Select Standard Client Task Sequence.
  6. Select the Operating System Windows 10 1909 x64 <Edition>.
  7. Select Do not specify a product key at this time.
  8. Enter a Name and Organization.
  9. Select Do not specify an Administrator password at this time.
  10. Complete the wizard.

Now we’ll configure the task sequence and add applications.

 

Configuring the Task Sequence

  1. Right click on the Task Sequence just created and select Properties.
  2. Go to the Task Sequence tab on the Properties window of the Task Sequence.
  3. Go to the State Restore folder and select Windows Update (Pre-Application Installation).
  4. On the right side of the Properties window, go to the Options tab.
  5. Uncheck the Disable this step tick box and do the same with Windows Update (Post-Application Installation).
  6. Go to the Install Applications item.
  7. In the right side of the Properties box, select the Install a single application option and click the Browse… button.
  8. Select an application from the list and change the name Install Applications to something more descriptive.
  9. To install other Applications, copy and paste the Install Applications item and repeat the previous steps.
  10. Click Apply and close the task sequence.

Next, we need to configure the Bootstrap.ini and the CustomSettings.ini files to control certain aspects of the deployment environment. You can get my example files I made for the YouTube video from my GitHub.

 

Configuring Bootstrap.ini

This configuration will setup the WinPE deployment environment to automatically login. For the UserID and UserPassword you should use a user on the PC that is hosting the deployment share. You’ll also need to change the DeployRoot and UserDomain based on your PC name.

  1. In Deployment Workbench, right click the Deployment Share and select Properties.
  2. Select the Rules tab and click the Edit Bootstrap.ini button.
  3. Add the settings below to the Bootstrap.ini.
  4. Close and Save the Bootstrap.ini
[Settings]
Priority=Default

[Default]
DeployRoot=\\PC-NAME\DeploymentShare
UserDomain=PC-NAME
UserID=user1
UserPassword=pass1
SkipBDDWelcome=YES

 

Configuring CustomSettings.ini

The settings below automate MDT to build an image for capture. This enables you to use the resulting image as a custom install.

On the Rules tab of the Deployment Share properties window, add the settings below. You’ll need to change some settings based on your PC name.

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitLocker=YES
SkipLocaleSelection=YES
SkipTimeZone=YES
SkipDomainMembership=YES
SkipSummary=YES
SkipFinalSummary=YES
SkipComputerName=YES
SkipUserData=YES

_SMSTSORGNAME=Build Image
_SMSTSPackageName=%TaskSequenceName%
DoCapture=YES
ComputerBackupLocation=\\PC-NAME\DeploymentShare\Captures
BackupFile=Captured-Image.wim
FinishAction=SHUTDOWN
SLShare=\\PC-NAME\DeploymentShare\Logs

We now need to create the boot media in order to boot the Virtual Machine into WinPE for deployment.

 

Creating the Boot Media

  1. In Deployment Workbench, right click on the Deployment Share.
  2. Select Update Deployment Share.
  3. Select Completely regenerate the boot images.
  4. Complete the wizard. It will take some time to create the boot images.

 

Testing the Task Sequence

To test everything, we need to copy the ISO file that we just generated. It is located in the Boot folder in the Deployment Share. Copy the LiteTouchPE_x64.iso file to a location where the virtual machine will be able to access it.

Create a new virtual machine with the following configuration:

  • For Hyper-V Only: Generation 1, not 2. I’ve had issues reported with Gen2 VMs.
  • 2x vCPUs
  • 4GB of RAM
  • Network Adapter with access the local network.
  • Virtual Hard Drive of at least 40GB, preferably on an SSD.
  • Boot from CD using the LiteTouchPE_x64.iso from MDT.

 

  1. Start the VM and it will boot from the LiteTouchPE_x64.iso into WinPE.
  2. You will be presented with a screen with the name of the task sequence we created earlier. Select the Task Sequence and click Next.
  3. Click Next and the task sequence will begin.

The task sequence will install Windows 10, run Windows Update and install the applications we put in the task sequence. When this process completes the image will be captured and the VM will shut down.

Once we have a final WIM file, we need to create an ISO from it.

 

Creating an ISO From A Captured WIM

  1. Create a new copy of the win10-src files that we created at the beginning of this walkthrough. For example, I’ll create a new copy in a folder called win10-src-new.
  2. Navigate to C:\DeploymentShare\Captures and copy the WIM file to the root of the C:\ drive.
  3. Rename the WIM file to install.wim and move it to C:\win10-src-new\sources. Overwrite any old install.wim files.
  4. You can safely delete the old install.esd if it is still in the source folder.
  5. To create the ISO, we must first run a BAT file. In an elevated command line, run the following command, including the quotes: “C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\DandISetEnv.bat”
  6. Now run the following command, please be aware that you must change some of the paths to reflect your own file system: oscdimg.exe -m -o -u2 -udfver102 -bootdata:2#p0,e,bC:\Win10-src-new\boot\etfsboot.com#pEF,e,bC:\Win10-src-new\efi\microsoft\boot\efisys.bin C:\Win10-src-new\ C:\win10-custom.iso

When this command completes, you should have a new ISO file in the root of your C:\ drive called win10-custom.iso. You can now use a tool such as the Windows USB/DVD tool to make a bootable USB drive from the ISO and install your own custom Windows 10 image.

If you’d like to get in touch with me please use the comments, Twitter (you can tweet me and my DMs are open) or my contact form.

I hope this article is useful to you, as I said at the beginning of the article, please consider supporting my work by checking out my Patreon, or by donating with PayPal, or Ko-fi.

-Mike

10 thoughts on “Microsoft Deployment Toolkit for the Enthusiast, Home or Small Business

Add yours

  1. Hi! I followed your video. Thanks, it’s an awesome video really well explained.

    However, I had two questions :

    Would DeploymentWorkbench be the place to work on an ISO that would be bilangual after WinPE? (so after first reboot, when user enter language, keyboard layout, network, name, etc..)

    Is DeploymentWorkbench the place to work so I can create an ISO that can install Home And Pro?

    Thanks!

    Liked by 1 person

    1. Hi William,

      To create a multilanguage ISO you would add the languages that you need into Deployment Workbench (MDT) and then use the rest of the guide to generate an ISO from the resulting WIM. I believe you could also use the DISM command line tool as well.

      To create and ISO with both Home and Pro, you will need to use the DISM command line tool to add the other versions as additional indexes to the WIM image, and then create an ISO from that.

      I hope this helps!

      -Mike

      Like

      1. Hi!

        It sure helps.

        The thing that I wonder is that if I had a version into the WIM, how do I get it link with the languages and the task, since the task are related to the version of the OS.

        Liked by 1 person

          1. For the Home/Pro duality, on the step Converting the ESD to a WIM, I did the command line for both Index (Home and Pro) so I guess both are in the WIM File. However, when using the created ISO, I’m not able to choose which one to install in the WinPE.

            For the language, I installed the Microsoft-Windows-Client-LanguagePack-Package en-US amd64 10.0.18362.1 Language Pack and when I am in the LiteTouch ISO, I see it. However, when we are in the menu to create a user (I don’t know what it’s called) I don’t see both languages at the beginning.

            I don’t know if you could help me go further

            Liked by 1 person

Leave a Reply to Anonymous Cancel reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Create a website or blog at WordPress.com

Up ↑

%d bloggers like this: