PostPpkg settle 60s -> 120s

Empirical: a fresh-imaged bay often hasn't finished AAD-join + first
Intune sync by 60s, so the post-PPKG-reboot Monitor instance starts
without DeviceId visible to dsregcmd yet. Doubling the settle to 120s
gives MDM more time to land baseline policies before the reboot,
which means the post-reboot Monitor sees AAD-joined + DeviceId on
first tick and fires idx=7 immediately.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
cproudlock
2026-05-14 19:13:26 -04:00
parent 3fb1d983df
commit 2d75935dfc
2 changed files with 3 additions and 3 deletions

View File

@@ -421,7 +421,7 @@ if (Test-Path -LiteralPath $enrollScript) {
Write-Host "=== Running enrollment (PPKG install) ===" Write-Host "=== Running enrollment (PPKG install) ==="
Write-Host "NOTE: PPKG schedules a near-immediate reboot. We will cancel" Write-Host "NOTE: PPKG schedules a near-immediate reboot. We will cancel"
Write-Host " it and hand off to Monitor-IntuneProgress -PostPpkg, which" Write-Host " it and hand off to Monitor-IntuneProgress -PostPpkg, which"
Write-Host " runs a 60s settle (giving MDM time to push baseline" Write-Host " runs a 120s settle (giving MDM time to push baseline"
Write-Host " policy) and then performs a clean reboot." Write-Host " policy) and then performs a clean reboot."
try { Stop-Transcript | Out-Null } catch {} try { Stop-Transcript | Out-Null } catch {}
& $enrollScript & $enrollScript

View File

@@ -80,11 +80,11 @@ param(
# The persistent @logon sync_intune task takes over after reboot. # The persistent @logon sync_intune task takes over after reboot.
[switch]$PostPpkg, [switch]$PostPpkg,
# -PostPpkgSettleSec: how long to wait before the clean reboot when # -PostPpkgSettleSec: how long to wait before the clean reboot when
# in -PostPpkg mode. 60s empirically gives MDM enough time to push # in -PostPpkg mode. 120s empirically gives MDM enough time to push
# the baseline policy (4 -> ~30 PolicyManager subkeys) so when techs # the baseline policy (4 -> ~30 PolicyManager subkeys) so when techs
# see sync_intune resume after reboot, the readiness signals are # see sync_intune resume after reboot, the readiness signals are
# already meaningful instead of "policy still pulling". # already meaningful instead of "policy still pulling".
[int]$PostPpkgSettleSec = 60 [int]$PostPpkgSettleSec = 120
) )
# ============================================================================ # ============================================================================