Replies: 1 comment
-
|
There's a few settings have have been removed from the WUfB ring policy over time, yes. Another one that springs to mind is the one relating to Preview Builds, which can trigger a reboot between device and user ESP phases. The fix is to create a new update policy. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Win - OIB - SC - Windows Update for Business - D - Delivery Optimisation - v3.0 can return a conflict with Windows Update Rings for the 'DO Download Mode' setting if you use an old update ring.
We have an update ring that was created in 2018 (that we just renamed for the purpuse of setting up OIB) which includes the setting 'WindowsUpdateForBusinessConfiguration.DeliveryOptimizationMode' and causes a conflict, while new ones created in 2023 and 2025 omit this setting. I'm not entirely sure when Microsoft removed this, but some time after 2018 at least. This shouldn't happen if you use the OIB scripts, but if you have old update rings set up, you could run into this scenario. The setting is not visible in the update ring settings GUI and cannot be changed for an existing policy.
Old policy:

vs. new:

Workaround: Recreate the update ring and reassign groups to use the new policy, alternatively remove the 'DO Download mode' from your local Delivery Optimization policy.
Beta Was this translation helpful? Give feedback.
All reactions