Oliver Kieselbach cd6dfe7c3c feat(office): render Office as an install row + fix started/completed ordering
UI — Office in Install Progress:
- The office_install_* lifecycle now renders in the existing InstallProgress
  card as a first-class install row (live elapsed timer while installing +
  final duration). page.tsx feeds office_install_started/completed/failed into
  the component; InstallProgress maps them onto the same Installing/Installed/
  Failed flow via isStarted/isCompleted/isFailed (Office has no postponed/
  skipped; appName "Microsoft 365 Apps").

Fix — completed-before-started (field session a7525e97, Office CSP / Win32
wrapper):
- When Office is already on disk as the C2R worker runs (CSP install / a Win32
  package that re-runs C2R), the host's OfficeBinaryWatcher initial scan
  completes the lifecycle synchronously. BeginIfIdle armed that watcher (via
  ObserveInstallationPath) BEFORE emitting started, so completed was emitted
  first. Reorder: emit started, then observe the path — guaranteed started ->
  completed ordering. Start is still gated by real evidence (process / registry
  Scenario\INSTALL / DO job); only the emit order changed.
- InstallProgress defensive guard: a late started on an already-Installed item
  backfills startedAt and recomputes durationMs instead of dropping it, so
  out-of-order / network-reordered delivery still yields a correct duration.

V2-only + web. ConfigVersion unchanged. V2.Core 1264/1264, web 452/452, tsc clean.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-09 10:11:44 +02:00
2026-03-17 18:24:01 +01: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%