Feature Request - "Needs Reboot" Expanded Sort/Search Options
I see lots of somewhat similar requests, but here is what would help me immensely.
In the "Needs Reboot" we can currently filter simply by yes or no.
Right now I have to hover over the Yes to see if it's one of 2 things I typically see:
Updating core OS Files or Windows Updates asked for a reboot (or sometimes both)
With programs like MS Edge, Symantec, Firefox, Chrome and other frequent updating programs, almost every device in inventory is flagged to reboot daily for core OS files. While they are important at some point, I don't usually focus on them daily.
I do focus on the Windows Updates ones. I would like one of 3 things to happen:
1) The "Pin" in the Needs Reboots header instead of sorting by yes or no, include the option to pick the specific reasons within.
2) In either the Search or Filter boxes, let me type "Windows Updates" and have it search within the Reboot Needed messages
3) Split the Needs Reboot Column (or add individual addable columns) one for Needs Reboot (WU) and Needs Reboot (Core)
I saw the posts on collections and sql reports, and I'll try them as a temporary solution, but with a ton of Active Directory OUs and collections, and being able to manually reboot different sections at different times, I really need it as a live tool directly from the various collections screens.
Thanks!
Comments
Hi
I use this Dynamic collection, you can use it under any other collection (like different OU's) to have a good view of systems in need of a reboot
F V,
I made the collection to match your screen. I only have 88 machines in the collection. I did fresh full scans on them all and what scares me is of the 88, only 59 have the "Yes" Needs Reboot in the GUI. Of the 59, 9 of the Yes are for Updating Core OS Files only.
So had I focused today on just the Yes showing Windows Updates as I have in the past, I would miss the 29 No's and the 9 Core-Only Yes's that apparently have that registry setting.
Does your collection of devices have that discrepancy too? Off to investigate which needs what.
Thanks!
did your recent scans scanned that registry path ?