Oliver Kieselbach ae330f54d9 fix(v2): 882fef64 PR4 — Hello policy → DecisionEngine + 10s grace + mismatch detector
Surface the WHfB / Hello-for-Business policy fact to the decision engine and use
it to drive the post-ESP-exit Hello wait cadence. Policy=enabled keeps the 30s
default; policy=disabled shortens to 10s as a sanity check against a buggy
detector. A `hello_policy_detection_mismatch` Warning event fires when a Hello
terminal arrives despite policy=disabled — that is the detector-bug indicator.

The completion-gate is intentionally left untouched: completion is orthogonal to
Hello status (the Hello+Desktop AND-gate already accepts any terminal Hello
outcome). A feedback memory is saved so a future iteration doesn't re-add a
completion guard on this fact.

Foundation:
- DecisionSignalKind.HelloPolicyDetected (v1)
- SignalPayloadKeys.HelloEnabled / HelloPolicySource
- DecisionState.HelloPolicyEnabled : SignalFact<bool>? (null = unknown)
- DecisionStateBuilder.WithHelloPolicyEnabled fluent helper
- HandleHelloPolicyDetectedV1 reducer (set-once, no-op on same value, update on
  different value, DeadEnd on missing/unparseable payload)

Behavior:
- HelloTracker.HelloWaitTimeoutDisabledSeconds = 10
- StartHelloWaitTimer picks 10s when policy explicitly disabled, 30s otherwise
- HelloTracker.HelloPolicyDetected event re-raised through EspAndHelloTracker
- EspAndHelloTrackerAdapter posts HelloPolicyDetected signal once per session
- EmitHelloPolicyDetectionMismatch on Hello-terminal arrival under policy=disabled
  (wired into both ProcessHelloEvent and ProcessHelloForBusinessEvent paths)

Tests: DecisionCore 231 (+11), V2.Core 727 (+11), Functions 736, vitest 179,
solution build 0/0.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-25 18:54:38 +02:00
2026-04-22 19:36:19 +02:00
2026-03-17 18:24:01 +01:00
2026-03-26 07:02:33 +01:00
2026-04-04 19:17:01 +02:00

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.

S
Description
Windows Autopilot & Intune enrollment monitoring: live session timelines, fleet health, diagnostics, and an MCP server for AI-assisted troubleshooting.
Readme AGPL-3.0 60 MiB
Languages
C# 72.7%
TypeScript 25.7%
PowerShell 1%
JavaScript 0.5%