Forum Discussion
Force Update scan with WUFB managed by Intune
AriaUpdated thank you for the information.
I was asking because whenever I click on "Check for Updates" it doesn't honor my 'Windows 10 feature updates'
Is this because of the current bug:
"...when you co-manage devices by using Configuration Manager and Intune, there is a limitation where feature update policies may not immediately take effect. This limitation causes devices to update to a later feature update than the one that's configured in Intune. This limitation will be removed in a future update to Configuration Manager"
If so, then we will have to disable that possibilty until it's fixed to avoid workstations upgrading to another build than what we've specified or see if the workaround works
https://docs.microsoft.com/en-us/troubleshoot/mem/intune/create-feature-update-hold-co-managed-devices#set-the-targetreleaseversion-policy
Thks for sharing the workaround
MicrosoftIlalanc01 Unfortunately, it could be due to the delay. I'd recommend pausing feature updates or leveraging deferrals for the first 2 days after setting the feature preview policy and the removing pause/deferrals once the policy has time to take effect - just to ensure devices aren't impacted by any latency.
AriaUpdated I thought that when we use the 'Windows 10 feature updates' policy that we needed to set the FU deferal to zero.
Does that mean that we can set the FU deferal to 2 days and still use the 'Windows 10 feature updates' policies to lock a device in a specific build?
thks
- AriaUpdated
lalanc01 today the reason the recommendation is to not use both is because today deferrals will still apply if you leverage Feature Updates (Preview) in Intune. This means if you have a 365 day deferral and have configured 20H2 as your target version, you will not be offered 20H2 until your 365 day deferral elapses (aka when 20H2 is 1 year old).
Note - we are working to ensure that deferrals are not applied in future, but that is the current state.