Forum Discussion
Intune WUfB Feature Update deferral longer than 365 days
Is there a way, using Intune-managed WUfB, that Feature Updates can be deferred longer than 365 days? For instance, if we wanted to stay on Win10 1809, then in September move to only 19H1, is that possible, if so what would your recommendation be to stay on these builds with Intune WUfB? We have software (AV, VPN clients, security tools) that are closely tied to Feature Updates, so we can't always just let the Feature Updates roll within a year. Thank you.
- Karen_Simpson
Microsoft
PLEASE don't do this. Windows 10 v.1809 ENT edition goes out of servicing after the May Patch Tuesday update. You will NOT receive security updates for 1809 after May. We do not want you to be in an unserviced state and be exposed to future threats or vulnerabilities. Also - 19H1 is also no longer serviced. You will need to move your devices to a currently serviced version which would be 1909 or higher (2004/20H2). We never want to see customers in an unserviced state. - AriaUpdated
coleel you can of course stay on a feature update longer than 365 days after the next update is released. To do this you can leverage the new target version policies (Feature Update Deployment (Preview) in Intune to specify which feature update you want to move to and/or stay on until you change the policy. Alternatively, if you need to remain for just a short period of time you can leverage pause, but you will need to re-set it every 34 days.
AriaUpdated Thank you for the quick response. Are there any concerns if co-management is thrown into the mix, like does this break the Intune functionality? We ran into inconsistent behaviors, so not sure if this isn't supported or we just had a configuration conflict. We were told this isn't officially supported (Co-management of machines and using Intune-based WUfB to manage Feature Updates longer than 365 days), which is why the setting was in preview. So just curious if there are other strategies or if this is still the best course forward.
Why not use the targetreleaseversion setting to choose the feature release you want on?
