- This topic has 1 reply, 2 voices, and was last updated 6 years, 7 months ago by .
-
Posts
-
A bit about our environment – We have a 2012 R2 server that runs WSUS and BatchPatch. All servers are configured to look to that server for their updates.
We get erratic results from our 2016 OS servers; some operate just fine, others are highly problematic. Earlier today, several of my 2016 servers hadn’t checked into WSUS since late Feb. so I ran the WAM WSUS clean up utility written by Adam Marshall. That helped a bunch of servers check in to WSUS and make WSUS feel more snappy.
The problem is, I still have a bunch of servers which show in the WSUS console as “Updates Needed: X” where X is between 2 and 10, but which deliver “No applicable updates” when I check for available updates.
Wait wait… Nevermind. The problem is, that when we approved updates 3 days ago, these 2016 servers hadn’t checked in recently so they didn’t get a chance to say, “Hey I need updates X, Y and Z!”
You can delete this post if you like, or leave it here for some other hapless soul to find in case it helps them figure out their problem.
Your app is great, thanks!
Glad you got it figured out! Also happy to hear that you think the app is great!
Thanks,
Doug
- You must be logged in to reply to this topic.