How can I automate the deployment of Windows 10 version 1709 (Fall Creators Update) using MDT and PowerShell ?


Microsoft released the new Surface Pro and recently a new operating system, Windows 10 version 1709 (Fall Creators Update). Now you can automate the installation of it using PowerShell.


This script has been written to allow you to automate the deployment Windows 10 version 1709 (Fall Creators Update) using the latest available software including:

  • Windows 10 x64 (version 1709)
  • Microsoft Deployment Toolkit (MDT) build 8443
  • Latest available 2017 drivers for the Surface Pro
  • Windows 10 ADK (version 1709)
  • Windows Server 2016

Note: This is fully automated, and as this does install a Windows Deployment Services server role hosting a boot image, you should modify the script accordingly and test it thoroughly in a lab first.

This script is tailored for one thing only, deploying Windows 10 x64 version 1709 to the Microsoft Surface Pro with all drivers loaded and MDT 2013 preconfigured. Download it and customize it to suit your needs for other hardware if you wish because what it does is pretty cool.

This script performs the following actions:-

  • Downloads and then Installs Windows ADK 10 (version 1709) if you have not done so already
  • Downloads and then Installs MDT, if you have not done so already
  • Downloads all required drivers for Microsoft Surface Pro if you have not done so already
  • Imports the Windows 10 x64 (version 1709) operating system into MDT
  • Imports the Microsoft Surface Pro drivers into MDT
  • Creates Selection Profiles for Surface Pro and WinPE x64
  • Creates a Deploy Windows 10 X64 version 1709 task sequence
  • Edits the Deploy Windows 10 X64 version 1709 task sequence and adds an inject drivers step for Microsoft Surface Pro
  • Sets a WMI query for hardware detection for the Surface Pro on the corresponding driver step
  • Injects the Microsoft Surface Pro network drivers into the LiteTouchPE_x64.wim
  • Creates custom CustomSettings.ini and BootStrap.ini files
  • Disables the X86 boot wim (as it is not needed for Surface Pro)
  • Changes the Selection Profile for the X64 boot wim to use the WinPE x64 selection profile
  • Installs the Windows Deployment Service role
  • Configures the WDS role and adds the previously created LiteTouchPE_x64.wim
  • Starts the WDS service so that you can PXE boot (UEFI network boot).

All you have to do is download the script below, modify some variables, then place certain files in the right place such as the Windows 10 x64 Enterprise (version 1709) media. Please ensure you have a working DHCP scope on your Active Directory domain controller, then PXE boot a Microsoft Surface Pro  and sit back and enjoy the show.

Step 1. Download the script

The PowerShell script will do all the hard work for you, it is in the Downloads section at the end of this guide, download it, unzip it and place it on the server that is designated to be the MDT server.

Step 2. Configure the variables in the script

Once you have downloaded and extracted the script, you need to configure certain variables interspersed throughout the script. I’ll highlight the ones you need to edit.

The most important of them is the $SourcePath variable (line 53) as this decides where to get the content from and where to store it. This variable should point to a valid drive letter, the folder name will be created if it does not exist.

sourcepath variable.png

The $FolderPath variable (line 237) specifies the MDT Deployment share root folder for example C:\MDTDeploy. folderpath.png

There are other variables to configure, for joining the Domain (lines 315-317)

join domain.png

and then you need to configure how you actually connect to the MDT server from WinPE (lines 392-396)

connect to winpe.png

Step 3. Copy the Windows 10 x64 (version 1709) operating system files

Mount a Microsoft Windows 10 x64 Enterprise (version 1709) ISO and copy the contents to $SourcePath\Operating Systems\Windows 10 x64\1709 as shown below

Continue reading this post over at here.

This entry was posted in 1709, MDT (build 8443), PowerShell. Bookmark the permalink.

Leave a Reply

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

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