free780 Posted February 19, 2019 Posted February 19, 2019 https://www.askwoody.com/2019/server-2016-ltsc-patches-take-for-e-ver-there-are-numerous-reasons-why-and-not-much-you-can-do-about-it/ Automation via SCCM or the Windows Update powershell module kind of works around this. I guess it's Server 2019 or cloud.
Arthur Posted February 25, 2019 Posted February 25, 2019 There's quite a lot of unhappy sysadmins on Microsoft's uservoice site... https://windowsserver.uservoice.com/forums/295047-general-feedback/suggestions/32121229-stop-the-windows-update-madness-on-ws2016 No response from Microsoft.
free780 Posted February 25, 2019 Author Posted February 25, 2019 LTSC releases seem to be 2nd class citizens. The bug was fixed in 1703 but MS want you to move to Server 2019 or shift your workload into Azure. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now