What's changed: Created MD-102 Chapter 2 (domain: Manage and maintain devices). Deploy Windows clients (Windows Autopilot deployment profiles/device preparation policies, modes user-driven/pre-provisioning/self-deploying, Enrollment Status Page, Windows 11 upgrades, Windows 365 Cloud PC, Windows Backup), configuration profiles (device configuration profiles, ADMX import, Group Policy analytics, specialty devices, assignment filters, enrollment time grouping), and Intune Suite/remote actions (EPM, Remote Help, Cloud PKI, Microsoft Tunnel, Advanced Analytics, remote actions retire vs wipe, rotate BitLocker keys, device query KQL).
2.1Deploy Windows clients
Understand Windows Autopilot deployment profiles / device preparation policies, deployment modes (user-driven/pre-provisioning/self-deploying), the Enrollment Status Page (ESP), Windows 11 upgrades, and Windows 365 Cloud PC.
Cloud-based deployment reuses existing hardware and auto-configures it during first boot (OOBE). No traditional imaging needed.
2.1.1Windows Autopilot and modes
Windows Autopilot automates Entra join + Intune enrollment + configuration during OOBE. Define behavior with deployment profiles (or the newer device preparation policies). Choose a mode by use: user-driven (user signs in and configures for themselves), pre-provisioning (IT pre-provisions; the user receives it quickly), self-deploying (no user interaction—kiosk/shared devices). Show progress/blocks with the Enrollment Status Page (ESP).
2.1.2Upgrades and Cloud PC
Plan/deploy upgrades to Windows 11 with Intune. Windows 365 Cloud PC provides a Windows desktop in the cloud to users; configure provisioning policies, network connections, and image management in Intune (a different experience from physical-PC Autopilot). Configure backup/restore of settings/data with Windows Backup.
Cues: "user signs in and configures for themselves" = user-driven. "IT pre-provisions; user gets it quickly" = pre-provisioning. "no user interaction, kiosk/shared" = self-deploying. "show deployment progress/blocks" = Enrollment Status Page (ESP). "Windows desktop in the cloud" = Windows 365 Cloud PC. Reuse existing hardware with OOBE auto-config = Windows Autopilot.
Watch the mix-ups: (1) Autopilot’s three modes (user-driven/pre-provisioning/self-deploying) by use case. (2) Windows 365 Cloud PC (cloud virtual desktop) vs physical-PC Autopilot are different experiences. (3) ESP shows deployment progress/blocks—not the enrollment method itself. (4) Autopilot reuses existing hardware, replacing traditional imaging.
2.1.3Section summary
- Windows Autopilot automates Entra join + Intune enrollment + config via OOBE on existing hardware
- Modes = user-driven/pre-provisioning/self-deploying by use; ESP shows progress
- Windows 365 Cloud PC delivers cloud Windows desktops via provisioning policies
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. You want new org-owned PCs to auto-configure for the user simply by signing in. Best Windows Autopilot mode?
Q2. To minimize user wait time, IT pre-provisions devices before handing them over. Best mode?
Q3. Which mode auto-deploys/configures with no user interaction, for kiosk/shared devices?
Q4. During Autopilot, you want to show configuration progress and blocking apps/policies to users/admins. Best?
Q5. Without distributing physical devices, you want to provide cloud Windows desktops to users. Best?