In this post, I’ll show you how to streamline the Out-of-Box Experience (OOBE) setup process even if you’re using Autopilot Device Preparation ( AVP2). While AVP2 is a fantastic tool for device provisioning, it doesn’t include all the customization options that Autopilot offers: Hide Privacy Settings, Software License Terms, or changing account options during OOBE. But don’t worry; I’ll walk you through how to work around this with a PowerShell script!
FooUser@ meets the Cosmic Autopilot@ user
This blog will be about me wrecking a Windows device during Autopilot Pre-Provisioning to see […]
IsTPMAttested: The Ultimate Attestation Security Gate
This is the fourth and, for now, last blog post in the Windows Enrollment Attestation […]
The Wonderful Story of APV2 Device Preparation
In one of my last blog posts, I described how I noticed that Autopilot Version […]
There will be…..Autopilot Version 2 (APv2)
This blog will be about my first encounter with APv2. Yeah!! APv2 As in Autopilot […]
Intune Sync Debug Tool: The Last Royal Treasure
This blog will be about me showing and explaining the Intune Sync Debug PowerShell tool […]
Intune: The Legend of the Certificate
Do you have devices that are missing the Intune Device Certificate or have sync issues? […]
Ready For Attestation: A True Underdog Story
This blog will explain what the “Ready for Attestation” flag truly means and show you […]
Night at the Windows Store API Service: Secret of the Subscription Activation
This blog will show you what else could break when there are Authentication Issues at […]
The Return of the Autopilot Local Account Massacre
This blog will be about “something” old we need to beware of. This blog has […]