Oliver Kieselbach
11fc0560fc
Platform scripts already report a per-script run duration (StartedAtUtc captured at the start line -> durationSeconds on script_completed). This extends the same timing to proactive-remediation (health) scripts. The adapter's duration block is type-agnostic; it just needs StartedAtUtc on the emitted state. Remediation phase events are built from the [HS] new result JSON, which carries no timestamps, so the cycle start is captured from the HS-SCRIPT-START line into a dedicated per-policy map (_pendingHealthScript is cleared by the early-signal HS-COMPLIANCE handler before the result arrives) and stamped on every phase event when HS-NEW-RESULT is parsed. Duration is the whole-cycle runtime (detection + remediation + post-detection) since IME provides no per-phase timestamps. Null when the start line was never seen (replay) -> omitted. Web lifts the cycle duration onto the ScriptCard and shows it once on the card header rather than repeating the same value on each nested phase row; detect-only single-phase cards keep showing it on their row. V2-only. Tests: 2 agent timing tests (with/without observed start), 3 web card-duration tests. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Autopilot Monitor
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.