Home
%3CLINGO-SUB%20id%3D%22lingo-sub-714046%22%20slang%3D%22en-US%22%3ESupport%20Tip%3A%20Troubleshooting%20Windows%2010%20Update%20Ring%20Policies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-714046%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20everyone%2C%20here's%20another%20great%20post%20by%20Intune%20Support%20Escalation%20Engineer%20%3CSTRONG%3EMingzhe%20Li%3C%2FSTRONG%3E%20where%20she%20talks%20about%20how%20to%20verify%20if%20Intune%20Software%20Update%20Ring%20policies%20have%20been%20deployed%20to%20target%20clients%2C%20as%20well%20as%20offering%20up%20some%20great%20troubleshooting%20tips%20for%20the%20same.%20Be%20sure%20you%20check%20it%20out%2C%20and%20if%20you%20have%20any%20feedback%20for%20Mingzhe%20you%20can%20post%20it%20in%20the%20comments%20section%20below.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3D%3D%3D%3D%3D%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhen%20deploying%20Windows%20Update%20Ring%20policies%20to%20Windows%2010%20devices%20using%20Microsoft%20Intune%2C%20if%20you%20ever%20encounter%20an%20issue%20it%E2%80%99s%20important%20that%20you%20first%20determine%20whether%20the%20issue%20is%20Intune-related%20or%20Windows-related%20so%20that%20you%20can%20focus%20your%20troubleshooting%20efforts%20in%20the%20right%20place.%20As%20part%20of%20that%2C%20a%20key%20question%20is%20whether%20the%20Intune%20policy%20has%20been%20successfully%20deployed%20to%20the%20target%20device.%20Before%20I%20jump%20into%20that%20however%2C%20let's%20first%20get%20a%20basic%20understanding%20of%20Windows%20Update%20Rings%20and%20what%20their%20purpose%20is.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EUnderstanding%20Windows%20Update%20Ring%20Policies%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3ESometimes%20there%20can%20be%20a%20misunderstanding%20that%20Intune%20provides%20a%20cloud-based%20update%20service%20like%20WSUS%20from%20which%20clients%20can%20download%20updates%20and%20hotfixes.%20This%20is%20not%20entirely%20accurate%20however%2C%20as%20Windows%20Update%20Ring%20policies%20only%20%3CSTRONG%3Edefine%20an%20update%20strategy%20%3C%2FSTRONG%3E(e.g.%20block%20driver%20installation%2C%20set%20deferral%20period%2C%20set%20maintenance%20time%2C%20etc.)%2C%20they%20don%E2%80%99t%20actually%20provide%20the%20update%20infrastructure%20itself.%20Think%20of%20it%20as%20being%20analogous%20to%20certain%20Group%20Policies%20for%20Windows%20Update%20deployed%20from%20your%20on-premises%20Active%20Directory.%20This%20means%20that%20you%20still%20need%20to%20use%20your%20existing%20update%20solution%20such%20as%20%3CSTRONG%3EWindows%20Update%3C%2FSTRONG%3E%20or%20%3CSTRONG%3EWSUS%3C%2FSTRONG%3E%20to%20obtain%20the%20actual%20updates.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ENOTE%3C%2FSTRONG%3E%20%3CEM%3EYou%20can%20find%20more%20information%20in%20Windows%20Update%20Rings%20here%3A%20%3C%2FEM%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fintune%2Fwindows-update-for-business-configure%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CEM%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fintune%2Fwindows-update-for-business-configure%3C%2FEM%3E%3C%2FA%3E%3CSPAN%3E%3CEM%3E.%3C%2FEM%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CEM%3E%26nbsp%3B%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3EWindows%20Update%20Ring%20policies%20make%20use%20of%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fclient-management%2Fmdm%2Fpolicy-configuration-service-provider%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EWindows%20Policy%20CSP%3C%2FA%3E%20to%20configure%20the%20update%20policies%20on%20the%20Windows%20clients.%20Once%20Intune%20deploys%20the%20Windows%20Update%20Ring%20policy%20to%20an%20assigned%20device%2C%20Policy%20CSP%20will%20write%20the%20appropriate%20values%20to%20the%20Windows%20registry%20to%20make%20the%20policy%20take%20effect.%20So%20now%20that%20we%20know%20what%20these%20policies%20do%2C%20let%E2%80%99s%20look%20at%20how%20we%20can%20verify%20if%20the%20Windows%20Update%20Ring%20settings%20have%20been%20successfully%20applied.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CU%3EVerifying%20Windows%20Update%20Ring%20Settings%20on%20a%20Target%20Device%3C%2FU%3E%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3ELet%E2%80%99s%20begin%20by%20assuming%20that%20you%20have%20deployed%20a%20Windows%20Update%20Ring%20policy%20with%20the%20settings%20shown%20below%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20487px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F120111iA3874758BBFBA8AF%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22101922-jch-1.png%22%20title%3D%22101922-jch-1.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EHow%20do%20we%20confirm%20that%20the%20settings%20have%20been%20applied%20to%20the%20targeted%20device%3F%20There%20are%20a%20few%20different%20ways%20we%20can%20do%20that.%20Typically%20the%20status%20in%20the%20portal%20is%20sufficient%20but%20others%20are%20explained%20should%20you%20find%20them%20helpful%20when%20troubleshooting%20related%20issues.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E1.%20%3CU%3ECheck%20the%20policy%20deployment%20status%20in%20the%20Intune%20Portal%3C%2FU%3E%3C%2FP%3E%0A%3CP%3EThe%20first%20thing%20you%20should%20always%20do%20is%20check%20the%20status%20of%20the%20policy%20in%20the%20Intune%20Portal%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F120113i17CAAA3A9B113FDD%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22101922-jch-2.png%22%20title%3D%22101922-jch-2.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F120115iF0DDB70E4C0EF375%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22101922-jch-3.png%22%20title%3D%22101922-jch-3.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EAs%20you%20can%20see%20above%2C%20everything%20looks%20good%20and%20is%20reporting%20a%20success.%20However%2C%20if%20there%20are%20issues%20or%20you%20simply%20want%20confirmation%2C%20you%20can%20also%20verify%20the%20settings%20on%20the%20target%20device%20itself%20and%20we%E2%80%99ll%20go%20through%20how%20to%20do%20that%20below.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E2.%20%3CU%3EVerify%20that%20update%20policies%20are%20managed%20by%20MDM%3C%2FU%3E%3C%2FP%3E%0A%3CP%3EOn%20the%20targeted%20Windows%2010%20device%2C%20go%20to%20%3CEM%3ESettings%20-%26gt%3B%20Updates%20and%20Security%20-%26gt%3B%20Windows%20Update%20-%26gt%3B%20Advanced%20Options%3C%2FEM%3E%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F120116i250020FB58DA35AA%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22101922-jch-4.png%22%20title%3D%22101922-jch-4.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EClick%20%3CSTRONG%3EView%20configured%20update%20policies%3C%2FSTRONG%3E%2C%20then%20verify%20that%20the%20policy%20type%20is%20%3CEM%3EMobile%20Device%20Management%3C%2FEM%3E%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20746px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F120120i02ED1998C2A5CFE9%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22101922-jch-5.png%22%20title%3D%22101922-jch-5.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E-----%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20495px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F120121iDC95C9C6C7BD360B%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22101922-jch-6.png%22%20title%3D%22101922-jch-6.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EThis%20confirms%20that%20the%20update%20policies%20are%20configured%20by%20our%20MDM%20solution%2C%20which%20in%20this%20case%20is%20Microsoft%20Intune.%20However%2C%20it's%20possible%20that%20update%20policy%20is%20coming%20from%20the%20on-premises%20Active%20Directory%2C%20in%20which%20case%20we%20would%20see%20%3CEM%3EGroup%20Policy%3C%2FEM%3E%20as%20the%20policy%20type%3A%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20518px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F120122iB12D5F9FD15C74EC%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22101922-jch-7.png%22%20title%3D%22101922-jch-7.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EIf%20this%20is%20the%20case%2C%20it%20won%E2%80%99t%20matter%20what%20update%20policy%20you%20configure%20in%20Intune%2C%20the%20applied%20policy%20and%20the%20observed%20behavior%20is%20still%20going%20to%20be%20whatever%20is%20configured%20via%20Active%20Directory.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E3.%20%3CU%3EVerify%20that%20the%20Registry%20keys%20are%20properly%20configured%3C%2FU%3E%3C%2FP%3E%0A%3CP%3EIf%20the%20Windows%20Update%20Ring%20policies%20are%20successfully%20deployed%20by%20Intune%20to%20the%20target%20device%2C%20you%20will%20be%20able%20to%20see%20those%20settings%20in%20the%20Registry%20under%20%3CEM%3EHKEY_LOCAL_MACHINE%5CSOFTWARE%5CMicrosoft%5CPolicyManager%5Ccurrent%5Cdevice%5CUpdate.%26nbsp%3B%3C%2FEM%3EHere%E2%80%99s%20an%20example%20from%20a%20client%20running%20in%20my%20lab%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20386px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F120123i1D2766A7C140639B%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22101922-jch-8.png%22%20title%3D%22101922-jch-8.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThese%20values%20are%20configured%20by%20the%20Windows%20Policy%20CSP%20so%20you%20can%20verify%20that%20the%20values%20of%20the%20keys%20match%20the%20settings%20specified%20in%20your%20Update%20Ring%20policy.%20For%20more%20information%20on%20each%20of%20these%20see%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fclient-management%2Fmdm%2Fpolicy-csp-update%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fclient-management%2Fmdm%2Fpolicy-csp-update%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E4.%20%3CU%3ECheck%20the%20MDM%20diagnostics%20report%3C%2FU%3E%3C%2FP%3E%0A%3CP%3EAnother%20option%20is%20to%20capture%20and%20view%20an%20MDM%20diagnostic%20report%20from%20a%20targeted%20device%20and%20see%20if%20you%20can%20find%20the%20Windows%20Update%20Ring%20policy%20in%20it.%20If%20you%20can%20see%20the%20policy%20settings%20in%20the%20report%2C%20this%20is%20another%20indication%20that%20the%20policy%20was%20successfully%20deployed.%20The%20%3CEM%3EMicrosoft%20Helps%3C%2FEM%3E%20video%20below%20explains%20how%20to%20capture%20an%20MDM%20diagnostic%20report%20from%20a%20Windows%20device.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CIFRAME%20src%3D%22https%3A%2F%2Fwww.youtube.com%2Fembed%2FWKxlcjV4TNE%22%20width%3D%22560%22%20height%3D%22315%22%20frameborder%3D%220%22%20allowfullscreen%3D%22allowfullscreen%22%20allow%3D%22accelerometer%3B%20autoplay%3B%20encrypted-media%3B%20gyroscope%3B%20picture-in-picture%22%3E%3C%2FIFRAME%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20color%3D%22%23339966%22%3E%3CSTRONG%3ETIP%3C%2FSTRONG%3E%3CEM%3E%3A%20The%20primary%20purpose%20of%20the%20MDM%20diagnostic%20report%20is%20to%20assist%20Microsoft%20Support%20when%20troubleshooting%20issues.%20If%20you%20open%20a%20support%20case%20with%20Microsoft%20on%20Intune%20and%20the%20problem%20involves%20Windows%20clients%2C%20it%E2%80%99s%20always%20a%20good%20idea%20to%20gather%20this%20report%20and%20include%20it%20in%20your%20support%20request.%3C%2FEM%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CU%3ETroubleshooting%20Issues%20Relating%20to%20Windows%20Update%20Ring%20Policy%3C%2FU%3E%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EAt%20this%20point%20we%20have%20a%20pretty%20good%20idea%20how%20to%20confirm%20that%20our%20Windows%20Update%20Ring%20policy%20is%20being%20successfully%20deployed%2C%20but%20what%20do%20you%20do%20if%20they%E2%80%99re%20not%3F%20Here%20are%20a%20few%20things%20to%20check%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EIs%20the%20device%20properly%20enrolled%20into%20Microsoft%20Intune%3F%20If%20not%2C%20you%E2%80%99ll%20need%20to%20address%20that%20before%20troubleshooting%20anything%20specific%20to%20the%20policy.%3C%2FLI%3E%0A%3CLI%3EIs%20there%20an%20active%20network%20connection%20on%20the%20device%3F%20If%20the%20device%20is%20in%20airplane%20mode%2C%20or%20it%E2%80%99s%20turned%20off%2C%20or%20if%20the%20user%20has%20the%20device%20in%20a%20location%20with%20no%20service%2C%20the%20policy%20will%20not%20apply%20until%20network%20connectivity%20is%20established.%3C%2FLI%3E%0A%3CLI%3EHave%20you%20deployed%20the%20Windows%20Update%20Ring%20policy%20to%20the%20correct%20user%2Fdevice%20group%3F%20Be%20sure%20to%20double%20check%20that%20the%20correct%20user%2Fdevice%20really%20is%20in%20that%20group.%20This%20is%20an%20easy%20one%20that%20often%20gets%20overlooked.%3C%2FLI%3E%0A%3CLI%3EDoes%20the%20deployment%20of%20the%20entire%20policy%20fail%2C%20or%20is%20it%20that%20only%20certain%20settings%20are%20not%20being%20applied%3F%20If%20you%20find%20yourself%20faced%20with%20a%20scenario%20like%20this%20where%20only%20some%20policy%20settings%20are%20failing%2C%20below%20are%20some%20more%20things%20you%20can%20check.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EThe%20first%20thing%20to%20do%20is%20verify%20that%20the%20setting%20is%20supported%20by%20the%20Windows%20version%20of%20the%20target%20device.%20To%20give%20you%20an%20example%2C%20I%20recently%20worked%20with%20a%20customer%20who%20deployed%20a%20Windows%20Update%20Ring%20policy%20but%20there%20was%20an%20error%20in%20the%20Intune%20Portal%20for%20%3CEM%3EBlock%20user%20from%20scanning%20for%20Windows%20updates%3C%2FEM%3E%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20708px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F120124i79816DE40E2AE899%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22101922-jch-9.png%22%20title%3D%22101922-jch-9.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EWe%20started%20by%20checking%20to%20see%20what%20exactly%20the%20setting%20did%20and%20what%20the%20version%20requirements%20were.%20With%20a%20quick%20check%20of%20the%20doc%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fintune%2Fwindows-update-settings%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E%2C%20we%20saw%20that%20this%20is%20implemented%20by%20Policy%20CSP%20%3CEM%3EUpdate%2FSetDisableUXWUAccess%3A%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CEM%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F120125i1D7CF28EB0EC807E%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22101922-jch-10.png%22%20title%3D%22101922-jch-10.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBy%20further%20checking%20the%20Windows%20reference%20documentation%20at%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fclient-management%2Fmdm%2Fpolicy-csp-update%23update-setdisableuxwuaccess%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fclient-management%2Fmdm%2Fpolicy-csp-update%23update-setdisableuxwuaccess%3C%2FA%3E%2C%20we%20could%20see%20that%20the%20failed%20setting%20is%20only%20supported%20for%20Windows%201809%20and%20above%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F120126i58D38A42F51C2F69%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22101922-jch-11.png%22%20title%3D%22101922-jch-11.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20200px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F120127iB8A6E1B6D2F99A8D%2Fimage-size%2Fsmall%3Fv%3D1.0%26amp%3Bpx%3D200%22%20alt%3D%22101922-jch-12.png%22%20title%3D%22101922-jch-12.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EArmed%20with%20that%20information%2C%20we%20then%20verified%20that%20the%20effected%20devices%20were%20running%20Windows%201803%20and%20could%20then%20confirm%20that%20the%20issue%20disappeared%20once%20the%20device%20was%20upgraded%20to%201809.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20was%20the%20case%20here%2C%20if%20you%20can%20see%20that%20the%20Windows%20update%20policy%20type%20is%20set%20to%20%3CEM%3EMobile%20Device%20Management%3C%2FEM%3E%20and%20the%20registry%20key%20values%20are%20correct%2C%20it%E2%80%99s%20usually%20safe%20to%20assume%20that%20the%20problem%20is%20not%20directly%20related%20to%20Intune%2C%20but%20more%20likely%20an%20issue%20with%20the%20Windows%20client%20or%20an%20associated%20configuration%20in%20the%20environment.%20This%20means%20you%20need%20to%20start%20looking%20in%20other%20areas%20like%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EThe%20Windows%20OS%20version%20on%20the%20target%20device.%3C%2FLI%3E%0A%3CLI%3EIf%20and%20how%20Windows%20Update%20is%20configured.%3C%2FLI%3E%0A%3CLI%3EIf%20and%20how%20WSUS%20is%20configured.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EThese%20are%20beyond%20the%20scope%20of%20this%20article%2C%20however%20a%20good%20starting%20point%20is%20to%20check%20the%20%3CEM%3EWindowsupdate.log%3C%2FEM%3E.%20More%20information%20on%20that%20can%20be%20found%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Fcharlesa_us%2F2015%2F08%2F06%2Fwindows-10-windowsupdate-log-and-how-to-view-it-with-powershell-or-tracefmt-exe%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.technet.microsoft.com%2Fcharlesa_us%2F2015%2F08%2F06%2Fwindows-10-windowsupdate-log-and-how-to-view-it-with-powershell-or-tracefmt-exe%2F%3C%2FA%3E.%20Another%20good%20resource%20is%20the%20%3CEM%3ECBS%20logs%3C%2FEM%3E%20under%20%3CEM%3EC%3A%5CWindows%5Clogs%5CCBS%3C%2FEM%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20more%20information%20on%20troubleshooting%20Windows%20Update%20and%20WSUS%2C%20see%20the%20following%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F10164%2Ffix-windows-update-errors%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F10164%2Ffix-windows-update-errors%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4027322%2Fwindows-update-troubleshooter%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4027322%2Fwindows-update-troubleshooter%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4025764%2Fhow-to-troubleshoot-wsus-connection-failures%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4025764%2Fhow-to-troubleshoot-wsus-connection-failures%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CEM%3EMingzhe%20Li%3C%2FEM%3E%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%3CEM%3ESupport%20Escalation%20Engineer%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%3CEM%3EMicrosoft%20Intune%20Support%20Team%3C%2FEM%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-714046%22%20slang%3D%22en-US%22%3E%3CP%3EIntune%20Support%20Escalation%20Engineer%20%3CSTRONG%3EMingzhe%20Li%3C%2FSTRONG%3E%26nbsp%3Btalks%20about%20verifying%20Software%20Update%20Ring%20policy%20deployments%20as%20well%20as%20offering%20some%20great%20troubleshooting%20tips%20for%20the%20same.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-SUB%20id%3D%22lingo-sub-766705%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Troubleshooting%20Windows%2010%20Update%20Ring%20Policies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-766705%22%20slang%3D%22en-US%22%3E%3CP%3EGreat%20article%20Mingzhe%20!!%20Very%20helpful.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-867451%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Troubleshooting%20Windows%2010%20Update%20Ring%20Policies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-867451%22%20slang%3D%22en-US%22%3EThanks%20for%20the%20posting%2C%20Mingzhe%20-%20very%20informative.%20I'd%20like%20to%20ask%20what%20are%20your%20thoughts%20in%20regards%20to%20user-based%20assignment%20of%20update%20rings.%20Using%20user%20(rather%20than%20device)%20groups%20for%20assignment%20seems%20appealing%20to%20us%20in%20that%20user%20groups%20could%20be%20easier%20to%20administer%20than%20device%20groups.%20What%20are%20the%20implications%2C%20however%3F%20For%20example%2C%20you%20could%20have%20different%20users%2C%20possibly%20with%20different%20update%20rings%20assigned%2C%20logging%20into%20the%20same%20machine.%20Is%20there%20a%20precedence%20of%20which%20update%20settings%20will%20persist%3F%20Based%20on%20the%20documentation%20at%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fdeployment%2Fupdate%2Fwaas-servicing-channels-windows-10-updates%23switching-channels%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fdeployment%2Fupdate%2Fwaas-servicing-channels-windows-10-updates%23switching-channels%3C%2FA%3E%20you%20cannot%20always%20switch%20channels%20in%20the%20lifetime%20of%20a%20device%2C%20so%20that%20implies%20if%20a%20user%20with%20insider%20policy%20logs%20into%20a%20device%20(e.g.%20an%20IT%20support%20person)%2C%20then%20they%20could%20upgrade%20that%20device%20into%20the%20insider%20ring%20without%20a%20possibility%20to%20switch%20back%3F%20It%20seems%20safer%20to%20user%20device%20groups%20to%20get%20a%20more%20deterministic%20outcome%20of%20update%20settings%2C%20but%20have%20you%20(or%20anyone%20reading%20this)%20tried%20user%20group%20assignment%20of%20update%20rings%20and%20if%20so%2C%20what%20was%20your%20experience%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-868750%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Troubleshooting%20Windows%2010%20Update%20Ring%20Policies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-868750%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20haimizrael%2C%3C%2FP%3E%0A%3CP%3Ethanks%20for%20your%20feedback%2C%20really%20appreciate%20that.%20You%20are%20right%2C%20we%20also%20support%20the%20update%20ring%20to%20be%20deployed%20to%20a%20user%20group.%20This%20has%20the%20benefit%20that%20any%20device%20which%20belongs%20to%20that%20user%20will%20get%20the%20update%20ring%20settings%20assigned.%20But%20you%20are%20also%20right%20in%20saying%20that%20this%20could%20lead%20to%20some%20potential%20conflicts%20if%20we%20are%20talking%20about%20a%20shared%20device%20(multiple%20user%20affinity%20for%20one%20device)%20especially%20if%20the%20different%20users%20have%20different%20update%20ring%20settings.%3C%2FP%3E%0A%3CP%3EThis%20means%20that%20if%20you%20have%20a%20large%20number%20of%20shared%20devices%20(multiple%20users)%20in%20your%20company%2C%20in%20order%20to%20avoid%20potential%20conflicts%2C%20you%20should%20assign%20the%20update%20ring%20policy%20to%20a%20device%20group%20instead%20of%20user%20group.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHope%20this%20helps.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ERegards%2C%3C%2FP%3E%0A%3CP%3EMingzhe%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-870416%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Troubleshooting%20Windows%2010%20Update%20Ring%20Policies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-870416%22%20slang%3D%22en-US%22%3E%3CP%3EGreat%20Article!!!%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

