Know when a device last reported

Accepted check-ins establish connectivity. Never-reported devices remain Waiting, while previously reporting devices can become Offline when check-ins stop. That separation prevents an unfinished enrollment from masquerading as a diagnosed outage.

Look behind the current reading

CPU, memory and system-disk graphs cover one hour, twenty-four hours or seven days. Longer ranges use averages, and missing samples remain gaps. Basic inventory adds OS, hostname, architecture, CPU count, total memory and last boot where reported.

This is host-wide monitoring, not a process profiler or a complete software inventory. System-disk reporting does not cover every attached volume.

Plan with update visibility

The Updates view shows available OS updates from each platform's configured source, reboot observations where supported and report freshness. macOS reboot requirement remains Unknown. A failed query is not presented as zero updates.

Reporting does not install patches or reboot devices. Understand monitoring versus patch deployment before comparing that capability with a broader management tool.

Use the next useful check

When a device is offline, investigate check-ins before trusting its old service state. When it is online but users have trouble, inspect current service observations and local application diagnostics.

Read device status and history or follow the offline diagnosis guide.