Skip to main content

Agent Installation

Agent Installation (page header reads Agent Installation Analytics) is the device fleet dashboard — the place to verify that the SWA agent is healthy across every device. It surfaces high-level fleet counts and a per-device table with hostname, OS, agent version, status, last heartbeat, and last activity timestamps.

Summary Tiles​

  • Total Devices — All devices ever registered with SWA
  • Active Agents — Devices that have reported in within the configured liveness window
  • Stuck (no data 24h+) — Devices that are technically active but have not produced new activity for over 24 hours — usually a sign the agent process is running but blocked
  • Inactive Agents — Devices that have stopped reporting beyond the liveness window
  • Agent Versions — Distinct agent versions in the fleet (lower is better — uniformity is the goal)

Device Agent Status​

A sortable, paginated table:

ColumnDescription
Device UUIDStable device identifier (e.g. ILDPILABXP285)
User NameMapped employee, or Unassigned
HostnameDevice hostname
OSOperating system (e.g. Windows 11)
Agent VersionInstalled agent build (e.g. 6.0)
StatusActive / Inactive
Last HeartbeatTimestamp of the last keep-alive ping from the agent process
Last ActivityTimestamp of the last actual captured activity (foreground change, keystroke, click)

Use the search field above the table to find a specific device or user. Click any column header to sort.

Mapping Unassigned Devices​

If a device shows Unassigned in the User Name column, its activity will not appear under any user's analytics. Map it via Device Setup or set up an automatic mapping with Connectors.

Best Practices​

  • Watch Inactive Agents daily — anything more than a single-digit percentage of the fleet warrants investigation. Common causes: device offline for PTO, device reimaged without SWA, or an agent crash.
  • The Stuck (no data 24h+) tile is the early-warning signal — a stuck agent will still appear in Active Agents because heartbeats are flowing, but no real activity is being captured. Drill into the device row and compare Last Heartbeat vs Last Activity — a large gap confirms the diagnosis.
  • Keep Agent Versions to one or two versions at most — multiple older versions complicate troubleshooting.
  • Decommission stale devices via Device Setup → Block so they no longer count against Total Devices.
  • A jump in Total Devices without a matching jump in Active Agents usually means a deployment finished installing but devices haven't booted yet.