Repository navigation
Description
Symptom
After a domain rebuild, the two Windows 11 endpoints — carbuncle (154) and siren (155), cloned from template 911 — sit at the OOBE "set up a user account" screen and never reach a logon screen. The Server 2025 guests (DCs, titan, ramuh, from 912) are unaffected.
It is cosmetic, not a build failure
The rest of Setup completes and all automation runs; only the interactive OOBE front-end is stuck. On carbuncle, read through the guest agent while it was parked:
OOBEInProgress = 0,SystemSetupInProgress = 0QEMU-GARunning,sshdRunning- hostname already
carbuncle(ansible's base role renamed it over SSH, Configure with Ansible, and build ADR-0029's six guests from the pipeline rather than by hand #448) PartOfDomain = True;verify.ymlpassed on all six- the only console session is
defaultuser0— the throwaway account Windows uses to render the OOBE account page
So the guest is fully domain-joined and reachable; what's wedged is the first-logon UX. It bites only when someone wants an interactive console/desktop on a Win11 endpoint (e.g. to run a collector locally) — there's no real user to log in as, and the parked page won't let you pick the built-in Administrator.
Root cause
scripts/sysprep.ps1 deliberately strips the build's autologon ("so nothing logs in on the generalised image"). The clone answer file packer/windows/unattend-oobe.xml.pkrtpl therefore has no <AutoLogon> — only HideLocalAccountScreen=true plus the enabled built-in Administrator.
On Windows 11 client, that is not enough to finish the OOBE account page: without an AutoLogon or a created local user, OOBE idles as defaultuser0. The build answer file (autounattend.xml.pkrtpl) completes precisely because it does carry <AutoLogon> (Administrator, LogonCount 1) — its own comment says "AutoLogon once is what runs bootstrap.ps1." Server 2025 OOBE proceeds to the logon screen without a user, so 912-based guests don't park.
Fix
Give the clone's oobeSystem a one-shot <AutoLogon> for Administrator (LogonCount 1), with FirstLogonCommands that turn autologon off and drop the plaintext DefaultPassword Setup writes to Winlogon. The generalised image still never autologins (sysprep.ps1 unchanged); only the clone's single OOBE pass does, then disables itself — mirroring the proven build path. Draft PR attached.
It needs a 911 template rebuild (packer build, ADR-0074) and a domain rebuild to take effect, which is the lab-pipeline flow's to run — hence the PR is a draft until a rebuilt 911 clone is seen landing at a normal logon screen.
Context: ADR-0074, #440, #774.
Found while trying to run a collector on carbuncle for #451.
Activity
fix(packer): log the OOBE autologon session off, so Win11 clones lock (…
fix(packer): chain the OOBE first-logon commands so the logoff runs l…
fix(packer): one-shot AutoLogon so Windows 11 clones finish OOBE (#1092…
Gerrrt commentedon Oct 9, 2026
Verified on the rebuilt 911, 2026-10-09
#1093 merged as ba39b65, and 911 was rebuilt from main (
packer build -force, 1h15m). Then:packer-smoke.sh 911 --keep: every check passed, including "Panther answer files scrubbed (Win clones leave the build password in plaintext at C:\Windows\Panther\unattend-original.xml, readable by Users #1099)".OOBEInProgress=0;AutoAdminLogon=0;DefaultPasswordin Winlogon;defaultuser0disabled;quser: No User exists;dot-windows(198), re-cloned from the new 911 with the targeted-replace: the same result on first boot, plus noPanther\unattend-original.xml.The chained single
FirstLogonCommand(391863) is what ran. Closing.🤖 Generated with Claude Code