As Windows is now delivered ‘as-a-service’ with major updates being released biannually, you may want to push out these major updates using WSUS. In previous posts I’ve covered deploying Windows 10 1703 (Creators Update) as a clean install with Microsoft Deployment Toolkit and also how to perform an upgrade to Windows 10 1703 using MDT. In this post, I’ll walk through the process of pushing out the upgrade to Windows 10 1703 using WSUS.
If you’re looking to deploy the latest version of Windows 10 1703 (better known as the Creators Update) as a fresh install, please check out this post. This post is designed to walk through installing and configuring Microsoft Deployment Toolkit and to create a Task Sequence to upgrade to Windows 10 1703 from a previous version of Windows. The Windows upgrade process has come along way in recent years, so in certain circumstances it may be worth while running an upgrade, rather than a wipe-and-load.
Following on from a previous post which covers some queries and issues I had when first deploying Windows 10 1703 (better known as the Creators Update) this post is designed to walk through installing and configuring Microsoft Deployment Toolkit to build a reference image of Windows 10 1703 using a Hyper-V Virtual Machine. Installing & Configuring Microsoft Deployment Toolkit and Dependencies We’ll be using Microsoft Deployment Toolkit (MDT) version 8443, which at the time of writing is the most recent release and fully supports Windows 10 1703.
With the release of Windows 10 1703 (Creators Update) ISO on the Volume Licensing Service Center, I’ve recently been looking into using the “final” code with Microsoft Deployment Toolkit (MDT) to build reference images and discover what issues are present. This post is a round up of differences and issues I’ve found with building and deploying Windows 10 1703 thus far, and some resolutions. For a full walk through on installing MDT and creating a Windows 10 1703 (Creators Update) reference image, check out this post.
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.
As we hurtle towards the release of the Creators Update, I decided to take a look at the new OOBE (Out Of Box Experience) that users will see when installing the update. The new OOBE has been a part of the Insider preview builds for some time now. It’s main feature is Cortana support, so you can use speech to go through setup which appears to be as much as a cool and useful feature as it is about accessibility.
A feature that I’m very happy to see coming in the Creators Update for Windows 10 is Night light. It’s not exactly a headline feature, but I’m happy to see it and wanted to draw attention to it. What Night light does is change the colour temperature of the display as the sun sets, reducing the blue light and enabling your eyes to relax as you work into the night which, I personally do a lot.
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.
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 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.