Continuing on from my previous post (Building a Windows 10 1607 Reference Image with Microsoft Deployment Toolkit 8443) I’ll be continuing my series of deploying Windows 10 1607 with Microsoft Deployment Toolkit build 8443. In this post we’ll be building a task sequence to deploy the reference image created previously and we’ll also be tackling domain joining, drivers, and post-imaging tasks. Update 02/05/2017: Please note that this post is also relevant to Windows 10 1703 (Creators Update) with a few minor changes, which I’ve posted about here.
Following on from my previous post (Getting Started With Microsoft Deployment Toolkit 8443 and Windows 10 1607), I’ll be continuing my series of deploying Windows 10 with Microsoft Deployment Toolkit. Update 2017-05-02: Please note that this post is also relevant to Windows 10 1703 (Creators Update) with a few minor changes, which I’ve posted about here. In this post I’ll be building a task sequence to create a reference image that would be suitable for a real world deployment on new devices or performing a ‘wipe and load’ on existing devices.
I thought about trying to find a better name for this post and this issue, but this is all I could come up with. Update 2017-10-16: A few people have contacted me and made me aware that doing the reg hack below can prevent users from using Microsoft Office Clipart, so you should be aware of that before proceeding. Additionally, I’ve found that with Windows 10 1703 (Creators Update), allowing access to http://www.
I’ve replaced this script with a much more robust script that will backup each VM, including checkpoints/snapshots. You can find that post here. Let’s celebrate the holiday season with a quick PowerShell script to backup a Hyper-V server…or maybe you just need a quick and dirty, belt and braces backup script for your Hyper-V based VMs. It’s a small, quick script leveraging Hyper-V’s PowerShell module and some traditional command line utilities, like robocopy.
For this post the demo network consists of an Active Directory Domain Controller (DC01), a WSUS server (WSUS01) - here’s a previous post on installing WSUS, a server that will have Microsoft Deployment Toolkit installed (WDS01) and a blank Hyper-V Virtual Machine for creating the reference image. Update 2017-05-02: Please note that this post is also relevant to building Windows 10 1703 (Creators Update) images. I’ve posted about the differences here.
Update 2022-08-10 I’m will be no longer updating this page since Windows 11 has now been released and Microsoft have stated that Windows will return to a 2-3 year release schedule. Windows version information is available on Wikipedia also. Update 2017-05-02 I’ll attempt to keep this up to date as new versions of Windows come out. This might seem like an odd topic to cover, but I’ve receive quite a few questions about this in recent months.
If you’ve installed a fresh install of Windows 10 1607/Windows Server 2016 recently, you may have experienced a problem when it tries to download and install updates from your local WSUS server - specifically, it doesn’t, it gets stuck. You’ve tired rebooting, stopping the BITS and WU services, deleting %systemroot%\SoftwareDistribution but nothing seems to work. Both Windows 10 1607 and Windows Server 2016 require a cumulative update that fixes this specific issue.
If you’ve seen the news from the latest Microsoft Event, you’ll know that the next Windows 10 update, dubbed the “Creator Update” will be out early next year. One of the new tools shown was Paint 3D which looks to make the creation of 3D content more accessible. You can check it out right now, if you are a member of the Windows Insider Preview Program - which anyone can join.