Intuning laptops - oobe -> Reboot -> User Actions

[mdrabble]

So I have been busily sorting out apps, and generally testing our Intune processes.

 

which I have been testing using the follow steps.

 

• Install Windows 11 either by USB or SCCM to get a based image loaded.
  
• Shift F10, run a couple of scripts which adds the device hash to Autopilot and sets the Intune Tag
  
• Run sysprep /oobe /shutdown so it is then ready to go.
  

 

So my questions are......

 

When the laptop has been turned on after the oobe process, should I be presented with the choose keyboard options?

 

The Autopilot Deployment Profile is set to name the laptop and configure the keyboard - do these step happen during the joining process?

 

If the AutoPilot profile only configures things during the join process - how do I skip the choose lang/keyboard options at turn on - is it possible?

 

Cheers

[snagrat]

I think it is to do with LAN connectivity? I don’t recall having this problem with PCs only laptops.

 

It is as though the keyboard configuration from the policy is applied before join and the profile must be available before connectivity

[mdrabble]

I've spent most of yesterday evening playing and it seems to be a combination of waiting for Entra/Intune to Sync and also failed Hash uploads.

 

As the has upload was part of a script I never saw the error

 

I found a set of scripts, which use a webhook to post a pass/fail notification on Teams.

 

Of the 4 laptops I have tested using this method, 2 now do exactly what they are supposed to do - once I have waited before starting the User Join Process and the other 2 had failed hash uploads.

 

YouTube video on the process I now use - in case anyone finds it useful