Forum Discussion
Endpoint Manager Feature Updates not working
Hello,
We used WSUS in the past and want now to migrate to WUfB and feature update profiles. The feature update policy shows "not scanned yet". All devices are hybrid joined. The WSUS GPOs are turned off.
Update ring settings for the pilot ring:
Hi,
Just the first thing that pops up in my mind...
https://docs.microsoft.com/en-us/mem/intune/configuration/windows-health-monitoring?id=5004252just like i explained in this blog
Intune deploy Quality Updates | Troubleshoot installation (call4cloud.nl)
And did you happen to have read this blog
Co-Management of Windows Updates Workloads - Microsoft Tech Community
Hi,
Just the first thing that pops up in my mind...
https://docs.microsoft.com/en-us/mem/intune/configuration/windows-health-monitoring?id=5004252just like i explained in this blog
Intune deploy Quality Updates | Troubleshoot installation (call4cloud.nl)
And did you happen to have read this blog
Co-Management of Windows Updates Workloads - Microsoft Tech Community
- Hi Rudy_Ooms, I think everything is configured properly. We use Microsoft 365 Business Premium, could this be a licensing problem? I found this on the call4cloud.nl blog regarding quality updates:
Make sure you are licensed to use it: Windows 10 Enterprise E3 or E5/Windows 10 Education A3 or A5/Windows 10 Virtual Desktop Access- Feature updates should work with business premium as stated here
https://docs.microsoft.com/en-us/mem/intune/protect/windows-10-feature-updates?id=5004252
Did you happen to deploy a windows health monitoring report configuration profile?
- Hi johnsmith85, Did you ever get a resolution. I am having the exact same issue. Everything is configured correctly, but 90% of devices never update in the reports beyond offering, regardless if they have actually updated yet. It has been a week and the reports don't update once the offer is made. Many of the devices did update, but no update in reports.
I also have a tenant with lots of "Not scanned"errors. Nearly all are related to Hybrid Join errors. In Microsoft Entra - Devices the join status on these devices is often "Pending" or there are duplicate entries - Hybrid Joinn and Azure AD Registered. There are articles here on how to fix the join errors https://learn.microsoft.com/en-us/azure/active-directory/devices/troubleshoot-hybrid-join-windows-current . Mostly need to use the dsregcmd /leave command , make sure the group policy for autoenrollment is switched on then reboot. Sometimes I have to delete the device in Entra then rejoin to fix these issues.
Some errors also occur because the device has been switched off for a while
