Skip to content

Monitoring, telemetry and update management

These are the agent’s newest capabilities and the least visible ones. Everything here runs quietly on the device and surfaces in the control panel, so it is worth knowing what is being collected — not least because customers ask.

DEX monitoring watches the Windows event log for conditions that indicate a user is having a bad time — crashes, hangs, failures that never reach the helpdesk because people work around them.

The agent subscribes to event-log channels and matches events against rules issued from the control panel. A rule identifies events by publisher and severity, not by event ID alone: the same numeric ID means different things in different Windows components, so matching on the ID by itself would produce false positives.

Matched events are buffered on the device and sent in batches over the device’s IoT connection.

The buffer holds up to 5,000 events, batches are capped at 200 events or roughly 200 KB, and the agent backfills up to seven days of history when monitoring first starts — so a newly enrolled device arrives with recent context rather than nothing.

The device records when it last synchronized DEX data, which is the value to check if a device looks quiet.

Separate from DEX, general telemetry can be enabled or disabled per device, with a configurable batch size. When disabled, the agent stops sending it.

What else the agent reports about a device:

  • Hardware and warranty — warranty lookup, where enabled
  • Location — geolocation, where enabled
  • Network — the device’s external IPv4 and IPv6 addresses
  • Compatibility — Windows 11 readiness
  • Security posture — BitLocker key escrow state, Windows Autopilot registration, Intune ownership classification

Geolocation, warranty lookup and telemetry each have their own switch. If a customer objects to a specific collection, it can be turned off without disabling management.

The agent tracks update health rather than just installing updates, and records:

  • current health status and when it was last checked
  • whether remediation has already been attempted
  • the last error encountered
  • which updates last failed
  • whether a reboot is pending after an update
  • when the last automatic scan ran

This distinguishes the three cases that matter: a device that is up to date, a device that is behind, and a device whose update stack is broken and will stay behind until something repairs it. The remediate Windows update command exists for the third case.

When a device is behind on updates, the agent can notify the person using it — not just report to the panel. They see:

Updates Required — Your machine is missing critical updates. Click here to initiate Windows Updates now.

Clicking it starts the installation immediately, the same operation as the panel’s install-updates command. Once running, the user sees a second message confirming updates are in progress.

The agent records when it last showed this prompt, so the same user is not nagged repeatedly about the same condition.

Applications are updated through Windows Package Manager. The agent runs the update via a scheduled task with elevation, so it works whether or not anyone is signed in. Behaviour is configured at the organization level and can be triggered on demand with the run winget updates command.

This covers applications the package manager knows about — it is not a substitute for a deployment tool for line-of-business software.

Disk cleanup can be run on demand. It is worth knowing about ahead of an Entra ID migration: insufficient free space is one of the preflight checks that will block one, because the user’s profile is copied before it is moved.