Windows 10 Feature Update while device moves from ConfigMgr to intune

%3CLINGO-SUB%20id%3D%22lingo-sub-1780173%22%20slang%3D%22en-US%22%3EWindows%2010%20Feature%20Update%20while%20device%20moves%20from%20ConfigMgr%20to%20intune%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1780173%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20a%20Cloud%20Sync%20Collection%20that%20i%20use%20to%20sync%20devices%20from%20a%20on-prem%20WSUS%20solution%20to%20using%20Intune%20Update%20Rings.%20This%20very%20same%20Cloud%20Sync%20collection%20is%20also%20targeted%20for%20Feature%20Update%20lock%20to%20v1909.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20i%20see%20now%20is%20that%20in%20the%20process%20of%20moving%20a%20device%20from%20on-prem%20Wsus%20to%20Intune%20Update%20Ring%2C%20there%20is%20a%20delay%20before%20these%20settings%20from%20Intune%20come%20into%20effect%2C%20and%20during%20that%20time%2C%20WU%20take%20it%20up%20itself%20to%20push%20V2004%20for%20the%20device.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20can%20think%20of%20a%20few%20ways%20to%20possible%20delay%2Fstop%20this%20from%20happening%2C%20but%20what%20is%20the%20best%20option%20to%20do%20it%3F%20use%20a%20GPO%2FConfigMgr%2C%20seperate%20cloud%20sync%20collections%2C%20AAD%20device%20groups%20etc%3F%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1784507%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%20Feature%20Update%20while%20device%20moves%20from%20ConfigMgr%20to%20intune%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1784507%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F196193%22%20target%3D%22_blank%22%3E%40Thomas%20F%C3%B8rde%3C%2FA%3E%26nbsp%3BDune%20here%20from%20the%20MEM%20team-%20unfortunately%20we%20are%20aware%20of%20this%20issue.%20Right%20now%20moving%20the%20co-management%20workload%20paired%20with%20the%20Feature%20Updates%20(preview)%20can%20cause%20a%20race%20condition%20where%20devices%20reveive%20unexpected%20feature%20updates.%20This%20is%20documented%20here%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmem%2Fintune%2Fprotect%2Fwindows-update-for-business-configure%23windows-10-feature-updates%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmem%2Fintune%2Fprotect%2Fwindows-update-for-business-configure%23windows-10-feature-updates%3C%2FA%3E%20and%20will%20be%20addressed%20with%20a%20future%20upgrade%20to%20ConfigMgr.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

I have a Cloud Sync Collection that i use to sync devices from a on-prem WSUS solution to using Intune Update Rings. This very same Cloud Sync collection is also targeted for Feature Update lock to v1909.

 

What i see now is that in the process of moving a device from on-prem Wsus to Intune Update Ring, there is a delay before these settings from Intune come into effect, and during that time, WU take it up itself to push V2004 for the device.

 

I can think of a few ways to possible delay/stop this from happening, but what is the best option to do it? use a GPO/ConfigMgr, seperate cloud sync collections, AAD device groups etc??

1 Reply
Highlighted

@Thomas Førde Dune here from the MEM team- unfortunately we are aware of this issue. Right now moving the co-management workload paired with the Feature Updates (preview) can cause a race condition where devices reveive unexpected feature updates. This is documented here https://docs.microsoft.com/en-us/mem/intune/protect/windows-update-for-business-configure#windows-10... and will be addressed with a future upgrade to ConfigMgr.