Oliver Kieselbach
b5508965b6
The Succeeded reconcile hygiene (c0585133) clears FailureReason/FailureSnapshotJson on every Succeeded write, so a sweep-reconciled session (049b6e5b, session 294ab5b4) was indistinguishable from an agent-reported completion. Operators must always be able to tell whether WE declared a status or the device reported it. - New Sessions column ReconcileReason, set only for backend-automatic Succeeded verdicts: the maintenance sweep's classifier reason is persisted verbatim; a reason-less late completion upgrading a prior Failed/Incomplete/AwaitingUser verdict synthesizes "Late completion report received — upgraded prior '<Status>' verdict". - Admin flips stay attributed via AdminMarkedAction (no double badge); normal agent completions leave the field empty. Pure ComputeReconcileReason next to IsTerminalTransitionAllowed, pinned by 17 new facts. - Survives re-registration (StoreSessionAsync preserve + fresh-terminal-tuple mirror) and StartedAt-shift reindex (SessionsIndex projection); force-merge path mirrors the normal path against the FRESH prior status. - Web: "reconciled" chip in SessionStatusBadge (tooltip = justification) + info box on the session detail page; dashboard list passes the field through. - MCP: get_session_summary overview carries reconcileReason. Backend 2907/2907, web tsc + vitest 557/557, MCP 393 pass. 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.