Device-assigned MDM policies whose CSP URIs match the OS reboot-required
catalog force a coalesced reboot at the end of ESP DeviceSetup - the user
sees an unexpected restart and a second sign-in before AccountSetup.
Invisible in the Intune console; admins simply lived with it. Now attributed
and actionable (PMPC research).
- MdmRebootPolicyTracker (+host): watches DeviceManagement-Enterprise-
Diagnostics-Provider/Admin EventID 2800, emits one mdm_policy_reboot_required
per reboot-forcing URI (Warning, ImmediateUpload; tolerant EventData-first
URI extraction with regex fallback; fail-soft OMADM RebootRequired probe).
Cross-restart RecordId watermark (mdm-reboot-watermark.json) - mandatory,
the coalesced reboot restarts the agent and the backfill re-reads the log.
- ShellCoreTracker: RebootCoalescing branch on the already-watched 62407
stream -> esp_reboot_coalescing corroboration event; deliberate deviation:
emits on backfill too (live emit races the reboot kill).
- ANALYZE-ESP-005 advisory (warning): names the first URI via {{rebootUri}},
remediation = reassign profiles device -> user groups; +20 confidence on
coalescing corroboration, +10 on >=2 URIs.
- Config: Collectors.MdmRebootPolicyWatcherEnabled (default ON, internal
steering only - agent-native collector, NOT an IAgentAnalyzer, no admin UI),
MdmRebootPolicyBackfillLookbackMinutes=60; ConfigVersion 35.
- Event types deliberately distinct from system_reboot_detected so the
backend RebootCount (exact-string match, 2 sites) stays uninflated.
- Docs: docs/agent/mdm-reboot-coalescing.md (+index/log). Exact 2800/62407
message texts are unverified until E2E VM validation (tolerant matching).
Tests: Agent.V2.Core 1868/1868 (21 new), Functions 3099/3099, MCP 400 passed
(event-types drift), solution build 0 errors.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
4.2 KiB
Log
2026-07-20
-
Creation: Added
agent/mdm-reboot-coalescing.md— the agent now attributes the "unexpected mid-ESP reboot + second sign-in" pattern (PMPC research) to the device-assigned policy URIs that forced it: newMdmRebootPolicyTracker(DM-Enterprise EventID 2800, per-URImdm_policy_reboot_requiredevents, cross-restart RecordId watermark), aRebootCoalescingbranch inShellCoreTracker(esp_reboot_coalescing, backfill-emitting by design), and theANALYZE-ESP-005advisory (reassign device → user groups). ConfigVersion 35; event types deliberately distinct fromsystem_reboot_detectedso RebootCount stays uninflated. -
Creation: Added
backend/business-timestamps.md(newbackend/section) — the 2026-07-18 migration reset every row's system Timestamp, exposing that AuditLogs/OpsEvents/Events had (unknowingly) displayed and filtered on it all along; documents theOccurredUtccolumn, the RowKey decoders and RowKey-range date/retention clauses inBusinessTimestamp, the GUID-guard trap, the audit/ops backfill endpoint, and the "system Timestamp is never authoritative" migration rule. -
Creation: Added
rules/gather-rule-phase-scoping.md(newrules/section) — gather rules gainactivePhases(run only during listed phases),activeFromPhase(sticky latch from a phase onwards, never via Failed) andemitMode: "on_change"(canonical-hash result dedup withsuppressedPollsobservability), ConfigVersion 34. Includes the prerequisite backend fix: the custom-rule toggle PUT no longer wipes the stored rule definition (partial-merge inGatherRuleService.UpdateRuleAsync).
2026-07-18
- Creation: Added
agent/endpoint-migration.md— config-channel agent re-home (MigrateToApiBaseUrlonGET agent/config, ConfigVersion 33): backend or per-tenant API-URL moves without DNS indirection (impossible due to mTLS/Flex-TLS). Live-fetch-only with cache strip,AgentEndpointMigrationRulesallowlist validated on both sides, one hop, kill-switch wins. Built as the lesson from the 2026-07-18 WEU→GWC cutover, which hard-cut all in-flight agents.
2026-07-17
- Creation: Added
agent/build-counter-blob.md— agent build numbers now come from a shared public counter blob (buildcounter-v{N}.txt, reserve-before-build with ETag-CAS) so localbuild.ps1and CIbuild-agent.ymlbuilds can never mint the same number. Documents the CI parity fixes (SummaryDialog.exe.config in the ZIP, EXE-vs-manifest version check, hash-oracle update gated on stable cutover) and the Sigstore provenance attestation on CI-built ZIPs.
2026-07-16
- Creation: Added
agent/autopilot-ztd-diagnostics.md— reference for Windows' own ZTD diagnostic surfaces (ModernDeployment Autopilot event IDs incl. 807/809/815/908, theDiagnostics\Autopilotregistry key, deployment-service endpoints, known-issue error-code map with KB fixes). Backs the agent'sZtdEvidencecollector (ztdVerdictonautopilot_profile_missing) and the backend known-issue rules; sources carry a re-check RSS feed.
2026-07-13
-
Removal: Moved
customer-graph-add-on-permissions.mdout of this contributor bundle into the customer documentation repository (reference/optional-graph-permissions.md). It was customer-facing product content and did not belong in the tech-docs bundle; removed the entry fromindex.md. -
Creation: Added
agent/hello-wizard-unskip.md— session 772fe502 fix: theHelloWizardStarteddecision signal (prevention veto + un-skip cure for the policy-disabled Hello shortcut) and the HelloTracker confirmation second read against flip-flopping WHfB CSP values.
2026-07-11
-
Creation: Added the
agent/section — three concept documents on the V2 agent:agent/overview.md(runtime, collectors, telemetry pipeline),agent/decision-engine.md(DecisionCore reducer, signals, A/B/C completion arms, invariants),agent/logs-and-persistence.md(persisted artifacts, signal log vs spool, recovery/replay flow) plusagent/index.md. -
Creation: Converted
docs/into an OKF v0.1 knowledge bundle — added YAML frontmatter toarchitecture.md,mcp-oauth-flow.md, andcustomer-graph-add-on-permissions.md; createdindex.mdand this log.