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.
MicrosoftI 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.
Andre Della Monica Thanks - yes that was the culprit! My VM host (libvirt) required extra parameters to specify the serial number for the VM and once I did that, the devices enrolled in AutoPatch & are working just fine.