SOLVED

Devices not showing up on the Autopatch Portal

Brass Contributor

I am testing Autopatch on our environment, I added several devices to the "Windows Autopatch Device Registration: but only one is showing up as a discovered device. All devices are Windows 10 and Windows 11, Intune managed devices, and on the group there are laptops, regular Azure VMs and Windows 365 VMs

 

Also this device that is on the discovered list of devices went automatically to the "First" group. When I try to move it to the Test group the process looks ok but the group change doesn't happen. 

I opened a case with Microsoft, still waiting for a solution. When I get one I will posted here.

 

In the mean time, any ideas?

3 Replies
On the Autopatch Devices section of MEM you should see a "Not Ready" Section. This should show the devices which are not registered in Autopatch and possible reasons for failure.
best response confirmed by Harman_Thind (Microsoft)
Solution
The "Not ready" tab is available as of last Thursday (06/09). Now you'll be able to see all devices that successfully registered versus the ones that failed to register and its reasons. Let me know how that goes. Also, stay tuned in this doc, as I'm updating it soon with some more information to help you successfully register devices into Windows Autopatch.

https://docs.microsoft.com/en-us/windows/deployment/windows-autopatch/deploy/windows-autopatch-regis...
Thanks for the answer, Not ready started to show up around that date. Looks like it is working now.
1 best response

Accepted Solutions
best response confirmed by Harman_Thind (Microsoft)
Solution
The "Not ready" tab is available as of last Thursday (06/09). Now you'll be able to see all devices that successfully registered versus the ones that failed to register and its reasons. Let me know how that goes. Also, stay tuned in this doc, as I'm updating it soon with some more information to help you successfully register devices into Windows Autopatch.

https://docs.microsoft.com/en-us/windows/deployment/windows-autopatch/deploy/windows-autopatch-regis...

View solution in original post