Oliver Kieselbach
bbcd5cedd4
Intune health-script detections (scriptType=remediation, scriptPart=detection/ post-detection) that report complianceResult=True, exitCode=0 were emitted as script_failed/Severity=Error whenever the detection PowerShell leaked a benign probe line to stderr (e.g. Get-ChildItem path-not-found). On green sessions this inflated errorCount (8 on a successful session) and ranked the rows #1 in search_events, diluting usage. Root cause: the hasStderr check short-circuited the failure decision before the existing isHealthComplianceReport exemption. Exit-code was already exempt for detection phases; stderr was not. The flawed rule was hand-duplicated in the agent emit and the web reducer, and propagated into MCP errorCount + ranking. Fix (verdict is authoritative for detection/post-detection phases): - Agent ImeLogTrackerAdapter.EmitScriptCompleted: fold hasStderr under !isHealthComplianceReport. Platform scripts, the remediation phase itself, and explicit result="Failed" still route to script_failed/Error. - Web reducer scriptExecutions.ts: same exemption (kept in sync). Non-compliant detections render amber via isNonCompliantReport, not red. - MCP read-side guard isBenignHealthDetectionReport() in tools/shared.ts, applied in search.ts severityIntentFactor (damp 0.6, no failure boost) and sessions.ts errorCount/keyEvents. Non-destructive; de-pollutes already-stored rows before the agent build rolls out per-enrollment. Tests: Agent 70 pass (retargeted enrichment test + new compliant-stderr regression), MCP search 61 pass (helper + ranker damp), Web reducer 66 pass (flipped detection-stderr case). MCP + Web tsc clean. Co-Authored-By: Claude Opus 4.8 (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.