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 SysPrep 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. This issue is a known issue, but one I’ve managed to dodge when building previous versions of Windows 10. With 1709, I’ve had SysPrep fail every time.

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 Building a Windows 10 1703 (Creators Update) Reference Image with Microsoft Deployment Toolkit Building a Windows 10 1709 (Fall Creators Update) Reference Image with Microsoft Deployment Toolkit 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.

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.

In a previous post I walked through how to install MDT, it’s dependencies, and how to create a reference image to deploy. In this post I’ll be doing the same thing but centred around building a Windows Server 2016 image 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: 24/07/2017) is the most recent release and fully supports Windows Server 2016.

In my previous scripts I’ve included a function to send log files to an on-premises Exchange server. I’ve now put together an example script to improve this function to send emails to external e-mail providers, for example: Office 365, Outlook.com or GMail.com. This new code is designed to support many different requirements: No logging at all. Logging but with no e-mail. Logging with e-mail. E-mail with username & password authentication, with SSL.

At the time of writing (2017-07-18) the latest PowerShell available is PowerShell 5.1 which is a part of Windows 10 1607 and Windows Server 2016. To find which version of PowerShell you have, type this command into PowerShell: 1 $PSVersionTable.PSVersion To upgrade PowerShell, you’ll need the latest Windows Remote Management for your version of Windows. You might also need to upgrade WinRM to remotely manage servers using the Server Manager tool, which comes with Windows Server and is a part of RSAT for Windows 10 version 1607 and later.

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.

UPDATE 2017-11-07 After testing the method below on Windows 10 1703, I found that it wasn’t working as it did with 1607. To disable One Drive and remove the One Drive folder from the Navigation Pane of Windows Explorer, enable the group policy item: Computer Configuration/Policies/Administrative Templates/Windows Components/OneDrive/Prevent Usage of OneDrive for file storage and also set the following registry key from 1 to 0: 1 2 HKEY\_CLASSES\_ROOT\CLSID\{018D5C66-4533-4307-9B53-224DE2ED1FE6} "System.IsPinnedToNameSpaceTree"=dword:00000000 Please note that the registry key must be set on a per user basis.