Oliver Kieselbach
049b6e5b4a
The timeout classifier only read the ESP registry rollup, so a session where the user reached the desktop and completed Windows Hello — with only the RealmJoin completion gate still pending when the agent went silent — was labeled AwaitingUser (and would have graduated to Incomplete at grace expiry). Desktop arrival + a positive Hello terminal are the agent's own Classic completion AND-gate; the RJ gate self-releases after 60 min, so such a session's enrollment succeeded and only the completion report never left the device. - EnrollmentTimeoutClassifier: rollup now carries DesktopArrived, HelloResolved (hello_provisioning_completed/hello_skipped only) and RealmJoinDetected/Resolved (realmjoin_resolved/realmjoin_timeout); new rule 4 reconciles desktop+Hello sessions to Succeeded with an RJ-aware reason. Explicit failure and agent_emergency_break still win. - FailureSnapshotBuilder: schema v3 embeds the new evidence (helloResolved, realmJoinDetected, realmJoinResolved). - Web FailureSnapshotBlock: renders Hello completed + RealmJoin rows. - Design doc: decision table updated; desktop_arrived ALONE stays rejected as a completion signal. 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.