NOTE: This update applies to version 10.12 and later.
For the 10.12 release, we updated six default health category thresholds that contribute to the SysTrack Health Score. These updates better reflect modern customer environments and the systems they run.
Updated Default Health Thresholds
The following table lists the updated default health thresholds and their new values.
Category | Metric | Old Value | New Value |
|---|---|---|---|
CPU | CPU Percentage | >95% | >90% |
Hardware | Hardware Interrupt Rate | >25% | >10% |
Latency | Latency Gateway | >5 ms | >75 ms |
Home Directory | >25 ms | >100 ms | |
Latency Sessions | >100 ms | >200 ms | |
Memory | Memory Available | <50,000,000 bytes | <20% |
Network | Network Retransmit Rate | >10% | >5% |
Network Utilization | >30% | >70% | |
Wi-Fi Signal Strength | Not applicable | <50% | |
Virtual Machine | Virtual Machine Ready Time | >10% | >5% |
Wi‑Fi Signal Strength Metric
With the increase in remote work and dynamic office environments, SysTrack now includes Wi‑Fi signal strength as a key system health metric.
Wi‑Fi signal strength is part of the Network health category. By default, Wi‑Fi impacts system health when signal strength falls below 50 percent. You can customize this threshold per role, consistent with other health thresholds.
Session Latency Update
Session latency for the ICA protocol now references RTT (round-trip time).
How This Change Affects Your Environment
After 10.12 is applied to your cloud environment, SysTrack applies the new thresholds to all agents.
Wi‑Fi signal strength affects health when it falls below the configured threshold. You can configure this threshold per role before updating agents.
Memory thresholds now use a percentage for 10.12+ agents and an absolute value for 10.11 and older agents.
Health scores reflect the new thresholds, which may change overall estate health and per-device health scores.
NOTE: Custom health thresholds assigned to roles and applied to configurations take precedence over new default thresholds and are not overwritten during upgrades.
Memory Threshold Behavior
In version 10.12, memory thresholds change from an absolute value to a percentage.
Scenario | Result |
|---|---|
Master and agent upgrade to 10.12, with no Available Memory configuration | The agent uses the new default memory percentage (<20%). |
Master and agent upgrade to 10.12, with an Available Memory configuration set in absolute bytes | The agent uses the new default memory percentage (<20%). |
Master upgrades to 10.12 and the agent remains on an earlier version, with no Available Memory configuration | The agent continues to use the absolute memory value. |
Master upgrades to 10.12 and agent remains on older version with Available Memory config for absolute (bytes) value set. | The agent continues to use the absolute memory value. |
Opt Out of the 10.12 Health Threshold Updates
If you do not want to use the updated thresholds in version 10.12:
Non-memory thresholds: Set custom values per role before the 10.12 rollout.
Memory thresholds: Customize Limit Memory Percentage, because Limit Memory does not preserve behavior for agents running version 10.12 or later.
To set custom threshold values per role, see Health.