Hi everyone, here's another great post by Intune Support Escalation Engineer Mingzhe Li where she talks about how to verify if Intune Software Update Ring policies have been deployed to target clients, as well as offering up some great troubleshooting tips for the same. Be sure you check it out, and if you have any feedback for Mingzhe you can post it in the comments section below.

 

=====

 

When deploying Windows Update Ring policies to Windows 10 devices using Microsoft Intune, if you ever encounter an issue it’s important that you first determine whether the issue is Intune-related or Windows-related so that you can focus your troubleshooting efforts in the right place. As part of that, a key question is whether the Intune policy has been successfully deployed to the target device. Before I jump into that however, let's first get a basic understanding of Windows Update Rings and what their purpose is.

 

Understanding Windows Update Ring Policies

Sometimes there can be a misunderstanding that Intune provides a cloud-based update service like WSUS from which clients can download updates and hotfixes. This is not entirely accurate however, as Windows Update Ring policies only define an update strategy (e.g. block driver installation, set deferral period, set maintenance time, etc.), they don’t actually provide the update infrastructure itself. Think of it as being analogous to certain Group Policies for Windows Update deployed from your on-premises Active Directory. This means that you still need to use your existing update solution such as Windows Update or WSUS to obtain the actual updates.

 

NOTE You can find more information in Windows Update Rings here: https://docs.microsoft.com/en-us/intune/windows-update-for-business-configure.

 

