Forum Discussion
Autopilot issue on device set up "Identifying"
Hello everyone, I'm currently using autopilot to enroll devices into Intune. Up until now, everything has been going smoothly without any changes. However, the last three devices, which are the same ...
Even when it seems that is fixed (I also noticed the same behavior... )...i felt I still needed to post my feedback 🙂
Kinda weird that everyone mentions the prereqs like tpm... 🙂 ... As when looking at the screenshot of the esp... its becomes clear that device already passed that first step... "securing hardware" ... At that point in time, it is trying to execute powershell scripts and the office csp
(noticed that you converted it to win32.. so no issue here)
https://call4cloud.nl/2022/09/autopilot-pre-provisionings-infinite-play-uh-waiting-list/
... the google chrome one...was that a lob app?
Kinda weird that everyone mentions the prereqs like tpm... 🙂 ... As when looking at the screenshot of the esp... its becomes clear that device already passed that first step... "securing hardware" ... At that point in time, it is trying to execute powershell scripts and the office csp
(noticed that you converted it to win32.. so no issue here)
https://call4cloud.nl/2022/09/autopilot-pre-provisionings-infinite-play-uh-waiting-list/
... the google chrome one...was that a lob app?
Hi Rudy,
I have managed to get passed the Identifying on more this time however the apps are now taking so much longer and thats if they pass it.
Regardless of wifi use, ethernet etc these devices are still struggling to be consistent with autopilot. Other devices have no issues
Office I converted into win32 which works fine and we use this for all 2000 devices we have, but seems to get stuck only on these particular batch of devices / models on most occasions id get 3 that work perfectly all stages finished in 45 minutes then all others error out on the apps part or some dont pass the Identifying stage on device set up.
Google chrome is win32 too I read somewhere (probs on your blogs!) not to mix win32, lob etc.
I have managed to get passed the Identifying on more this time however the apps are now taking so much longer and thats if they pass it.
Regardless of wifi use, ethernet etc these devices are still struggling to be consistent with autopilot. Other devices have no issues
Office I converted into win32 which works fine and we use this for all 2000 devices we have, but seems to get stuck only on these particular batch of devices / models on most occasions id get 3 that work perfectly all stages finished in 45 minutes then all others error out on the apps part or some dont pass the Identifying stage on device set up.
Google chrome is win32 too I read somewhere (probs on your blogs!) not to mix win32, lob etc.
Also Rudy_Ooms_MVP Its never just identifying on just apps its all the stages within Device Set up if it gets stuck at the "identifying" stage for me
- If you try to enroll such a problem device with a regular autopilot enrollment, do you experience the same behavior?
- So use a autopilot entrolment without apps etc ie the default one?
I will give it a go.
Currently as I plan to enrol 285 devices next week I think I might need to use Provisioning packages one last time! Is it possible to get Office to install first this way?