Forum Discussion
Not Ready - Must be managed by Intune
I see what's happening here egoodman - the problem is that even your device is enrolled into Intune (it has an Intune object/record), it doesn't have a serial number generated, it's blank.
Devices are required to have serial number, model and manufacturer when you register them with Windows Autopatch. I see you're using QEMU as your device emulator - Windows Autopatch doesn't support device emulators that don't generate serial number, model and manufacturer. Intune lets you manage devices without that information, but Windows Autopatch doesn't.
I'll make sure to update the Windows Autopatch Device Registration documentation to include that information.
Microsoftegoodman - Have you checked if this device has an old device record in Azure AD? If there's a duplicated record of this device, it could be that Windows Autopatch tried to register an Azure AD device record that doesn't have an Intune object associated with it anymore.
- This is a brand new demo tenant and new VMs, so I don't see any old records in AAD
- Andre Della MonicaI’d need to take a look in our backend to understand what’s happening in your case. I sent you a private message asking for more information so we can investigate this.
- Andre Della Monica
I see what's happening here egoodman - the problem is that even your device is enrolled into Intune (it has an Intune object/record), it doesn't have a serial number generated, it's blank.
Devices are required to have serial number, model and manufacturer when you register them with Windows Autopatch. I see you're using QEMU as your device emulator - Windows Autopatch doesn't support device emulators that don't generate serial number, model and manufacturer. Intune lets you manage devices without that information, but Windows Autopatch doesn't.
I'll make sure to update the Windows Autopatch Device Registration documentation to include that information.