Windows Update Ring policies make use of the Windows Policy CSP to configure the update policies on the Windows clients. Once Intune deploys the Windows Update Ring policy to an assigned device, Policy CSP will write the appropriate values to the Windows registry to make the policy take effect. So now that we know what these policies do, let’s look at how we can verify if the Windows Update Ring settings have been successfully applied.

 

Verifying Windows Update Ring Settings on a Target Device

Let’s begin by assuming that you have deployed a Windows Update Ring policy with the settings shown below:

 

101922-jch-1.png

How do we confirm that the settings have been applied to the targeted device? There are a few different ways we can do that. Typically the status in the portal is sufficient but others are explained should you find them helpful when troubleshooting related issues.

 

1. Check the policy deployment status in the Intune Portal

The first thing you should always do is check the status of the policy in the Intune Portal:

 

101922-jch-2.png

 

101922-jch-3.png

As you can see above, everything looks good and is reporting a success. However, if there are issues or you simply want confirmation, you can also verify the settings on the target device itself and we’ll go through how to do that below.

 

2. Verify that update policies are managed by MDM

On the targeted Windows 10 device, go to Settings -> Updates and Security -> Windows Update -> Advanced Options:

 

101922-jch-4.png

 

Click View configured update policies, then verify that the policy type is Mobile Device Management:

 

