You’re probably used to looking at Windows Autopilot profiles in Intune. But most of the time, I’m looking at one from the CAB file that is created by the MDMDiagnosticsTool. As I noted in my previous log, these CAB files contain several files, including the AutopilotDDSZTDFile.json that contains all the Autopilot profile settings. But those do require some interpretation, especially to decode the CloudAssignedobeConfig values. To help with that, I published a new script on the PowerShell Gallery:
It’s a fairly simple script, but it is still useful to see what Windows Autopilot is using to provision the device. Here are a few examples, first from a User-Driven Azure AD join profile:
See how the OOBE config value (28) breaks down to three separate bits (skipping EULA, skipping OEM screens, and skipping other OOBE express settings). Next, here’s a Hybrid Azure AD Join profile:
Pretty much the same, except for a different join method. And lastly, here’s a self-deploying mode profile:
There are a number of different flags set on that one (which is the only way you can tell the profile apart from a user-driven AAD join profile).
If you want to just check the meaning of a particular OOBE flag value, you can do that too:
Categories: Windows Autopilot