Oliver Kieselbach
ea4bb1c8ef
The OfficeInstallDetector state was in-memory only, so every agent restart (an enrollment spans several reboots) re-armed the detector from Idle and all three start triggers fired falsely on an already-installed Office: Scenario\INSTALL persists post-install, OfficeC2RClient.exe runs again for update checks, and Office updates stream from the same CDN. Each restart then emitted a duplicate started+completed pair (~0s duration) via the binary watcher's initial scan; a mid-install reboot also reset the start time. New OfficeInstallStatePersistence (office-install-state.json in the state directory, fail-soft, atomic write) carries the lifecycle: - persisted terminal (Completed/Failed) -> the factory does not arm the detector at all on the next run (no WMI/RegNotify watchers) - persisted Active -> the host resumes the open lifecycle without a second started; a completion proven in this run reports the true total duration plus the persisted DO peak as doSummary (also catches completions missed across a mid-install reboot) - AbandonSilently deliberately does NOT persist a terminal: it fires on every dispose and would block that resume - DO peak growth re-persists throttled (30s) while Active V2.Core tests 1383/1383 green (14 new); V2 runtime builds clean. No ConfigVersion bump (no new remote setting); inert until redeploy. Co-Authored-By: Claude Fable 5 <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.