Oliver Kieselbach
389426f8f2
ResolveOccurredAt rejected a source timestamp when ageHours < -1.0. That bound could not fire for the single most common timezone error: with a one-hour offset mistake the real value is parseLag - 3600 s, i.e. just ABOVE -1.0. It sat exactly on the boundary of the case it was meant to catch, which is why every skewed session sailed past it. It was asymmetric too — a past-shifted error had to exceed 24 h before anything noticed, while the measured field errors reached -17 h. The bound is now derived rather than guessed: writer and reader share one system clock, and the tracker only sees a line after it was written, so a correctly converted source timestamp is always at or behind "now". Anything ahead means the conversion was wrong. MaxFutureSourceSkew is 2 minutes of jitter tolerance — deliberately far below the hour a timezone mistake produces. The rejection log now names which bound tripped and by how much, instead of printing a bare ageHours that reads the same for both directions. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
AutopilotMonitor
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.
Availability
Autopilot Monitor is publicly available — the Community plan is free. Sign in with your work account at autopilotmonitor.com; new organizations complete a short activation step after first sign-in.
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 admin documentation is available at docs.autopilotmonitor.com
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.