Oliver Kieselbach
27612db560
Today's RJ doesn't populate the DisplayName registry value for most package subkeys (only ArgsHash / Success / LastExitCode / Version / Type are written — confirmed on generic-vlc and generic-gkgab-set-wallpaper-preference). The old MaybeFirePackageEvents gated the started signal on snap.HasStartedMarker (= DisplayName non-empty), so realmjoin_package_started never fired for these packages and only realmjoin_package_completed landed with an empty DisplayName slot. Change: drop the HasStartedMarker guard from the started branch. The first observation of a new <packageId> sub-key is itself the started signal, period. DisplayName stays in the payload + message as a passthrough field — empty when RJ didn't advertise a name (useful "RJ didn't write it" indicator on the wire) and populated automatically when a future RJ version starts writing it at install-start. Completed semantics unchanged (still gated on Success + LastExitCode presence). Behavior for pre-existing/already-completed packages observed on agent boot: a single MaybeFirePackageEvents pass now fires BOTH started AND completed (started first), so the timeline reflects the full lifecycle even when we missed the live transition. Tests: +2 watcher tests via the new TriggerMachinePackageObservationFromTest seam — "fires started even without DisplayName" + "fires both started and completed for pre-existing snapshot with completion markers". 10/10 adapter suite green. 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.