This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(272, 92%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJP%3C/text%3E%3C/svg%3E)
I will try to provide as much information as I can to describe the situation.
We have newly configured Autopilot, have a hybrid AD environment configured with MECM and have configured all existing devices to enroll into autopilot so we can start to eliminate the need to image/re-image our Windows workstations. We have also configured the Enrollment Status Page.
For the ESP, we have set the option to "Yes" for not displaying the ESP for devices that did not go through the OOBE. The problem we're having is that all Windows machines are still showing the ESP to every subsequent user on a computer. We have tried a variety of options, most of which have no affect at all, and don't appear to be updating on the workstations even after a forced sync.
We have also tried setting a manual OMRI to SkipUserStatusPage, but when deployed to all Windows workstations, the configuration policy shows "Not applicable" for all 1000 computers.
I had a hunch that the issue is that most of these machines, which were existing, have never been through the OOBE so they will show the ESP once, but that isn't the case, it is still shown for each new user. We're at a complete loss as to what is going on and why these computers are not honoring the settings to skip this page.
Questions:
Are there any other suggestions on how to fix the ESP issue? Is there a script or local commands we can run through MECM to fix existing machines to eliminate the ESP? Any ideas as to why the OMRI is showing not applicable even though we scoped it to all Windows workstations?
Has anyone opened a support case yet? If not, please do so that we can research the issue.
we have set the option to "Yes" for not displaying the ESP for devices that did not go through the OOBE.
Where did you set this option? ESP has 'Show app and profile configuration progress' setting. If you set to Yes, the enrollment status page is displayed.
ESP will display provisioning progress after a new device is enrolled, as well as when new users sign into the device.
SkipUserStatusPage will be applied to the devices/users that undergo the enrollment phase but not all devices that exist in intune.
Regards,
Eswar
www.eskonr.com
Thanks for the reply. We have 2 ESP profiles set. The default is set to Yes to show app and profile config as we'd like Autopilot devices to show them and then we have another, higher-priority configuration assigned currently to all Windows workstations with it set to No.
All machines, regardless of which group they're in, are showing the ESP for all users who log in.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(25.6, 84%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAB%3C/text%3E%3C/svg%3E)
Glad to see we aren't crazy. We are the same scenario: Hybrid AD, managed by ConfigMgr, we have our hardware vendors register devices to our AutoPilot service but we don't actively use AutoPilot yet. We image our machines from ConfigMgr. I've had our ESP configured similar to yours for months, if not years at this point, and it was just recently that we began getting feedback from our support teams that machines are displaying the ESP when new users log in. I have now turned off both of our ESP configs to see if that "fixes" it. I'm thinking something has changed on the back end at Microsoft that is causing this behavior, was searching for any kind of change logs when I happened upon this thread.
We have not but will open a ticket. One thing we have now discovered is that since we have Configuration Manager and Intune in place and the devices are Co-Managed, in testing, if we switched the workload in MECM to allow Intune to manage the Device Configuration, then the settings to skip the ESP were honored. I don't know if/when settings were changed, and this isn't a workaround for us at the moment, but there is now something to point to.