Dynamic Group to show Windows Feature Update ready?
Andrew Gresbach
We inadvertently had some VM's in the wrong WSUS group and now found that some had a Windows 10 feature update come down to their VM (currently on 1909 and its trying to go to 2004)......its the pop up saying its ready and when to reboot to finish. Trying to get my head wrapped around how many more might be out there waiting for this since that reboot can take a while. Curious if theres any way PDQ can help dynamically show me any that are in that state? i know i can report on current S/P version but hoping to catch the ones that havent yet but will next reboot
1
Comments
I don't currently have a way to test this, but this PowerShell Scanner might work: https://github.com/pdq/PowerShell-Scanners/tree/master/PowerShell%20Scanners/Get%20Available%20Windows%20Updates
awesome thanks for the tip! you dont happen to know the 2004 upgrade kb # by chance i thought i could focus in on to use w/ this?
I'm sorry, but I don't.
no problem. i wonder if theres any way via registry or other to show any systems that have this flagged.
your scanner might be a good way to go....running the get-windowsupdate locally does populate this so i'll have to see if i can make a group based on this
that scanner worked great so thank you for the help!
follow up on this ps windows update history scanner.......still working ok but noticing on anything after windows 10 1909 (ie 2004, 20h2) its significantly slower to run this scan for some reason (20 sec or so on 1909 vs 5 min on anything newer). could there be an updated script or another method needed on newer feature builds?
and actually looking closer it looks like anything past 1909 its not even pulling results now w/ that ps script