101922-jch-5.png

-----

101922-jch-6.png

This confirms that the update policies are configured by our MDM solution, which in this case is Microsoft Intune. However, it's possible that update policy is coming from the on-premises Active Directory, in which case we would see Group Policy as the policy type:

101922-jch-7.png

If this is the case, it won’t matter what update policy you configure in Intune, the applied policy and the observed behavior is still going to be whatever is configured via Active Directory.

 

3. Verify that the Registry keys are properly configured

If the Windows Update Ring policies are successfully deployed by Intune to the target device, you will be able to see those settings in the Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\current\device\Update. Here’s an example from a client running in my lab:

 

101922-jch-8.png

 

These values are configured by the Windows Policy CSP so you can verify that the values of the keys match the settings specified in your Update Ring policy. For more information on each of these see https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-update.

 

4. Check the MDM diagnostics report

Another option is to capture and view an MDM diagnostic report from a targeted device and see if you can find the Windows Update Ring policy in it. If you can see the policy settings in the report, this is another indication that the policy was successfully deployed. The Microsoft Helps video below explains how to capture an MDM diagnostic report from a Windows device.

 

 

TIP: The primary purpose of the MDM diagnostic report is to assist Microsoft Support when troubleshooting issues. If you open a support case with Microsoft on Intune and the problem involves Windows clients, it’s always a good idea to gather this report and include it in your support request.

 

