Oliver Kieselbach
2e7172b6ab
The PR4 coordinator-pipeline tests drove adapter.TriggerEspExitingFromTest(), which only proves the adapter emit — it bypasses the coordinator's OnEspExited handler (where LastEventOccurredAtUtc mirroring + public EspExited re-raise live). A future regression that breaks the coordinator subscription, the LastEventOccurredAtUtc mirror, or the public EspExited fire would slip past. This commit adds a coordinator-level test seam mirroring the existing TriggerFinalizingSetupPhaseForTest pattern, and reroutes the wire-through tests through it. EspAndHelloTracker.TriggerEspExitedForTest: - internal seam (InternalsVisibleTo) that calls OnEspExited(this, args) - exact signature match to the live ShellCoreTracker.EspExited delegate - exercises LastEventOccurredAtUtc mirror + public EspExited invoke + finally reset — i.e. the full coordinator-side contract ShellCoreToEngineEspExitingTests: - Coordinator_EspExited_handler_re_raises_to_adapter_as_EspExiting_signal: asserts source-time preservation through the coordinator → adapter chain and that no clock-fallback "derivedTimestamp" evidence tag was added. - Coordinator_EspExited_handler_clears_LastEventOccurredAtUtc_after_re_raise: new defensive test for the finally-block reset; protects against a stale ShellCore timestamp bleeding into a subsequent Hello/Provisioning forward. - Coordinator_to_reducer_arms_HelloSafety_when_AccountSetup_observed: rewritten to use the coordinator seam; now asserts HelloSafety dueAtUtc == sourceTime + 300s (not Clock.UtcNow + 300s) so source-time threading is proven end-to-end (ShellCoreTracker → Coordinator → Adapter → Engine), not just adapter → engine. 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.