If an Active Directory Health Agent becomes temporarily unreachable from the ADS server, it may rapidly transition from OK to Warning and then Critical status. Before Active Administrator 8.9, this escalation could occur within minutes, ultimately resulting in the ADS server restarting the Active Directory Health Agent.
In these scenarios, the agent may still be able to communicate with the ADS server and send data points even though the ADS server cannot successfully reach the agent. This behavior is not uncommon in cases of DNS resolution issues or temporary network latency spikes.
The predefined time thresholds before the Active Directory Health Agent transitions to Warning and Critical states were increased. When the agent enters a Critical state, it is automatically restarted.
This change allows Active Administrator administrators to define the time thresholds at which Active Directory Health Agents transition to Warning and Critical states. These settings are not configurable through the GUI and must be set in the registry using the following values:
Registry path:
HKEY_LOCAL_MACHINE\SOFTWARE\Quest\Active Administrator\Settings\ADS
Registry values:
DAAgentHeartbeatWarningThreshold
DAAgentHeartbeatCriticalThreshold
Both values are of type REG_SZ, either be specified as an integer (representing this number of minutes) or as a timespan (in the format "days.hours:minutes:seconds").
NOTE: Agent status is evaluated every three minutes. Threshold values shorter than this interval are not recommended. For best results, configure Warning and Critical thresholds as multiples of this interval.
