[ad_1]
I’ve been used to the routine: If an app fails to install during Autopilot with ESP monitoring the progress, you don’t find out about it right away. Instead, you would have to wait until the ESP time limit passed and then you’d get a timeout error. Not only was that more difficult to troubleshoot than it should have been, it also could add a long delay to the process. If ESP was configured with a two-hour timeout (120 minutes), you wouldn’t see the (timeout) error until two hours had passed.
Today, I purposely caused an app install to fail (I put in an invalid installation command line on a Win32 app), and was surprised to see ESP fail right away:
The diagnostics page wasn’t particularly helpful in telling you which app failed, as it marked all the apps that had not yet finished installing as errors:
But it could at least tell you that there were one or more app issues. The Get-AutopilotDiagnosticsCommunity script could tell you which app had an issue:
So that’s progress. I don’t see any indication of changes in Autopilot itself related to this, but it is possible that there were changes to Intune Management Extension to report an error right away (and quite possibly it wasn’t an issue in Autopilot in the first place). Regardless of where it was fixed, it’s a welcome change.
[ad_2]
Source link
