By Mihai Lucian Androne | Support Escalation Engineer and Eric Orman | Sr. Intune Program Manager
We recently released a new feature for the Enrollment Status Page (ESP) that will allow you to both track the installation progress for Office 365 Click-to-Run (C2R) and also configure and confirm that the ESP policy will be enforced for C2R installation if marked as a required application. This change only applies to Windows 10 October 2018 Update (version 1809) and later. Prior Windows versions will not have Office C2R installation enforced or tracked in ESP.
The impact of enforcing installation of C2R with ESP policy might cause your end user to remain in ESP longer and possibly could cause ESP timeout depending on the configuration. To avoid an app error, you may want to consider increasing the time specified in the Autopilot profile. Below, we share additional information on this new feature and how you can keep from having the ESP timeout delays for your users.
NOTE: Customers have reported a known issue and we also observed the same transient issue whereby existing ESP profiles might not show the new setting to configure which apps should block ESP. We are working on fix estimated to ship mid-December. In the meantime, if your exiting ESP profiles don’t have the new setting, then change the setting “Block device use until all apps and profiles are installed” from Yes to No then back to Yes. This is a workaround until the fix is released.
The ESP (in preview) allows you to customize the device set up experience for your users, helping them to understand the status of their device related to policies that are going to be applied to their device or applications that are mandatory for their productivity.
There are situations where large applications like C2R will require more time to be installed completely on the device. The app installation time is not increased/decreased by ESP, but depends instead on network bandwidth and different device capabilities. We got an Apps (failed) when testing the new ESP and C2R experience ourselves, and it took a bit of time to troubleshoot the error. What we found was that we needed to change the default time-out configuration of 60 minutes. The behavior we saw in our testing looked similar to this:
Your end users may see this with other large applications that go beyond the ESP time period, or if you have many apps that need to be installed during the ESP time period. To keep end users from seeing this Apps (failed) screen due to this root cause, you can:
To enable this, you need to:
Respond back on this post if you’ve got any additional questions on Enrollment Status Page app installation tracking and hope this helps you troubleshoot!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.