Windows 11 Delay Rollout via Intune

%3CLINGO-SUB%20id%3D%22lingo-sub-2704623%22%20slang%3D%22en-US%22%3EWindows%2011%20Delay%20Rollout%20via%20Intune%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2704623%22%20slang%3D%22en-US%22%3E%3CP%3EWith%20Microsoft%20announcing%20today%20that%20October%205th%20being%20the%20release%20date%20for%20Windows%2011%20will%20there%20be%20Microsoft%20Intune%20policies%20to%20either%20delay%20rollout%20or%20to%20limit%20the%20rollout%20to%20IT%20and%20some%20test%20users%3F%20What%20is%20the%20plan%20for%20rollout%20with%20Intune%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2704623%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-2730871%22%20slang%3D%22en-US%22%3ERE%3A%20Windows%2011%20Delay%20Rollout%20via%20Intune%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2730871%22%20slang%3D%22en-US%22%3EJeffrey%2C%20This%20can%20be%20achieved%20by%20one%20of%20two%20ways%20that%20I%20can%20think%20of%3A%201.%20Deploy%20an%20Update%20rings%20for%20Windows%2010%20and%20later%20policy%20to%20all%20devices%20and%20exclude%20IT%2Ftest%20users%20and%20create%20a%20second%20policy%20for%20those%20testing%3B%20or%202.%20Deploy%20a%20Feature%20update%20for%20Windows%2010%20or%20later%20policy%20and%20specify%20the%20feature%20update%20version%20you%20want%20to%20deliver%2C%20in%20doing%20this%20the%20targeted%20devices%20will%20not%20go%20further%20than%20the%20feature%20update%20version%20stated%20in%20the%20policy%2C%20so%20if%20your%20devices%20are%20already%20at%2021H1%20then%20when%20you%20deploy%20the%20policy%20to%20those%20devices%20they%20will%20not%20update%20further%20than%2021H1.%20Microsoft%20goes%20a%20little%20into%20detail%20on%20how%20this%20works%20and%20how%20the%20safeguards%20work.%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmem%2Fintune%2Fprotect%2Fwindows-10-feature-updates%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmem%2Fintune%2Fprotect%2Fwindows-10-feature-updates%3C%2FA%3E%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fdeployment%2Fupdate%2Fupdate-compliance-feature-update-status%23safeguard-holds%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fdeployment%2Fupdate%2Fupdate-compliance-feature-update-status%23safeguard-holds%3C%2FA%3E%3C%2FLINGO-BODY%3E
Super Contributor

With Microsoft announcing today that October 5th being the release date for Windows 11 will there be Microsoft Intune policies to either delay rollout or to limit the rollout to IT and some test users? What is the plan for rollout with Intune?

3 Replies
Jeffrey, This can be achieved by one of two ways that I can think of: 1. Deploy an Update rings for Windows 10 and later policy to all devices and exclude IT/test users and create a second policy for those testing; or 2. Deploy a Feature update for Windows 10 or later policy and specify the feature update version you want to deliver, in doing this the targeted devices will not go further than the feature update version stated in the policy, so if your devices are already at 21H1 then when you deploy the policy to those devices they will not update further than 21H1. Microsoft goes a little into detail on how this works and how the safeguards work. https://docs.microsoft.com/en-us/mem/intune/protect/windows-10-feature-updates https://docs.microsoft.com/en-us/windows/deployment/update/update-compliance-feature-update-status#s...

@BraulioCulcay, While I do like that idea and it did cross my mind, if I do that then the devices might not get the 21H2 update and so I'm hoping there will be a policy that I can just assign that is configured for Win 11 specifically. I do intend as you mentioned, to having IT and a few test users go to Win 11 when available but want to delay moving the rest until maybe late Spring or even the summer of 2022.

Hi,

I am not certain if this works... but maybe creating a proactive remediations which configure

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
TargetReleaseVersion and TargetReleaseVersionInfo and configure the 21h2 update in it?

And after a while change it/remove it ? (looked in the settings catalog.. you could select it.... but not configure it?)