Troubleshooting Issues Relating to Windows Update Ring Policy

At this point we have a pretty good idea how to confirm that our Windows Update Ring policy is being successfully deployed, but what do you do if they’re not? Here are a few things to check:

 

  • Is the device properly enrolled into Microsoft Intune? If not, you’ll need to address that before troubleshooting anything specific to the policy.
  • Is there an active network connection on the device? If the device is in airplane mode, or it’s turned off, or if the user has the device in a location with no service, the policy will not apply until network connectivity is established.
  • Have you deployed the Windows Update Ring policy to the correct user/device group? Be sure to double check that the correct user/device really is in that group. This is an easy one that often gets overlooked.
  • Does the deployment of the entire policy fail, or is it that only certain settings are not being applied? If you find yourself faced with a scenario like this where only some policy settings are failing, below are some more things you can check.

The first thing to do is verify that the setting is supported by the Windows version of the target device. To give you an example, I recently worked with a customer who deployed a Windows Update Ring policy but there was an error in the Intune Portal for Block user from scanning for Windows updates:

 

101922-jch-9.png

We started by checking to see what exactly the setting did and what the version requirements were. With a quick check of the doc here, we saw that this is implemented by Policy CSP Update/SetDisableUXWUAccess:

 

101922-jch-10.png

 

