Forum Discussion
Solved
intune Autopilot deployment profile get not assigned
Hi all, my first question and certainly not my last. I am currently testing to get my first local devices into the AAD. So far everything has worked, the join and the policies are assigned, unde...
- Sounds to me your Autopilot registration is taking place after the enrollment and a result of ‘convert existing devices to autopilot’ in the Autopilot profile. It should be other way round. You need to register your devices in Autopilot using HWhashid before the provisioning process. Are you registering the HWhashids?
it means that the device is registered under "Autopilot Devices".
Sounds to me your Autopilot registration is taking place after the enrollment and a result of ‘convert existing devices to autopilot’ in the Autopilot profile. It should be other way round. You need to register your devices in Autopilot using HWhashid before the provisioning process. Are you registering the HWhashids?
OK, thanks. I will try.
- I personally use something like -
PowerShell.exe -ExecutionPolicy Bypass
Install-Script -name Get-WindowsAutopilotInfo -Force
Set-ExecutionPolicy -Scope Process -ExecutionPolicy RemoteSigned
Get-WindowsAutopilotInfo -Online -Grouptag xxxxx - Maybe this can help - https://learn.microsoft.com/en-us/mem/autopilot/add-devices
- "you can register the HWhashids your self in the oobe stage" Could you explain that a bit deeper?!
- That is correct. You can either the process out with your supplier or you can register the HWhashids your self in the oobe stage. Once registered, make sure they populate in a dynamic AAD group which can be assigned to your Autopilot profile and other Intune policies. The registration and assignment of Autopilot profile can take anywhere between 10-20 mins so take that into account.
- omg...yes I was able to track it just now after resetting a registered device and then the autopilot came on during setup. Phew.
So if I want to use autopilot, I always have to register all devices first?