Background - We have a custom Fixlet that has been around for about a year. It was deployed successfully as planned over 6 months ago to about 2000 relevant devices. However, when checking the content in web reports, The “Time Remediated” dates seem to be updating to the last couple of days for many systems. There is no open action for this fixlet and no action history in the last 6 months. Has anyone seen this type of behavior?
I am curious what this fixlet does and what the relevance is.
time remediated doesn’t have to do with actions, it has to do with it becoming relevant, then non relevant. There is also last became non relevant, last became relevant, and is it relevant now. I look to all 4 values to try to understand what is happening.
For instance, if you have a fixlet that has relevance for firefox not being updated to the most recent version, it will become remediated if firefox auto updates not by bigfix action. It will become unremediated by reinstalling firefox at an older version. It will become remediated again if patched by bigfix.
1 Like
This fixlet is looking for a couple of reg keys for a specific user. I am thinking there must be a reason outside of BigFix that is causing the relevance to change… perhaps only briefly. Enough to show in Web Reports, but not long enough to show in the console. We’ll take a look at the other values to see what is going on. Thanks for the suggestion JG
1 Like
If it's based on a specific users' registry value, it may well toggle to non-relevant when the user logs off and their registry hive is unmounted by Windows.
2 Likes