Oliver Kieselbach
5a858cb4c5
Plan §2.1a / §2.2 — 3 erste SignalAdapter pro Collector. Sub-Split analog M3.x. New in V2.Core.SignalAdapters: - DesktopArrivalDetectorAdapter → DesktopArrived / DesktopArrivedPart2 - AadJoinWatcherAdapter → AadUserJoinedLate / UserAadSignInComplete (nur AadUserJoined-Event gemapped; PlaceholderUserDetected ist diagnostic, nicht Decision-relevant — dokumentiert) - HelloTrackerAdapter → HelloResolved / HelloResolvedPart2 (payload trägt HelloOutcome: completed|skipped|timeout|not_configured|wizard_not_started) Adapter-Pattern: - internal sealed class : IDisposable - Ctor: Collector + ISignalIngressSink + IClock + optional part2Mode - Subscribe auf Collector-Event; dedup-Flag (fire-once) - TriggerFromTest() internal hook für Tests (umgeht Event-Plumbing) - Dispose() unsubscribed - Keine Modifikation der Collector-Files (§2.11 transitional-SKIP bleibt) PII-Guard in AAD-Adapter: nur userDomain im Payload, nicht full email. New tests (+21, 95 total V2.Core.Tests): - Trigger → Post mit korrektem Kind/Evidence/Payload - part2Mode → Part-2-Signal-Kinds - Duplicate-Trigger → Dedup - Null-Args → ArgumentNullException - HelloOutcome-Varianten (Theory, 5 values) - AAD PII-Guard (full email NICHT in payload) Pattern-Erkenntnisse: - Collectors sind meist internal — Adapter sind auch internal (InternalsVisibleTo Agent.V2 + V2.Core.Tests deckt Usage) - Evidence.Derived braucht mind. einen DerivationInput — Adapter setzen sinnvolle Detection-Source-Keys - Part-1/Part-2 via bool-Ctor-Param (einfacher als 2 Klassen) Testsuite: 1195 → 1216. V2-isolation clean. 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.