The current Inactive Devices dashboard lists historical agent sessions (agent + IP combinations) rather than a true deduplicated device view. This creates misleading data and operational overhead because: IP churn (DHCP/VPN) results in multiple entries for the same device. Old IP contexts remain indefinitely; there is no auto-purge or refresh mechanism. Dashboard logic relies solely on Huntress agent heartbeat, ignoring other health signals such as Microsoft Defender for Endpoint (MDE) sensor status or Intune compliance. No option to customize inactivity thresholds or automatically delete stale records. Using this dashboard as a trigger for remediation could lead to false positives and unnecessary workload. Example: Device BLM-PC10Y482 appeared two times in the dashboard with different internal IPs (192.168.87.232, 192.168.87.162), even though the agent was healthy and active.