removable "feature on demand" (FOD), and sometime in 2027 is expected to be turned off

continues now with PowerShell 7.4.

again? I blame Gary Block

process based on work that you've done in the past.

Windows Autopilot - sometimes these were simple configuration issues, other times they were self-inflicted pains (e.g. deleting Azure AD device objects associated with a registered Windows Autopilot device). But as we learn more about the types of challenges encountered, we get better at detecting those issues (and eventually we'll try to prevent them from happening). To help with the detection process, I've published a new script called AutopilotHealthCheck.ps1 to the PowerShell Gallery. You can install it using PowerShell quite easily, along with its pre-requisite modules.

but that doesn't mean the device is actually usable.

were a few "preview" releases as we worked out kinks in the processes. Things are looking reasonably good now (thanks to feedback from several people on the preview versions), so a new 3.3.0 release was published.

Get-AutopilotDiagnosticsCommunity (and the older Get-AutopilotDiagnostics script too) had events in the wrong order.

Windows 10 or 11 media, for both x64 and ARM64 architectures.

fix the module so that it's compatible with PowerShell 7.

history of BDD, now known as MDT. Eighteen years later, I can now complete that story and expand on some of the items in more detail. (I will refrain from getting too carried away, hence the abridged part of the title, because you probably don't care to read a small novel.)

- it's pretty boring overall, showing information that isn't really useful (e.g. what does "Preparing for mobile device management" really mean)