Registry reads now go through RegistryKey.OpenBaseKey(.., Registry64) explicitly. SDK-style net48 EXEs can resolve AnyCPU to 32-bit at runtime depending on MSBuild defaults; in that case HKLM\SOFTWARE\Microsoft\Enrollments redirects to the WOW6432Node mirror, a different (and usually stale/empty) hive that never carries the active MDM enrollment. Forcing Registry64 makes the resolver bitness-independent regardless of how AnyCPU resolves. Diagnostic-on-miss is now compact: * Sub-keys without an EnrollmentType value (Context, Ownership, Status, ValidNodePaths) are recognized as structural and skipped silently. * The detail list contains only Type=6 (Intune MDM) entries with their EnrollmentState and AADTenantID presence — that's the only enrollment flavor that ever carries the TenantId. * Non-Type-6 enrollments collapse into a single counter so a heavily enrolled device (e.g. dev box with 30+ historical enrollments) no longer floods the agent log with one Warning per sub-key. Mirrored across the V1 + V2 resolver shipped in99ec2517/fc950757. Co-Authored-By: Claude Opus 4.7 (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.



