Oliver Kieselbach
7afa03aaf1
Remediation rows showed "8m" for scripts that ran seconds: durationSeconds was measured HS-SCRIPT-START -> HS-NEW-RESULT, and IME writes that line only after its batched service report. The early-signal (HS-COMPLIANCE) completion carried no duration at all because it never read the cycle-start map. Agent: - HS-COMPLIANCE early-signal completions now PEEK _healthScriptStartTimes and emit the actual run time (durationBasis=script_runtime); HS-NEW-RESULT keeps consuming the entry and stamps its phases cycle_including_reporting_latency. - durationBasis now comes from the emitting handler (ScriptExecutionState. DurationBasis) instead of pauschal per scriptType. - Platform scripts emit the live script_started signal too (gated on pending- slot creation so the duplicate agentexecutor+ime start line stays one signal). Web: - Reducer normalizes durationBasis: runtime -> durationSeconds, cycle -> reportedAfterSeconds (legacy events without basis infer from scriptType, so old remediation cycle values are never displayed as run time again). - Dedupe merges both timings across the early/late emissions instead of dropping the runtime when the more complete HS-NEW-RESULT entry wins. - Card run time = max of phase runtimes; "Reported after Xm" shown in the expanded Details strip (per UX decision), never on the compact row. Inert for new events until agent redeploy; web deploy alone already fixes the misleading display of stored data. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
AutopilotMonitor
Advanced monitoring and troubleshooting solution for Windows Autopilot deployments. Gain full visibility into every enrollment session with a detailed event timeline, fleet health dashboards, and session reporting. Define custom analysis rules to automatically detect issues and gather rules to collect targeted evidence. Retrieve diagnostics packages on demand, configure agent settings like auto-reboot behavior and automatic timezone adjustment — all managed centrally from the web dashboard.
Private Preview
Autopilot Monitor is currently running as a Private Preview. Visit autopilotmonitor.com to request access and learn more.
Overview
Autopilot Monitor provides real-time tracking, intelligent diagnostics, and automated troubleshooting for Windows Autopilot enrollment processes. It consists of:
- Bootstrap Script — PowerShell script deployed via Intune that starts monitoring early in the enrollment process
- Monitoring Agent — Lightweight .NET application that collects telemetry and evidence during enrollment
- Backend API — Azure Functions-based ingestion and processing pipeline
- Web Dashboard — Next.js application for real-time monitoring and fleet analytics
Architecture
For detailed information about the system architecture, components, and data flow, see Architecture Documentation.
Documentation
Full documentation is available at autopilotmonitor.com/docs
License
This project uses a split licensing model:
- MIT License — Agent (
src/Agent/) and Shared library (src/Shared/) — unrestricted use on end-user devices - AGPL-3.0 — Backend (
src/Backend/), Web Dashboard (src/Web/), and MCP Server (src/McpServer/) — server-side components remain open source
See LICENSE for full details.