Stop Auto-Login Once Imaged? Unattend.xml?
-
Hello all.
Know this isn’t a FOG issue but just wondered if anyone passing knew what to do kinda thing.
Got FOG up and running here, all looking pretty swell, about to put the DHCP rules in for BIOS/UEFI cohabitation.
Idly did wonder though if it were possible to stop any freshly-imaged machine logging in at all, and just ideally have it sit at a login screen until the FOG client reboots it and it domain joins. I’d want to keep the local admin acct enabled (as well as one other local acct) and set and retain the passwords (though can do those in the VM before it’s sysprepped, doesn’t have to be in unattend.xml.)
Issue I have is setting LogonCount in the Autologon section to zero breaks sysprep, but setting it to 1 it’s fine. Removing the whole Autologon section also breaks it.
Annoying this is I’ve done this before but I can’t for the life of me recall what I did! Maybe what I did is now deprecated, or Microsoft changed something, or I’m getting old…
Either way if anyone knows how to tackle that I’d be very grateful. Thanks all.
