From b53e992f254853479b09f2b66b18b33bf2a40ade Mon Sep 17 00:00:00 2001 From: Oliver Kieselbach Date: Fri, 3 Apr 2026 14:41:41 +0200 Subject: [PATCH] add full enrollment timeline docs section explaining IME log backfill Co-Authored-By: Claude Opus 4.6 (1M context) --- .../app/docs/sections/SectionAgent.tsx | 50 +++++++++++++++++++ 1 file changed, 50 insertions(+) diff --git a/src/Web/autopilot-monitor-web/app/docs/sections/SectionAgent.tsx b/src/Web/autopilot-monitor-web/app/docs/sections/SectionAgent.tsx index bd7faf56..3a4517f8 100644 --- a/src/Web/autopilot-monitor-web/app/docs/sections/SectionAgent.tsx +++ b/src/Web/autopilot-monitor-web/app/docs/sections/SectionAgent.tsx @@ -52,6 +52,56 @@ export function SectionAgent() { the backend for live monitoring and analysis.

+
+
+ + + +

Full Enrollment Timeline — From the Very First Second

+
+

+ Although the agent arrives on the device via the bootstrapper script — typically a few minutes after + MDM enrollment begins — it does not miss any earlier activity. The Intune Management Extension (IME) + has been writing detailed log files from the very start of enrollment, and the agent reads those logs + from the beginning on its first launch. This backfill mechanism ensures complete coverage of the entire + enrollment timeline, with no blind spots. +

+
+
+ 1 +
+ IME logs from the start:{" "} + The Intune Management Extension begins logging immediately when enrollment starts — long before + the agent exists on the device. App downloads, installations, ESP phase transitions, and policy + processing are all recorded into CMTrace-formatted log files on disk. +
+
+
+ 2 +
+ Backfill on first launch:{" "} + When the agent starts for the first time, it reads the IME log files from byte position zero. Every + historical entry — app state changes, phase transitions, download progress, script executions — is + parsed and processed as if the agent had been running the whole time. Archived (rotated) log files + are included and processed before the current log to preserve chronological order. +
+
+
+ 3 +
+ Real-time from there:{" "} + After the initial backfill completes, the agent switches to incremental polling. It tracks the byte + position in each log file and reads only new data on each cycle, providing real-time visibility into + ongoing enrollment activity without re-processing earlier entries. +
+
+
+

+ The result is a complete, chronologically accurate record of every app installation, ESP phase, and + enrollment signal from T=0 — regardless of when the agent was installed on the device. +

+
+