Oliver Kieselbach c23dc9a329 fix(agent-v2): console-bypass watcher hardening (L12, L13, L14, L15, L20)
Delta-review 2026-07-02 findings:
- L12: `cmd /k` leaves a fully interactive shell after running its command —
  it was classified as a scripted invocation and silently ignored (deliberate
  false-negative seam, e.g. a technician-planted `cmd /k whoami`). Now
  surfaced as low-confidence `interactive_console_with_command`; only /c
  (run-and-exit) is ignored.
- L13: the WMI trace arm + startup probe ran synchronously in the
  orchestrator`s sequential host-start loop; a WinMgmt hang (documented OOBE
  failure mode) delayed every later host. Both now run on a background
  thread, with a dispose-race guard around the watcher arm.
- L14: the desktop-arrival callback was the ONLY stop path — if the DAD never
  validated a real-user owner, the watcher flagged ordinary post-desktop user
  consoles for the agent`s whole remaining lifetime. Fallback: the host also
  stops on a DesktopArrived or HelloResolved signal on the decision rail.
- L15: wtsErrorCount counted the routine "session has no logged-on user yet"
  OOBE case as an error; ProcessOwnerLookup.ViaWts now reports real API
  failures separately and only those are counted.
- L20: WatchedProcessNames is now actually the single seam — WQL trace
  filter, startup probe and the emitted processName are all built from it.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-03 11:03:47 +02:00
2026-06-13 16:10:14 +02:00
2026-03-26 07:02:33 +01:00
2026-05-07 08:51:22 +02:00

Autopilot Monitor

Status License Website

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%