Building zero touch USB Windows installer

[localzuk]

I am trying to build a USB boot image that allows us to plug it in to a device, boot it and it will do the full Windows install process, reboot into OOBE, load a package created in Windows ICD and go through the process of joining Azure AD etc...

 

I have the 2 halves of this working.

 

I have a autounattend.xml that installs windows, and is supposed to reseal.

 

I have a package from Windows ICD that works if you run it/load it during OOBE.

 

However, when you start the laptop up from that reseal, it isn't actually in OOBE - it is at the stage asking for login to Azure AD. If I go to the desktop with Ctrl Shift F3 and click to reseal, it does exactly what I want - puts us in OOBE and loads the package.

 

What am I doing wrong here?

[localzuk]

Has anyone managed to get a USB stick set up that can do this?

[pete]

Is the device already pre-registered with Azure AD (you/reseller have imported it into Azure before the box was opened) or does Azure know nothing about the device?

[localzuk]

It can be either. Some devices will arrive unregistered, some are ones we have registered. The goal is just to have a stick we can go to any of our devices, reboot to and it just reimages it fresh. No faffing. Edited June 25, 2024 by localzuk

[localzuk]

What I don't understand is why the reseal isn't properly resealing.

 

It skips over a bunch of the OOBE after the boot, post reseal - going straight to ask for wifi details (that it should have got from the ppkg file).

 

If I ctrl+shift+F3 and go into audit mode, and do nothing but click the button to reseal? That works perfectly from then on - it boots into OOBE on next boot, and loads the ppkg.

 

So, why is the reseal from the autounattend.xml not resealing the same as the sysprep tool does?

[maxschmidt]

Hi,

 

To ensure that the system enters OOBE automatically after installation and applies the package, follow these steps:

 

Ensure Resealing in Autounattend.xml: In the autounattend.xml file, make sure you're using the oobeSystem pass and that the setting under the auditSystem or auditUser section is properly set:

 

OOBE

 

Audit Mode and OOBE: If you are entering audit mode (Ctrl+Shift+F3) during setup, ensure the reseal process is included to switch from audit mode to OOBE automatically.

 

Correct Timing for the Package: Make sure the ICD package is configured to apply at the right phase of the OOBE process. The package should trigger after resealing, once the system enters OOBE.

 

Post-Setup Configuration: Double-check that the OOBE stage is properly defined in your unattend file, particularly in the oobeSystem section, to handle Azure AD and post-setup steps.

 

Testing these changes should help automate the reseal and OOBE process correctly.

 

 

Thanks