Oliver Kieselbach
6344a8b061
Surface "how many reboots did this enrollment have" as a stored, filterable per-session metric so admins can ask e.g. "machines with many reboots" via MCP search_sessions. No agent change: V2 already emits one system_reboot_detected per reboot (EventLog 6009 boot-time vs session start). The backend counts and stores it; V1 stays 0 (never emits it). Hybrid counting: - Incremental per ingest batch in ClassifyEvents (V2 + legacy V1, shared EventClassification) -> rebootIncrement on IncrementSessionEventCountAsync, for a live in-flight value (passed 0 on terminal batches). - Authoritative reconcile (ReconcileSessionRebootCountAsync): distinct count of system_reboot_detected from the Events table, idempotent + fail-soft. Runs centrally in TableSessionRepository.UpdateSessionStatusAsync after any successful terminal transition (ingest, admin mark, maintenance timeout, rule-engine fail), and again post-increment in the ingest path to cover already-terminal batch replays. Self-corrects at-least-once batch double-counts. Storage/correctness: - RebootCount preserved across re-registration in StoreSessionAsync (a reboot IS the restart trigger) and projected in BuildSessionIndexEntity (superset rule). Search/MCP: - rebootCountMin/Max pushed to OData in BuildSearchScanFilter (sparse-subset), decoded in SearchSessionsFunction + QueryRawSessionsFunction, added to the continuation fingerprint and the fields= projection. Client-side MatchesRebootCountBounds backstops the device-snapshot + legacy scan paths. - search_sessions MCP tool gets rebootCountMin/Max + rebootCount projection. Tests: SessionIndexProjection (superset), StoreSessionReregistrationPreserve, RebootCountFilterBounds. Suite 2228/2228 green; MCP 220 green. Inert until backend redeploy; legacy index rows lack the column until next upsert (excluded by min-filter, intended). Web UI badge deferred. 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.