I'm having issues with an Autopilot laptop during the initial login. Often, it either takes forever to complete the setup or freezes at the last step, requiring a reboot to start the process over again. Is there any way to bypass this?
4 Answers
Make sure your profile settings don’t require certain apps to be installed before you can proceed. Also, check if you have a screen lock timeout set for users instead of devices—that's a common issue. Setting up a web login method using a TAP might be useful too.
You might want to check your ESP profile settings. There's usually an option to allow device usage even if there are installation errors. This can help you get past the last step of Autopilot without too much hassle.
I'll look into that! It seems like it times out after about 15 hours, which would allow user login afterward.
Check out these logs for troubleshooting: intunestuff.com/2024/09/04/identify-failed-apps-during-an-autopilot-installation/. It could help you find out what's going wrong with your setup.
That article looks interesting! But I'm curious, why would certain machines take 17 hours while others finish in like an hour, considering they have the same apps installed?
Have you tried logging in and possibly logging out using the Azure command line? This might allow you to start a session in a different way and see if it helps with the Autopilot issue.
So, would doing a function like F10 to access the command line during the ESP work? What command would I use to force a completion?
The screen doesn't lock, but it goes to the screensaver. It locks after completion. Where can I find the lock setting info you mentioned? And what's this TAP for web login all about? Also, does the amount of data in OneDrive impact the speed of ESP?