Clean up your WSUS I’ve overhauled WSUS Maintenance Utility and have added some new features which were long overdue. It also includes all the same improvements that the other refactored utilities have. 2020-03-20: Version 20.03.20 Added code contribution from firstname.lastname@example.org. Individual cleanup jobs now run separately. Improved reporting. Made slight improvements to documentation. WSUS Maintenance Utility can also be downloaded from: The Microsoft PowerShell Gallery GitHub See the full documentation available here.
Clean up your WSUS I’ve overhauled WSUS Maintenance Utility and have added some new features which were long overdue. It also includes all the same improvements that the other refactored utilities have. 2020-03-05: Version 20.03.03 ‘Burger’ Added SSL option for connecting to the WSUS server. Made the -Port switch optional. If it is not specified the default port is used. If -WsusSsl is specified, the default port for SSL is used.
You may have seen the option to use Windows Update for Business and wondering what it brings to the table when compared to WSUS and SCCM. Windows Update for Business (WUfB) is a good way of simplifying and automating the deployment of Windows Updates without using any on-premises infrastructure. The downside is that you do loose some control, but the benefits outweigh the drawbacks. As I always say, it does depend on your infrastructure and environment though.
In this post I’ll walk through how I manage and test the delivery of Windows Updates to all my clients and servers. I’ll also go through how I manage essential servers like Domain Controllers, Hyper-V hosts and I’ll touch on getting started with Cluster-Aware Updating. We’re going to group our machines into Clients and Servers, and then group each of those groups into Ring 1 and Ring 2. If you want, you can create more rings for more control, but generally I find two rings are sufficient.
Download it from the Microsoft TechNet Gallery, PowerShell Gallery and GitHub. I’ve released a major update to my Automated WSUS Maintenance utility. If you are using a previous version, please update to this new one. Fixed in version 1.7: The script will now not run the cleanup process twice. The script will now report if the service isn’t running before starting. My original post with the full documentation is available here.
I’ve been revisiting my MDT process as I wanted to try and use Windows Update to get drivers during deployment - by itself this is not a problem, I can just remove the WSUSServer=http://wsus:8530 configuration from the CustomSettings.ini. However as the device is added to the domain, Group Policy will configure the device to use the local WSUS for updates, this is desired as I still want to use WSUS for future updates, but I want to use Windows Update during deployment.
Windows Server Update Services, along with a growing list of other traditional Microsoft server products, seems to be in ‘maintenance mode’ at best. It’s been on my mind as to whether they’re going to release a cloud based version in Azure (unless they already have something like that and I’ve missed it) or if they’re going the route that I think they are: just update from the internet and don’t worry about it, which seems to be the answer when looking at Windows Autopilot.
Windows Server Update Services (WSUS) can use a lot of resources, so why not use Windows Server Core and make the most of the resources you have. In this post I’ll go through the initial steps on how to deploy and configure a WSUS server using command line and PowerShell. Important note: If you need the to boot Windows Server 2016 ISO from a USB flash drive, use the Windows USB/DVD Tool available to download direct from Microsoft.
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.
Clean up your WSUS 1 2 3 4 5 6 7 8 9 10 11 12 13 o o o-o o o o-o o o o | | | | | | |\ /| o | o o o o-o | | o-o | O | oo o-o -o- o-o o-o oo o-o o-o o-o \ / \ / | | | | | | | | | | | | |-' | | | | | | | |-' o o o--o o-o o--o o o o-o-| o o o o-o o o o-o-o o o-o o-o o o o o o | | | o | o | | | -o- | -o- o o | | | | | | | | | Version 20.
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.
Update 2018-04-20: I’ve rolled the information in this post and updated it, into a new post about setting up a WSUS server from scratch on Windows Server 2016 Core. The post is also suitable for a regular Windows Server 2016 server with a GUI. You can read it here. I’ve been dealing with some issues with a WSUS server recently. It services around 1000 devices, mostly Windows 10 with some Windows 7, Windows Server 2016/2012 R2/2012 and 2008 R2.