I have been tasked with learning it, getting it up to speed, and getting all our machines updated.
Our WSUS server had not been maintained in several months. I've seen it where removing previous updates fix the problem due to one of the updates causing a block.īeyond that, look at the eventlog and see what it says. Then install the latest SSU and the latest CU like I mentioned above. Remove the last few of them including the SSU (Servicing stack update). That won't happen in this scenario though, but you should be doing it (or automate it with WSUS Automated Maintenance (WAM) ©) You could also try downloading and manually installing those last 5 updated from May, then checking for updates again.Īre you performing the proper WSUS maintenance including but not limited to running the Server Cleanup Wizard (SCW), declining superseded updates, running the SQL Indexing script, etc.? You could try to reset the Windows Update ( clearing downloads from Software Distribution and other relevant folders )( or try the update troubleshooter ) reboot and check for updates again. You may need to mark those updates as superseded in WSUS( if that is still a thing ). Some of those would be superseded, so it doesn't seem like it is seeing the correct updates available. I would say there is something wrong from last year, as the updates go back to last May.
0 kommentar(er)
