We appear to have more and more of the following issue. Patches will show they are applicable for a PC but when you distribute the patch to the device, it comes back as not relevant, and it will still show that the patch is applicable for that PC in the BigFix Console. The PCs all have the current client, 7.2.1.357 and appear to be reporting on a regular basis (not greyed out).
We have done the following to try to fix it:
Force a refresh of the PC using Notify Client Refresh task. This works sometimes.
Stop the BES Service, remove the _BESData folder and restart the device. This works sometimes.
Stop the BES Service, uninstall the BES client, restart the PC and reinstall the BES client. This works most of the time.
Is there something else we should be doing to get these devices to report accurately? This can be really time-consuming, when we have to stop and troubleshoot each specific device that won’t update. We have over 10K devices and do not have the resources to do this type of troubleshooting. =(
Yes, the problem persists after clearing the cache. And it exists on more than one console. The only thing that appears to work consistently is uninstalling and reinstalling the BigFix client. As I said, we are getting more and more of these, especially with laptops that are not regularly on the network. Any other ideas? Thanks.
Having a similar issue where all the fixlets from 4/12/2011 are showing not relevant to any computer, however, when I run the debugger and evaluate each piece of relevance, they each show as TRUE, meaning the workstation needs the fixlet.
I’ve refreshed the console cache, i’ve restarted every BES service on the server and the workstation. I’ve rebooted the server, and the workstation. I’ve deleted on the workstation the __BESDATA folder, and allowed it to recreate and download all the content again.
We are also having same issue, windows patches are showing applicable for endpoints but when we distribute patches through baseline, showing not applicable.BES client version is 8.2.1175.0.