Oliver Kieselbach
9e81e9b74e
Several MCP search tools could return count:0 together with a nextLink on the first page while real matches sat on later pages (in-memory post-filters run after a single Azure-table page fetch). Callers stopped at the empty page and wrongly concluded "no results". Invalid eventType / deviceProperties keys produced the same count:0, so a bad filter was indistinguishable from a miss. - Add scanUntilMatch (client.ts): scans forward while a page is empty until it finds matches, drains, or hits a bounded budget (maxPages/wallClockMs). Emits an honest moreToScan + recallNote at the budget boundary and always adds scannedPages. The three end states are now distinguishable: matches found (nextLink = more pages), truly empty (count:0, no nextLink), budget-bounded (count:0 + nextLink + moreToScan). Pages map 1:1 to backend boundaries. - Wire into search_sessions, get_session_events, query_raw_events. Leave search_sessions_by_event / query_raw_sessions on single-fetch (server-side OData filters can't produce empty-but-continuable pages). - Add catalog validators (resource-catalog.ts): assertKnownEventType against the drift-tested ALL_EVENT_TYPES, and assertKnownDevicePropertyKeys (prefix-only, so valid-but-uncatalogued sub-properties aren't blocked). - Update tool descriptions; drop the now-wrong "keep scanning yourself" comment. - Tests: auto-exhaust.test.ts (13 cases) covering scan/drain/budget paths and all validators. 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.