Forum Discussion
Dell laptop runs OOBE several months after being registered and used
We have a Dell Vostro laptop that has started to bring up the Autopilot oobe after login and connected to Wi-Fi, this is several months after first configuration and monitoring with Intune. it start...
I downloaded a a diagnostics from the intune admin centre, is this different to Get-AutopilotDiagnostics module - What would I be looking for?
If different can I run it remotely or do I need to login as local admin on the broken machine?
If different can I run it remotely or do I need to login as local admin on the broken machine?
The Get-AutopilotDiagnostics is easier to look through in my opinion 🙂
If you want to use the module, you can open the CMD in the ESP by pressing SHIFT-F10.
Can you see anything in the logs from Intune that can help you?
- It would appear so, once the ESP Page from previously was closed Intune started working as it should.
I have no idea why it came up with OOBE so long after the first registration with the same user in the first place, I will keep this box as a test device for now and see how I get on.
Thanks for your assistance - You now have an Autopilot-enrolled device. that isn't causing any issues?
- I deleted the old Hash and uploaded the new one, it did nothing.
I changed the Autopilot profile so that it would give diags on error and it did nothing different.
I set an Autopilot reset in progress, eventually it gave a reboot notice on the screen but then marked it as a failed reset and left the broken ESP still running.
I forced a reboot and it commenced a reset of the device.
Now have a reset machine, logged in as the end user and it seems empty but ok
It thinks its a United States laptop with a US Region though! - I haven't started yet, will upload the latest has this morning
- Hi Paul,
Sorry for the delay.
What have you tried so far? - Thanks for our help this far.
I plan to use Intune and do the following:
1. Upload the lasted Hardware Hash
2. Do an Autopilot reset and see what happens
3. If this fails do a Fresh Start.
Do you think this will work? - Nothing yet, Sent the same information to Microsoft 365 Support and they have basically washed their hands of it.
Dell diagnostics give the machine a clean bill of health. - That sounds interesting.
What have you done with the new hardware hash? - No, nothing changed, it looks like hardware hashes are not unique - they have a time element apparently.
- Has the hardware been changed on the device?
Shift-F10 does not work in the ESP 😞
Logged in as Local Admin and ran Get-AutopilotDiagnostics it came back - "This is not an Autopilot device."
Logged in as end user, Shift-F10 doesn't work on screen titled "Setting up for work or school", did Ctrl-Alt-Del and Taskmanager, opened cmd as admin and Powershell, ran Get-AutopilotDiagnostics and got same answer.
Recreated HWID and the two hardware hashes are different!