Oliver Kieselbach
c649d80c86
The agent read device hardware twice: once at startup via HardwareInfo (feeds the security headers + telemetry) and again at registration via DeviceInfoProvider (feeds the Sessions row). When WMI was transiently unavailable during OOBE, the body read returned "Unknown" while the header read had already captured real values — producing session rows with Manufacturer/Model/SerialNumber = "Unknown" even though the backend validated (and passed) real values from the headers. - HardwareInfo.GetHardwareInfo: retry once (~1.5s) when any field is still unresolved, per-field merge across attempts, and isolate each WMI query so a BIOS-serial failure no longer discards manufacturer/model. Healthy devices resolve on attempt 1 and never sleep. - SessionRegistrationHelper.BuildRegistration: accept the already-read hardware tuple and use it instead of re-querying WMI (falls back to DeviceInfoProvider only when none supplied, e.g. unit tests). - BackendSessionRegistration: pass the auth bundle's hardware through so the session row matches the headers the backend validated against. Net: one hardened WMI read instead of two, and the Sessions row can no longer diverge from the security headers. Co-Authored-By: Claude Opus 4.8 (1M context) <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.