By further checking the Windows reference documentation at https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-update#update-setdisableux..., we could see that the failed setting is only supported for Windows 1809 and above:

 

101922-jch-11.png

          101922-jch-12.png

Armed with that information, we then verified that the effected devices were running Windows 1803 and could then confirm that the issue disappeared once the device was upgraded to 1809.

 

As was the case here, if you can see that the Windows update policy type is set to Mobile Device Management and the registry key values are correct, it’s usually safe to assume that the problem is not directly related to Intune, but more likely an issue with the Windows client or an associated configuration in the environment. This means you need to start looking in other areas like:

 

  • The Windows OS version on the target device.
  • If and how Windows Update is configured.
  • If and how WSUS is configured.

These are beyond the scope of this article, however a good starting point is to check the Windowsupdate.log. More information on that can be found here: https://blogs.technet.microsoft.com/charlesa_us/2015/08/06/windows-10-windowsupdate-log-and-how-to-v.... Another good resource is the CBS logs under C:\Windows\logs\CBS.

 

For more information on troubleshooting Windows Update and WSUS, see the following:

 

https://support.microsoft.com/en-us/help/10164/fix-windows-update-errors

https://support.microsoft.com/en-us/help/4027322/windows-update-troubleshooter

https://support.microsoft.com/en-us/help/4025764/how-to-troubleshoot-wsus-connection-failures

 

