I am going to leave this here in case it ever helps anyone else. This is a really old bug that I reported in early days of Windows 10. If you change your workgroup setting in computer name to anything other than WORKGROUP once you join AAD the device gets stuck on boot and takes hours to move forward. I would love to know why. Ugh so much wasted time.
After joining AAD and enrolling in Intune devices take 3 hours to reboot?
I am trying to join devices to AAD and Intune. When I do those devices take 3 hours to reboot. I have tested on physical as well as VM hardware. I have disabled all configuration policies, apps and anything else. When the computer reboots it sits at the white circling dots screen for hours. Once it gets passed it everything seems fine but then any further reboots take a similar time. Something is timing out obviously but what? If I have a Local AD joined device and then do Hybrid-AAD + MDM enroll it seems to be fine. Any ideas? I can provide a MDM report made after joining AAD and before rebooting if it helps. This is on Windows 10 2004 19041.388 Education edition.
1 additional answer
Sort by: Most helpful
-
CiciWu-MSFT 1,206 Reputation points
2020-07-23T07:13:53.167+00:00 Thanks for your posting. By the way, would you please create an free online support ticket with following link and report this issue directly to Intune product team. I think it is a better way to resolve this bug as soon as possible. Thanks a lot. Here is the link:
https://learn.microsoft.com/en-us/intune/get-support#help-and-support-experience