Hey everyone, I’m kind of new to device management and am seeing things like user-driven mode, self-deploying mode, ESP, and pre-provisioning being used around. But I’m not sure how to decide what to use where. Would appreciate it if someone could help me see things more clearly. Cheers.
Autopilot modes, ESP, and pre-provisioning – when do you actually use them?Solved
Tags
Replies (7)
@noor_k, I hear you. The Autopilot setup options such as deployment modes, ESP, and pre-provisioning, can feel a bit layered at first, but it usually comes down to the device’s use case. If the device is going to a specific employee, user-driven is the way to go. The users sign in, and setup continues from there. If it’s a shared device or something like a kiosk, self-deploying fits better. No user login is involved, and the device just configures itself. That said, this mode depends on TPM being available for it to work properly.
And ESP? Is that something we should always enable?
In most cases, yes.
ESP is basically there to stop users from getting into a half-configured device.
Without it, a user might land on the desktop while critical apps (like VPN or antivirus) are still installing in the background. With ESP enabled, the device just waits until everything you marked as required is done.
Got it. What about pre-provisioning?
That’s more situational.
If your users are remote and the setup involves large apps, letting everything download on their home network can slow things down quite a bit.
Pre-provisioning lets IT handle that part in advance—apps and policies get installed before the device is shipped out. When the user receives it, they just sign in and it wraps up quickly.
So, it’s more about improving first-time experience?
Exactly. Not mandatory, but very useful when setup time becomes noticeable.