Announcing Extended Support for WSUS 3.0 SP2

___________________________________________________________________________________________________________________________

IMPORTANT ANNOUNCEMENT FOR OUR READERS!

AskPFEPlat is in the process of a transformation to the new Core Infrastructure and Security TechCommunity, and will be moving by the end of March 2019 to our new home at https://aka.ms/CISTechComm (hosted at https://techcommunity.microsoft.com). Please bear with us while we are still under construction!

We will continue bringing you the same great content, from the same great contributors, on our new platform. Until then, you can access our new content on either https://aka.ms/askpfeplat as you do today, or at our new site https://aka.ms/CISTechComm. Please feel free to update your bookmarks accordingly!

Why are we doing this? Simple really; we are looking to expand our team internally in order to provide you even more great content, as well as take on a more proactive role in the future with our readers (more to come on that later)! Since our team encompasses many more roles than Premier Field Engineers these days, we felt it was also time we reflected that initial expansion.

If you have never visited the TechCommunity site, it can be found at https://techcommunity.microsoft.com. On the TechCommunity site, you will find numerous technical communities across many topics, which include discussion areas, along with blog content.

NOTE: In addition to the AskPFEPlat-to-Core Infrastructure and Security transformation, Premier Field Engineers from all technology areas will be working together to expand the TechCommunity site even further, joining together in the technology agnostic Premier Field Engineering TechCommunity (along with Core Infrastructure and Security), which can be found at https://aka.ms/PFETechComm!

As always, thank you for continuing to read the Core Infrastructure and Security (AskPFEPlat) blog, and we look forward to providing you more great content well into the future!

__________________________________________________________________________________________________________________________

Hi everyone! Brandon Wilson here just passing along a friendly note that consumers of WSUS will probably be jumping for joy to hear. Nathan Mercer and Michael Niehaus have published some useful news in this blog post (contents can also be read below).

So, without further delay….here it is in Nathan and Michael’s words:

—–

Windows Server Update Services (WSUS) is key to the Windows servicing process for many organizations. Whether being used standalone or as a component of other products like System Center Configuration Manager or Windows Small Business Server, it provides a variety of useful features, including automating the download and installation of Windows updates.

While WSUS has been built into Windows Server 2012 and later operating systems, most people didn’t realize that it was a separate product for earlier operating systems like Windows Server 2008 R2. Because the version that complemented Windows Server 2008 R2, WSUS 3.0, was considered a separate product, it had a separate support lifecycle, and that lifecycle was due to end in July of 2017, even though extended support for Windows Server 2008 R2 continues until January of 2020.

To remedy this situation, we have extended WSUS 3.0 support to coincide with the Windows Server 2008 R2 end of support date. Now, both will be supported through January 14, 2020. While this reduces the sense of urgency, we still would like to encourage organizations to move all remaining WSUS 3.0 servers to a later version, a process that involves migrating to a new version of Windows Server where WSUS 4.0 (or later, in the case of the upcoming Windows Server 2016 release) can be used.

For those using Windows 10, it is particularly important to look at moving to WSUS 4.0 (or later) to support the deployment of Windows 10 feature updates, which add new features to Windows 10. Support for this new type of update has been added to WSUS 4.0 via an update to WSUS itself. This functionality isn’t available in WSUS 3.0 because mainstream support for that version has already ended (extended support does not add new capabilities; it only fixes security issues).

To help you with the migration process to WSUS 4.0 (or later), we have provided some additional documentation to help guide you through the process. For more information on WSUS, be sure to check out the WSUS team blog.

—–

This change is great news, however don’t let it deter you from embracing WSUS 4.0! Hopefully this post will be of some help, and if you have questions are comments, please feel free to leave them here or on the above linked post.

Until later….Brandon Wilson