@george1421 Thanks for that George, and also for all the help over the years!

Had a tinker with unattend.xml and it’s fine now. Thinking it was the mismatch with local admin acct setup in there vs what I’d set locally initially, but all ok now.

However have done none of the service off/restart it options post-sysprep (and was wondering even if I’d just put something in group policy later on that’d do it, as the last time I ran this having ANY setupcomplete at all broke the sysprep process) it was in fact just fine and happy. Maybe something in 22H2 Edu is just alright with it, or the stars aligned for me on that one.

Either way all working now and thanks for diving in there.

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.

@george1421 Thanks for that George, and also for all the help over the years!

Had a tinker with unattend.xml and it’s fine now. Thinking it was the mismatch with local admin acct setup in there vs what I’d set locally initially, but all ok now.

However have done none of the service off/restart it options post-sysprep (and was wondering even if I’d just put something in group policy later on that’d do it, as the last time I ran this having ANY setupcomplete at all broke the sysprep process) it was in fact just fine and happy. Maybe something in 22H2 Edu is just alright with it, or the stars aligned for me on that one.

Either way all working now and thanks for diving in there.

Hello all - old (very old) hand at FOG but getting some oddness with my latest venture.

So, W10 goes on to VM, into audit mode, update fully, FOG service goes on, unattend.xml goes in C:\Windows\System32\Sysprep, image is drawn up successfully, then on reboot (expecting initial startup of W10) I get this:

However if I put NO unattend.xml in it goes to OOBE fine, which obviously I don’t want to be doing but suggests greatly some strangeness with unattend.xml

Anyone seen this and have any ideas? Not strictly a FOG thing (most likely) but if it’s a common one and anyone knows what to do to shut it up I’d be very grateful!

Thanks all.