May 19 2022 10:34 AM - edited May 19 2022 10:44 AM
Hi all, I've been testing Autopilot Self-Deployment mode extensively for the last few months testing various scenarios and iterating several times daily on Autopilot builds. Every once and a while, I'll run into this strange issue where everything is acting 100% perfectly with a newly Autopiloted device except that it's MIA in Intune. Not hybrid, just straight AAD and Intune. This goes on for hours. Sometimes if I wait overnight, it will be there. Other times, it never shows up.
The device is getting all its configuration and apps as expected... everything looks right, it's just missing from Intune. I am re-using the same device with the same serial number. I delete the device from Intune, then Autpilot (under Windows enrollment in Intune) then I delete it from AAD. Once it's deleted, I re-install Windows on my Surface, drop to cmd with Shift-F10, use get-WindowsAutopilotInfo to upload the device, assign it to an SG, assign it to a profile, etc. etc. Then I reboot, run through Autopilot as usual.
I can select the device in AAD, hit the "manage" button and view all its config and apps. Everything looks right. I'm not sure if using the "manage" button from AAD is the same as Intune? It definitely looks like Intune but the URL is portal.azure.com instead of endpoint.microsoft.com.
any ideas? Thanks.
May 19 2022 06:34 PM
Please check if the MDM user scope is set to "All" and MAM user scope is set to "None" in Devices > Windows > Windows enrollment > Automatic Enrollment in MEM.
Hope this helps!
Moe
May 19 2022 07:36 PM
May 20 2022 01:05 AM
May 24 2022 11:12 AM