Mingzhe Li

Support Escalation Engineer

Microsoft Intune Support Team

5 Comments
Microsoft

Great article Mingzhe !! Very helpful.

Occasional Visitor
Thanks for the posting, Mingzhe - very informative. I'd like to ask what are your thoughts in regards to user-based assignment of update rings. Using user (rather than device) groups for assignment seems appealing to us in that user groups could be easier to administer than device groups. What are the implications, however? For example, you could have different users, possibly with different update rings assigned, logging into the same machine. Is there a precedence of which update settings will persist? Based on the documentation at https://docs.microsoft.com/en-us/windows/deployment/update/waas-servicing-channels-windows-10-update... you cannot always switch channels in the lifetime of a device, so that implies if a user with insider policy logs into a device (e.g. an IT support person), then they could upgrade that device into the insider ring without a possibility to switch back? It seems safer to user device groups to get a more deterministic outcome of update settings, but have you (or anyone reading this) tried user group assignment of update rings and if so, what was your experience?
Microsoft

Hi haimizrael,

thanks for your feedback, really appreciate that. You are right, we also support the update ring to be deployed to a user group. This has the benefit that any device which belongs to that user will get the update ring settings assigned. But you are also right in saying that this could lead to some potential conflicts if we are talking about a shared device (multiple user affinity for one device) especially if the different users have different update ring settings.

This means that if you have a large number of shared devices (multiple users) in your company, in order to avoid potential conflicts, you should assign the update ring policy to a device group instead of user group.

 

Hope this helps.

 

Regards,

Mingzhe 

Microsoft

Great Article!!!

Occasional Visitor

Good .

Thanks.