Forum Discussion
Autopilot Pre Provisioning Stuck at Device Setup
Hello Everyone,
I was trying to use Autopilot Preprovisioning for Windows 10 devices that we would like to setup before we deliver it to our end user.
We were getting correct Intune Autopilot profile
Once we click on Pre provisioning
Device Prepration completed in 2 minutes
then Device setup never completed and stuck on Identifying for 60 minutes
As my ESP setting is set to 60 minute.
I am getting that red screen mentioning that provisioning can not be completed.
however that device is visible in Endpoint portal with correct name template as per Autopilot profile
Not sure why it is getting stuck at Device Setup
Unable to identify Apps
Configuration profile
network
Your advise on this issue would be really appreciable.
I have tried it on OOBE device and existing device that met all the pre requisite.
33 Replies
- Any updates?
- unfortunately no update so far
- I have same issue and i am waiting for update from you, it's annoying
Masterlord2023my problem was fixed with new esp and set to yes.
I know how to create a new ESP, but what do you mean by set to yes?
Show app and profile configuration progress?Edit: Thank you this also works for me.
- hi..
1. If you dont use Autopilot prepro ... does that work like expected?
2. The device passes the first esp steps so we can rule out attestation issues as you also mentioned the device object gets created in Intune and azure.
3. could you share a screenshot at which part it is stuck? on identifying apps or other parts?
4. Which apps did you configured as required apps in the esp (assuming you configured the esp with required apps...
5. deploying any powershell scripts that could a loop?
I guess I need some more info to pinpoint your issue- Hi Rudy, Thank you so much for checking this out!
I am not pishing any POlicy, script, apps as of now to test this pre provision Autopilot
However if I test Autopilot with user login, it works like a charm as we have done mutiple devices with that method.
But Pre-Provisioning is getting stuck on Device Setup
Identifying Apps, Configuration Profile, network
Once ESP time out, I got error Something happened and we could not complete the provisioning processs in the required time.
1st Scenerio, Apps and configuration profile assigned to device with Autopilot pre-provisioning
Device Prepration completed successfully and Device visible in the Endpoint manager
Also Configuration profile assisgned successfully
App installation went fine
however, It is stuck on Device Stuck
Identifying Apps, Profile & Network for 60 minutes as per ESP settings and then Red page appears.
2nd Scenario, Without apps and Profile for Autopilot pre-provisioning
Device Preparation went successfully
Stuck on Device Setup
3rd Scenario, Autopilot Profile with user login
It works like a charm, user login, device, setup, apps install, configuration profile setup and user login altogether.- Just to be sure... no Haadj?
- Have you checked the device management events? Assess the configuration and application policies that you have assigned. Also, test with user provisioning method first to rule things out.
@rahuljindal-MVP Hi Rahul, thank you for your revert,
I have gone through the diagnostic logs and Device state is still NO to AzureAD joined
Also NGC Prerequisite check
Isdevicejoined: NO
IsUserAzureAD: NO
POlicy Enable: NO
POstlogonenable: Yes
PreReqResult: WillNotProvison1st Scenerio, Apps and configuration profile assigned to device with Autopilot pre-provisioning
Device Prepration completed successfully and Device visible in the Endpoint manager
Also Configuration profile assisgned successfully
App installation went fine
however, It is stuck on Device Stuck
Identifying Apps, Profile & Network for 60 minutes as per ESP settings and then Red page appears.
2nd Scenario, Without apps and Profile for Autopilot pre-provisioning
Device Preparation went successfully
Stuck on Device Setup
3rd Scenario, Autopilot Profile with user login
It works like a charm, user login, device, setup, apps install, configuration profile setup and user login altogether.
Azure ad join is reporting as NO. At what stage did you capture this? Are you pre-provisioning on LAN or wifi? Also, what is the Windows OS version and build?
