Forum Discussion
WuFB and Clients that Never Check
Microsoftacjuelich have you confirmed that you don't have any old policies configured on the device? The devices shouldn't be paused unless pause feature/quality update start date is configured and shouldn't require manual effort unless Configure Automatic Updates (AUOptions) is configured to notify to download / install. I'd recommend reviewing your configured policies against this new blog: https://techcommunity.microsoft.com/t5/windows-it-pro-blog/common-policy-configuration-mistakes-for-managing-windows/ba-p/2077328
Thanks! The 'Pause' was in reference to a Feature Update and it was removed months ago, but I still see Clients stuck with that. Occasionally I do find some Clients with some legacy GP settings configured via the ConfigMgr Client so I can sometimes delete Registry.Pol and have it retry but I still have other clients that are configured properly and just sit there and never check. Is there a Proactive Remediation that can be done, or something via Usoclient via Run Script to rectify some of these?
I'll take a look at that article but I think when I glanced at it yesterday, it was more targeted to configurations via GPO, not Intune.
- AriaUpdated
acjuelich it should contain the CSPs which correspond to Intune policies. That said, for Intune you may instead prefer this talk: Configure Windows 10 feature updates policy in Intune - Azure | Microsoft Docs
The devices just simply aren't scanning at all? If that is the case, I would encourage you to submit a support case with logs so that we can triage this issue.