Known issues and limitations
These are the known issues and limitations in BigFix DEX.
- The client
setting _BESClient_Resource_AccelerateForPendingMessagemust be set to '0' on every DEX client. - The BigFix Scanner DEX Plugin being uninstalled and then reinstalled can cause the score to go below '0'.
- In the presence of persistent anomalies that continuously produce a score of 0 (for
example, a partition free space constantly below the critical threshold), the
reported anomaly count may differ depending on the aggregation
window.
Specifically:
When the aggregation window is ≥ 1 day (i.e., total time range ≥ 7 days), the anomaly count reported for the last 24 hours can differ from the anomaly count reported when the aggregation window is < 1 day (i.e., total time range < 7 days) for the same last 24-hour timeframe. This leads to inconsistent anomaly counts for the same period based solely on the selected aggregation window.
- Some inventory parameters might be shown as '0' on macOS.
- On macOS endpoints, Event collection in macOS is heavily dependent on the Unified Logging System of the OS and its related performances. Due to this, at startup on slower platforms some events might be not reported due to the time taken to report or the additional action taken by the user to restart before our agent was able to collect the event.
- Out-of-the-box reports are owned by the first user who logs into the BigFix UI, and who can then reconfigure them and change their visibility. This limitation will be removed in the next release, making them read-only.
