(imported topic written by BenKus)
We have made a change in some Fixlet messages to remove “not pending restart” from the Fixlet relevance that I think will be beneficial to all.
You may have seen that some Fixlet messages contain “not pending restart” in their relevance, which was added because we were unable to determine whether files were updated until the restart occurred. You would see this in most “Corrupt Patch” Fixlets as well as some other Fixlets that had only file updates (and not registry key updates).
Many people commented that this behavior presented an annoyance because it caused the Fixlet to change relevance every time the computer needed a restart (even for unrelated reasons). Additionally, if you put these types of Fixlets in a baseline, they often wouldn’t run because the first Fixlet in the baseline would cause the computer to be in a pending restart state and the other Fixlets wouldn’t run until the restart.
BigFix has addressed this issue in this month’s patch release and going forward using a new feature called “named pending restarts”. Using this feature, future Fixlet messages that require a ‘not pending restart’ relevance check should no longer be affected by unrelated pending restarts of the computer.
The end result is that these Fixlets can be more easily incorporated into baselines and you will be able to easily figure out which Fixlets are relevant in the console.
Thanks to those that reported this issue and pressured us to make your lives easier and improve our product in the process.
Ben