Event banner
Event details
Is any work planned, or underway, to make Intune and Entra ID enrolments on Windows PCs in an AD/EID hybrid environment a bit more robust?
We're regularly coming across machines, sometimes several per week that just stop correctly checking in with EID and Intune, causing updates to stop, etc. We're currently having to use commands such as dsregcmd /leave to force the client to remove itself from Entra ID, then manually delete the Intune device and any remnant device entries on Entra ID, then wait up to 30 minutes for the next AD to EID sync to repopulate the device, then reboot the PC to have it re-register on EID, before then running dsregcmd /join and dsregcmd /updateDevice to get everythng back on track again, after which updates from WUfB resume once more.
It's a pain.
Jason_Sandys
Microsoft
MicrosoftHi Ryan,
Sorry to hear this is happening and seemingly pervasive in your environment. Note that this is not in any way expected though and should not be a common occurrence (if ever) and thus should be troubleshot to determine the root cause as there's some additional factor or influence leading to this scenario that is, as noted, not normal or expected. I strongly suggest that you open a support case to help troubleshoot this issue. You can start this process on your own as well by reviewing the event logs. The troubleshooter described at https://learn.microsoft.com/en-us/entra/identity/devices/troubleshoot-device-windows-joined may help as well.