Google Chrome – Enterprise Installer You now have a functioning Microsoft Deployment Toolkit server, with a Deployment Share specifically configured for building reference images, and a Task Sequence to build and capture a Windows 10 1709 reference image. If you’d like to get in touch with me, please leave a comment or tweet me.
Product datasheet Upgrade Price Guarantee Compatible with Windows 10, 8.1, 8, 7, Vista and XP, 32 Bit / 64 Bit Editions New language versions: Chinese - Lithuanian - Japanese - Polski - Romanian - Spanish - Czech Update Star is compatible with Windows platforms.
The Power Shell script is included below in this walk through.
Original Post This post is designed to walk through installing and configuring Microsoft Deployment Toolkit to build a reference image of Windows 10 1709 (better known as the Fall Creators Update) using a Hyper-V Virtual Machine.
Create a new VM in Hyper-V and configure it as such: Start the VM and it should boot from the Lite Touch PE_x64into the deployment environment.
You should be presented with a wizard and the name of the Task Sequence you created earlier. The Task Sequence will now run, install Windows 10 1709, update from the WSUS server, install Microsoft Office applications (if you added them) and then run Windows Update from the WSUS server again to update the Office apps, run Sys Prep and the reboot back into the MDT environment and capture the image.
Update 16/01/2018: Updated this post to reflect the release of Microsoft Deployment Toolkit 8450, which fully supports Windows 10 1709.
Update 30/10/2017: If Sys Prep is consistently failing when building your Windows 10 1709 image, it is most likely due to the Windows Store update process updating the built in UWP apps.
Solution: The best way to prevent Sys Prep from failing is to disable the Store update process or to disable internet access.
If ($Disable) Save the script in your MDT share, where the Task Sequence will be able to access it.
I save my custom scripts in a folder called _scripts the Applications folder.
The settings below enable auto log in and skip the welcome screen, so these should only be used for lab/closed environments.
Configure Configure Rules/Custom On the Rules tab of the Deployment Share properties window, add the settings below.