Intune Windows Update/Feature Update Ring applied but clients not updating

%3CLINGO-SUB%20id%3D%22lingo-sub-2427882%22%20slang%3D%22en-US%22%3EIntune%20Windows%20Update%2FFeature%20Update%20Ring%20applied%20but%20clients%20not%20updating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2427882%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20recently%20moved%20some%20of%20our%20co-managed%20workloads%20from%20SCCM%20to%20Intune%2C%20not%20pilot%2C%20and%20for%20the%20most%20part%20our%20devices%20are%20happy%20with%20our%20Intune%20Windows%2010%20Update%20Ring%20settings.%26nbsp%3B%20We%20have%20a%20profile%20created%20for%20Quality%20updates%20and%20are%20also%20using%20the%20Window%2010%20Feature%20Updates%20as%20a%20separate%20profile.%20What%20we're%20seeing%20on%20some%20devices%20is%20the%20profiles%20are%20being%20applied%20to%20the%20Windows%2010%20device%20but%20the%20device%20is%20not%20going%20out%20to%20WUfB%20to%20grab%20the%20required%20Quality%20or%20Feature%20update.%20I%20can%20see%20the%20settings%20have%20been%20applied%20by%20reviewing%20the%26nbsp%3BMDMDiagReport%20and%20these%20settings%20are%20identical%20to%20a%20working%20device.%20In%20Intune%20I%20can%20see%20that%20the%20device%20does%20have%20the%20proper%20workloads%20as%20well.%20What%20is%20odd%20though%2C%20is%20on%20the%20device%20when%20I%20look%20at%20the%20configured%20update%20policies%2C%20it%20shows%20that%20no%20policies%20have%20been%20configured%20yet.%20There%20are%20no%20GPO%20or%20MECM%20client%20settings%20that%20are%20still%20configured%20that%20could%20be%20stomping%20on%20the%20Intune%20policy%20as%20I've%20ran%20an%20RSOP%20and%20have%20checked%20to%20make%20sure%20the%20client%20settings%20have%20been%20removed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anyone%20else%20seen%20this%3F%20Any%20ideas%20what%20else%20to%20check%3F%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EThanks%20very%20much%20everyone!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2427882%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EIntune%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMobile%20Device%20Management%20(MDM)%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2429508%22%20slang%3D%22en-US%22%3ERe%3A%20Intune%20Windows%20Update%2FFeature%20Update%20Ring%20applied%20but%20clients%20not%20updating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2429508%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F708029%22%20target%3D%22_blank%22%3E%40HenrikInAB%3C%2FA%3E!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20sure%20we%20can%20solve%20this%20together%2C%20I%20have%20some%20questions%20to%20get%20us%20going%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3E%3CSPAN%3EFrom%20the%20printscreen%20it%20seems%20the%20faulty%20device%20does%20not%20have%20a%20%3CSTRONG%3EPrimary%20User%3C%2FSTRONG%3E%2C%20is%20this%20the%20case%20for%20the%20working%20devices%20as%20well%3F%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3EAre%20the%20MDM-policies%20deployed%20to%20%3CSTRONG%3EUser%3C%2FSTRONG%3E%20och%20%3CSTRONG%3EDevice%3C%2FSTRONG%3E%20objects%3F%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3EAre%20you%20able%20to%20find%20any%20differences%20in%20the%20MECM%20%3CSTRONG%3Eclient%20policy%3C%2FSTRONG%3E%20deployed%20to%20working%2Ffaulty%20devices%3F%3C%2FLI%3E%3CLI%3EPlease%20see%20this%20article.%20We%20want%20to%20make%20sure%20that%20we%20do%20not%20have%20a%20WUserver%20value%20pointing%20towards%20a%20WSUS-server.%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fde-de%2Fsecurity-updates%2Fwindowsupdateservices%2F21669493%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EConfigure%20Clients%20in%20a%20Non%E2%80%93Active%20Directory%20Environment%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FLI%3E%3CLI%3EPlease%20see%20this%20article%20describing%20feature%20update(s)%20policy%20and%20Co-Management.%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Ftroubleshoot%2Fmem%2Fintune%2Fcreate-feature-update-hold-co-managed-devices%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EHow%20to%20create%20a%20feature%20update%20hold%20for%20co-managed%20Windows%2010%20devices%20-%20Intune%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELet%20me%20know%20if%20above%20helps%2C%20otherwise%20we%20will%20keep%20digging%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%20regards%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENicklas%20Ahlberg%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fnicklasahlberg.se%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Fnicklasahlberg.se%2F%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

We recently moved some of our co-managed workloads from SCCM to Intune, not pilot, and for the most part our devices are happy with our Intune Windows 10 Update Ring settings.  We have a profile created for Quality updates and are also using the Window 10 Feature Updates as a separate profile. What we're seeing on some devices is the profiles are being applied to the Windows 10 device but the device is not going out to WUfB to grab the required Quality or Feature update. I can see the settings have been applied by reviewing the MDMDiagReport and these settings are identical to a working device. In Intune I can see that the device does have the proper workloads as well. What is odd though, is on the device when I look at the configured update policies, it shows that no policies have been configured yet. There are no GPO or MECM client settings that are still configured that could be stomping on the Intune policy as I've ran an RSOP and have checked to make sure the client settings have been removed.

 

Has anyone else seen this? Any ideas what else to check?


Thanks very much everyone!

1 Reply

Hello @HenrikInAB!

 

I am sure we can solve this together, I have some questions to get us going :)

 

 

Let me know if above helps, otherwise we will keep digging :)

 

Best regards

 

Nicklas Ahlberg

 

https://nicklasahlberg.se/