mulderite Posted February 13, 2018 Posted February 13, 2018 (edited) Is it me or is the deployment of full Cumulative Updates for Server 2016 using WSUS just....weird? I have three 2016 servers all using WSUS. One of them will fail installing the CU each month (for the last three months) if I try and deploy it through WSUS. In the end I just download the setup file and install it at the server manually. In the last few weeks I've introduced two new 2016 servers onto the network and both times I've seen the following behaviour during the build - as in they install the December 2017 CU, restart, check with WSUS and show up as being 100% updated - then after a certain amount of time (a few hours/the next day) they'll suddenly 'see' the January 2018 CU and install that! Why is it insisting on installing the December update first? I thought the whole idea of the CU's was to just go with the latest one? And WHY is it reporting as being 100% to then backtrack after a certain amount of time to then install the next CU? I've decided with February's updates to try using the Delta version instead, hoping that this will deploy on my original 2016 server (and the other two) without issues. Has anyone else seen this behaviour with Server 2016 and WSUS? Edited February 13, 2018 by mulderite
Michael Posted February 13, 2018 Posted February 13, 2018 If all you're installing are the Delta Updates, then that makes 100% logical sense, one after the other. To be honest, I'd always deploy the Full Updates to servers, rather than Delta as there have been reported 'issues' with some Delta releases. And secondly, I don't deploy every single CU that's released, so the Full Update comes in handy for this scenario.
mulderite Posted February 13, 2018 Author Posted February 13, 2018 Apologies, maybe I didn't make it clear in my first post. Up 'til now I HAVE been using the full updates, I always decline the Delta versions, which is why I can't understand it doing one then the other...
Michael Posted February 13, 2018 Posted February 13, 2018 Normally approving a newer CU should decline the older CU, but you could always do it manually, or perform a Clean Up operation within WSUS.
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