Forum Discussion
Autopilot Error (0x81036502) - Endpoint Manager
- https://call4cloud.nl/?s=0x81036502 😛
just use my blog as your own personal google search....
Lets start by looking at which apps you configured as required apps during the esp
If you know the apps... use mn his get-autopilotdiagnostics tool to determine which app has a wrong install status ... or by looking at the registry
https://learn.microsoft.com/en-us/troubleshoot/mem/intune/device-enrollment/understand-troubleshoot-esp
I guess with a little bit of searching you will find the culprit
nmartinez1205 removing the application from the ESP does not prevent it from being installed, it will still install in its own good time after the ESP finishes. The ESP only tracks the installs of the applications specified in the ESP, and will not release the ESP until they are installed. I believe it prioritizes these app installs, but it does not force them to be installed first. This has been an issue with Intune apps and continues to be as there is no way to control the install order. Say, for example you have two apps specified in your ESP, and 10 other required apps. It is possible that these 10 apps could install prior to the 2 you specified, and the time this takes could cause the ESP to time out. However, the application will still install in the background, regardless of the ESP failure or not (providing the installation is working fine), which makes troubleshooting difficult. Another scenario is that an application may fail to install because it has a dependency on another application and cannot install successfully until that application is installed. A third scenario is when an application install fails and puts a prompt or information screen up, which is hidden by the ESP. The user never sees it, and so cannot hit continue or ok or whatever the prompt is waiting for and the ESP stalls and eventually times out. generally these are the best issues as they may prevent the other applications from installing until the button is pressed and the process ends, permitting the next application to start.
Yet another scenario is where you have multiple application deployment mechanisms, like ConfigMgr and Intune, if both try to deploy an application at the same time, one will win, the other will fail due to another install taking place. This can happen with MSI apps or when mixing MSI (lob) and Win32 as the Win32 could have an embedded MSI.
In my personal opinion the Autopilot process is not Enterprise-ready and has so many issues. Don't get me started with Co-Management in Autopilot, that is a whole other can of worms.
As a workaround, by removing it from the ESP, what I achieved, is that the AP process continues its course so that the workstation is finished configuring satisfactorily.
I did some research, and the failure was because the detection method of the application was wrong, so after fixing it, I was able to assign it back to the ESP.