In a couple of weeks the next update to Windows 10 - Redstone 4, 1803, the Spring Creators Update will be released and later this year Redstone 5, 1809 will be come out, all being well. This continues the pace set last year and the semi-annual release cycle that Microsoft have put into place. For those of you who, like me, might be wondering what would happen to Windows Server’s release cycle.

This is a round-up all my previous posts regarding deployment and configuring Windows 10, installing Microsoft Deployment Toolkit and Windows Server Update Services into one post for reference. Installing and Configuring a WSUS Server Installing WSUS from scratch! Resolving WSUS Connection Errors On Windows Server 2012 R2 Installing and Configuring Microsoft Deployment Toolkit Getting Started With Microsoft Deployment Toolkit 8443 and Windows 10 1607/1703 PXE Booting for Microsoft Deployment Toolkit PXE Booting with WDS for UEFI and BIOS Devices Building and Deploying a Windows 10/Windows Server 2016 Reference Image Building a Windows 10 1607 Reference Image with Microsoft Deployment Toolkit 8443 Deploying a Windows 10 1607 Reference Image with Microsoft Deployment Toolkit 8443 Walkthrough: Building a Windows 10 1703 (Creators Update) Reference Image with Microsoft Deployment Toolkit Walkthrough: Building a Windows 10 1709 (Fall Creators Update) Reference Image with Microsoft Deployment Toolkit Walkthrough: Building a Windows Server 2016 Reference Image with Microsoft Deployment Toolkit Customising and Configuring Windows 10 Stuck Windows Updates from WSUS on Windows 10 1607/Windows Server 2016 Windows 10 1607 (Anniversary Update) opens msn.

With Hyper-V it is possible to run VMs inside of VMs without needing to install third-party virtualization software. You might not have the need to run an entire Virtual Machine inside of another, but some upcoming security features of Windows 10 require Hyper-V to be enabled so this could be a way to have those security features on a Windows 10 VM that you otherwise would not be able to take advantage of.

Here’s a quick update on an option I missed in my previous post about how to customise the Start Menu and Taskbar for new Windows 10 1607/1703 installs. Update 2017-05-02: This also works with Windows 10 1703 (Creators Update) The method that I used in my previous post would not be suitable for other environments where you would still want users to have some control over apps that were pinned to the Start Menu.

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.

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.

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.