Event banner
Event details
During the Enrollment Status Page ESP phase of device deployment (for example autopilot), devices will go to sleep and/or lock, if a screen lock policy gets deployed. This disrupts the deployment and ruins the user experience since they need to sign in again.
We target users with this policy, not devices because device policies often cause unexpected reboots during ESP.
Is there an easy way to prevent devices from sleeping/locking during ESP so we can ensure a smooth deployment?
- Hung_Dang
Microsoft
The ESP consists of the "device" ESP, which is displayed during OOBE proper (i.e., before Windows logon), and "user" ESP, which is displayed after Windows logon. OOBE itself prevents the device from going to sleep. For the user ESP, there's no built-in sleep prevention, and so you'd have to go with work-arounds, like targeting a script to the device to configure sleep/lock (and have it run during the ESP), and undo that when the user reaches the desktop via another scheduled task.
Darn. I was afraid you'd say that. 😁
Where is the right place to provide this feedback to?
Given that the user phase usually takes MUCH longer (due to apps installing), it seems this must be a common issue. Is it not?- Hung_Dang
You can file a Feedback Hub item to make the suggestion. (Although my team owns the ESP, so... :D ) You're right that customers that don't use AP registration can't target apps to devices easily, and so need to depend on the user ESP to deliver them.
