-
- | Category |
- Maximum deferral |
- Deferral increments |
- Example |
- Classification GUID |
-
-
- | Feature Updates |
- 180 days |
- Days |
- From Windows 10, version 1511 to version 1607 |
- 3689BDC8-B205-4AF4-8D4A-A63924C5E9D5 |
-
-
- | Quality Updates |
- 30 days |
- Days |
- Security updates |
- 0FA1201D-4330-4FA8-8AE9-B877473B6441 |
-
-
- | Drivers (optional) |
- EBFC1FC5-71A4-4F7B-9ACA-3B9A503104A0 |
-
-
- | Non-security updates |
- CD5FFD1E-E932-4E3A-BF74-18BF0B1BBD83 |
-
| Microsoft updates (Office, Visual Studio, etc.) | varies |
-
- | Non-deferrable |
- No deferral |
- No deferral |
- Definition updates |
- E0789628-CE08-4437-BE74-2495B842F43B |
-
-
+In this example, some problem is discovered during the deployment of the update to the "pilot" ring.
-9. Close the Group Policy Management Editor.
+
-Because the **Windows Update for Business – CB2** GPO contains a computer policy and you only want to apply it to computers in the **Ring 2 Pilot Business Users** group, use **Security Filtering** to scope the policy’s effect.
+At this point, the IT administrator can set a policy to pause the update. In this example, the admin selects the **Pause quality updates** check box.
-### Scope the policy to the Ring 2 Pilot Business Users group
+
-1. In the GPMC, select the **Windows Update for Business - CB2** policy.
+Now all devices are paused from updating for 35 days. When the the pause is removed, they will be offered the *next* quality update, which ideally will not have the same issue. If there is still an issue, the IT admin can pause updates again.
-2. In **Security Filtering** on the **Scope** tab, remove the default **AUTHENTICATED USERS** security group, and add the **Ring 2 Pilot Business Users** group.
- 
-The **Ring 2 Pilot Business Users** deployment ring has now been configured. Next, configure **Ring 4 Broad business users** to set those clients into the CBB servicing branch so that they receive feature updates as soon as they’re made available for the CBB servicing branch.
+#### Set branch readiness level for feature updates
-### Configure Ring 4 Broad business users policy
+This policy only applies to feature updates. To enable preview builds for devices in your organization, set the "Enable preview builds" policy and then use the "Select when preview builds and feature updates are received" policy.
-1. Open GPMC (gpmc.msc).
+We recommend that you set up a ring to receive preview builds by joining the Windows Insider Program for Business. By having a ring of devices receiving "pre-release slow" builds and learning about commercial pre-release features, you can ensure that any issues you have with the release are fixed before it is ever released and far before you broadly deploy.
-2. Expand **Forest** > **Domains** > *your domain*.
+- Enable preview builds: **Computer configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business > Manage Preview Builds**
-3. Right-click *your domain* and select **Create a GPO in this domain, and Link it here**.
-4. In the **New GPO** dialog box, type **Windows Update for Business - CBB1** for the name of the new GPO.
-
-5. Right-click the **Windows Update for Business - CBB1** GPO, and then click **Edit**.
-
-6. In the Group Policy Management Editor, go to **Computer Configuration** > **Policies** > **Administrative Templates** > **Windows Components** > **Windows Update** > **Defer Windows Updates**.
-7. Right-click **Select when Feature Updates are received**, and then click **Edit**.
+- Set branch readiness level: **Computer configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business > Select when Preview Builds and Feature Updates are Received**
-8. In the **Select when Feature Updates are received** policy, enable it, select a branch readiness level of **CBB**, and then click **OK**.
- 
-9. Close the Group Policy Management Editor.
-
-### Scope the policy to the Ring 4 Broad business users group
-
-1. In the GPMC, select the **Windows Update for Business - CBB1** policy.
-
-2. In **Security Filtering** on the **Scope** tab, remove the default **AUTHENTICATED USERS** security group, and add the **Ring 4 Broad business users** group.
-
-
-The **Ring 4 Broad business users** deployment ring has now been configured. Finally, configure **Ring 5 Broad business users #2** to accommodate a 7-day delay for quality updates and a 14-day delay for feature updates
-
-### Configure Ring 5 Broad business users \#2 policy
-
-1. Open GPMC (gpmc.msc).
-
-2. Expand **Forest** > **Domains** > *your domain*.
-
-3. Right-click *your domain* and select **Create a GPO in this domain, and Link it here**.
-
-4. In the **New GPO** dialog box, type **Windows Update for Business - CBB2** for the name of the new GPO.
-
-5. Right-click the **Windows Update for Business - CBB2** GPO, and then click **Edit**.
-
-6. In the Group Policy Management Editor, go to **Computer Configuration** > **Policies** > **Administrative Templates** > **Windows Components** > **Windows Update** > **Defer Windows Updates**.
-
-7. Right-click **Select when Feature Updates are received**, and then click **Edit**.
-
-8. In the **Select when Feature Updates are received** policy, enable it, select a branch readiness level of **CBB**, set the feature update delay to **14** days, and then click **OK**.
-
- 
-
-9. Right-click **Select when Quality Updates are received**, and then click **Edit**.
-
-10. In the **Select when Quality Updates are received** policy, enable it, set the quality update delay to **7** days, and then click **OK**.
-
- 
-
-11. Close the Group Policy Management Editor.
-
-
-
-### Scope the policy to the Ring 5 Broad business users \#2 group
-
-1. In the GPMC, select the **Windows Update for Business - CBB2** policy.
-
-2. In **Security Filtering** on the **Scope** tab, remove the default **AUTHENTICATED USERS** security group, and add the **Ring 5 Broad business users #2** group.
-
-## Known issues
-The following article describes the known challenges that can occur when you manage a Windows 10 Group policy client base:
-- [Known issues managing a Windows 10 Group Policy client in Windows Server 2012 R2](https://support.microsoft.com/help/4015786/known-issues-managing-a-windows-10-group-policy-client-in-windows-serv)
-
## Related topics
- [Update Windows 10 in the enterprise](index.md)
@@ -371,3 +142,8 @@ The following article describes the known challenges that can occur when you man
- [Deploy Windows 10 updates using Windows Server Update Services](waas-manage-updates-wsus.md)
- [Deploy Windows 10 updates using System Center Configuration Manager](waas-manage-updates-configuration-manager.md)
- [Manage device restarts after updates](waas-restart.md)
+
+
+
+
+