Forum Discussion
Does Windows Autopatch support DIY build PCs?
Hi,
I have some DIY build PCs enrolled and managed by Intune.
They don't have effective values (but not blank) of serial number, manufacturer and model.
Looks like following pic in Intune portal:
(For all the DIY build PCs I got similar values of serial number, manufacturer and model.
Like "SystemSerialNumber", "System manufacturer", "System Product Name", "ToBeFilledByO.E.M." and "To Be Filled By O.E.M.")
I tried to register 2 such PCs with Windows Autopatch and succeeded.
But today one of them disappeared from Windows Autopatch portal, either in Ready or Not ready tab.
The other one is fine.
I can still find the missing one in "Modern Workplace *" AAD groups, and the corresponding policy assignment seems OK.
Following pic are from the missing one:
(membership of "Modern Workplace *" AAD groups)
(corresponding policy assignment)
I guess it's a bug for Windows Autopatch to handle such DIY build PCs.
How could I solve it?
Will there be an offical fix for this?
If unfortunately it's not a bug, I wonder why.
Current device records in AAD and Intune for such DIY build PCs should be enough for Windows Autopatch to work, doesn't it?
Any opinions are welcome.
Many thanks.
- Alber - Today we use serial number, manufacturer and model to differentiate devices that are generated from device emulators we currently support (device emulators that generate serial numbers, manufacturer and model). We're considering a change on that logic in a near future to allow devices to be registered with Autopatch even no serial number, manufacturer or model is generated by the device emulator. Stay tuned for that change.
7 Replies
- AlberIron Contributor
Seems like no one (but me) use DIY build PCs in enterprise workspace.
Sounds reasonable.
I may try to use more brand pre-built PC from now on.
But I still need an explanation and suggestion about the problem above.
And I wonder why Windows Autopatch requires more information than Windows Autopilot and Intune?
Intune and AAD device IDs should be enough to identify every single device without a need of serial number, manufacturer and model, isn't it?
- RichardLian
Microsoft
Hi Alber
For detailed information on the overall device registration process for Autopatch, see Device registration overview - Windows Deployment | Microsoft Docs.
If your devices meet the requirements and you are still seeing differing results as you have described, please submit a support request and the Windows Autopatch Service Engineering Team can investigate further.
- AlberIron Contributor
Hi RichardLian
According to the docs, a duplicate serial number is not accepted by Autopatch.
I guess I registered the two devices (with the same serial number) before the check mechanism be added.
Now I still have one of them stay in Autopatch and works fine.
Really wonder why we need serial number, model and manufacturer of a device to use Autopatch.
Nonsense to me.