Has anyone experienced an issue where properties are not being shown with accurate values in the BigFix Console? I am experiencing a growing problem where important properties that have been confirmed via local on-box inspection to be of one value are not reflecting that value in the BigFix Console - even after long periods of time have passed (days) without connectivity interruptions.
The inaccurate propery issue is causing operational problems for processes that rely on these values. I have openeded a support case already and have been told I need to upgrade to 7.2.4.60 (curretnly on 7.2.1.357). While I can appreciate the notion of upgrading, I do have the luxury of upgrading on a whim without proper testing and QA.
Are there any workarounds or actions I can take in the meantime to resolve the inaccurate property issue?
It would help to dig into the specifics of your case, including:
Is the relevance for your properties returning invalid results when you run QnA on the computer?
Which properties and their relevance?
If QnA returns the expected results but they aren’t reflected in the console, then there are several things we can ask you to do and check to figure out why that would be.
General troubleshooting for these types of issues includes:
Verifying the relevance results on the computer using QnA to determine if the problem is the relevance being used or the console reflecting state accurately.
Reloading the BES Console cache (or disabling it entirely).
Sending the Client a ‘force refresh’ request by right-clicking it in the console.
Checking the retrieved property’s evaluation interval through Tools->Manage Properties in the BES Console.