Assigning Autopilot profiles by exception

I mentioned in my previous blog that I typically use an “All Autopilot Devices” dynamic group to assign an Autopilot profile automatically to most devices, while using two additional groups to let me manually assign devices that I want to deploy differently.  Given that there were several questions around that, I though it would be…

6

Evaluating/Testing/Demoing modern deployment with Windows Autopilot

Whether you are evaluating Windows Autopilot for the first time, testing out new features and capabilities, or demoing it to new customers, you’re typically going through the same basic steps: Getting the hardware hash from an existing machine.  See https://docs.microsoft.com/en-us/windows/deployment/windows-autopilot/add-devices#collecting-the-hardware-id-from-existing-devices-using-powershell for the steps to do this using the Get-WindowsAutopilotInfo script. Uploading the device to Intune…

8

Revisiting Windows Autopilot for existing devices

Back in October, I posted a blog talking about speeding up Windows Autopilot for existing devices, with a custom task sequence template to avoid the extra sysprep generalize and specialize that happens with the default ConfigMgr task sequence template for Windows Autopilot for existing devices (now built into ConfigMgr current branch).  Based on feedback from…

1

Blocking for app installation using Enrollment Status Page

When you do an Autopilot deployment, we recommend configuring the Enrollment Status Page (ESP) to block until those app installations are done – the user won’t be able to get to the desktop until the device is configured so that they can be secure and productive. But we recognize that some apps are more important…