Windows Update for Business Group Policy Setting

COG1.pngMicrosoft has now release the new ADMX pack for Windows 10 1511 (Threshold 2). What is notable about this release is that is has the Group Policy setting “Defer Upgrade and Updates” which is the policy that enabled the Windows Update for Business feature.

WUFB

 

 

 

 

 

 

This policy setting can be found under the “Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Update”. To enable the new policy setting install download the Windows10_Version_1511_ADMX.msi from  http://www.microsoft.com/en-us/download/details.aspx?id=48257  and then copy the PolicyDefnitions folder over top of your Group Policy central store.

To use the setting simply configured the “Defer upgrade for the following duration” to the number of months you wish to defer the upgrade to the latest OS build. The “Defer updated for the following duration” is another option to delay the installation of security patches. Unlike the “Defer Upgrades” option “Defer updated” can only be deferred weeks based on their critical nature.

Also note, these policy setting are only applicable to computers that are configured to use Windows Updated as a source for patches. Updates that are delivered in corporates using WSUS are still controlled via the more traditional approve/deny within the tools itself.

Then to target the different levels of policy setting using my How to apply a Group Policy Object to individual users or computer or setup multiple test groups as per my other post  Group Policy for WSUS

Author: Alan Burchill

Microsoft MVP (Group Policy)

11 thoughts on “Windows Update for Business Group Policy Setting

  1. After the upgrade and replacement files in “PolicyDefinitions”.
    on windows 2012 server
    +Windows8.1-Server2012R2ADMX-RTM.msi
    +Windows10-ADMX.msi
    +Windows10_Version_1511_ADMX.msi
    Getting the error “Name space ‘Microsoft.Policies.WindowsStore'” is already defined as the target namespace for another file in the store”. See file winstoreui.admx line 4, column 80.

    who knows how to fix?

    1. Deleting the WinStoreUI.admx & WinStoreUI.adml from my PolicyDefinitions folder fixed it for me. Those files appear to conflict with the new WindowsStore.admx & WindowsStore.adml files. The new files appear to have all the same settings plus a few more. The settings appear in “Administrative Templates > Windows Components > Store” for both User and Computer Configuration.

  2. The following ADMX are Removed with Version 1511:
    microsoft-windows-geolocation-wlpadm.admx
    parentalcontrols.admx

Leave a Reply to AndreyCancel reply