Windows 10: sccm pxe boot destroys oobe

Configuration Manager 2107Windows 10 21H2Problem:When I use dism to deploy a captured wim image, I could get oobe and the user has to create their username and password etc to use the new computer.However, when I deploy the same wim image using sccm and pxe, I cannot start with oobe no matter what. I always end up with starting with a pre-built user account or no user account.How can I deploy the wim image using sccm and pxe so that the target computer starts with oobe instead of either a fixed user account have to know the password or no user account cannot log in?

:)

 

PXE BOOT and Defrag

Fog is an awesome utility we used it to image over 200 machine over at place I used to be employed at. You might be able to setup a PXE of hirens boot

 

PXE BOOT and Defrag

Is it possible to PXE BOOT Defrag Windows XP Pro over the network? At work we have a TON of XP Pro machines we use and they are slow as a coffin in a grave due to fragmentation.
The IT dept can not get to them as it is a 2-3 man crew. Is it possible to PXE Boot to initiate a defrag over the network to all the PCs? The management wont let them install other tools.

 

PXE BOOT and Defrag

It is possible to PXE boot into a "light" windows XP install using a FOG server:

FOG Project

I have successfully setup a laptop as a fog server and loaded various tools such as Hiren's boot CD into the PXE menu. It requires some work but it works well.

As stated above though it would be easier to use group policy to achieve this.