Forum Discussion
Autopilot self-deploy failing to register for MDM
Devices do meet the requirements. TPM 2.0 is enabled. Our shop has been using Autopilot for user driven devices for about a year now.
I have checked that blog but I'm reviewing it again to ensure the profile is set up. I also confirmed that they are seeing the autopilot profile. These devices used to be user driven but I've cleared the intune & azure record and re-imported the hash. I've attached screenshots of both the autopilot profile and the kiosk config profile.
- Mar 12, 2022
TPM 2.0 AND attestation?
Self-deploying requires attestation
How does that group AP Kiosk devices look like? Do you have uploaded the hh with a grouptag or?Do you have multiple autopilot profiles as you are telling "autopilot for user driven devices"
Did you have take a look at the event logs (modern deployment / user device registration / )
- MiNealyMar 15, 2022Copper ContributorConfirmed that the devices that I'm using have TPM 2.0 and attestation.
The AP Kiosk Devices group is using a group tag to tie the profile to the device. Our other Autopilot profiles are set up the same way for user driven devices and experience no issues.- Mar 16, 2022At this point i would also recommended to start the ticket tour with Microsoft. Especially because of that error you got: profilevalidationwhiteglovedisabled
As I have never seen it before. Could you check out the registry key
HKLM:\Software\Microsoft\Provisioning\Diagnostics\Autopilot
and whats is in it