deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-13 05:47:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Removed guidance causing dual scan in SCCM

Browse Source
This commit is contained in:
Dani Halfin 2017-04-13 14:06:13 -07:00
parent 7442235ff2
commit eee3044ebb
1 changed files with 0 additions and 77 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

77
windows/update/waas-manage-updates-configuration-manager.md
View File

@ -48,83 +48,6 @@ For the Windows 10 servicing dashboard to display information, you must adhere t
When you have met all these requirements and deployed a servicing plan to a collection, you’ll receive information on the Windows 10 servicing dashboard. When you have met all these requirements and deployed a servicing plan to a collection, you’ll receive information on the Windows 10 servicing dashboard.
## Enable CBB clients in Windows 10, version 1511
When you use System Center Configuration Manager to manage Windows 10 servicing, you must first set the **Defer Updates or Upgrades** policy on the clients that should be on the Current Branch for Business (CBB) servicing branch so that you can use CBB servicing plans from Configuration Manager. You can do this either manually or through Group Policy. If you don’t set this policy, Configuration Manager discovers all clients, as it would in Current Branch (CB) mode.
**To use Group Policy to configure a client for the CBB servicing branch**
>[!NOTE]
>In this example, a specific organizational unit (OU) called **Windows 10 – Current Branch for Business Machines** contains the Windows 10 devices that should be configured for CBB. You can also use a security group to filter the computers to which the policy should be applied.
1. On a PC running the Remote Server Administration Tools or on a domain controller, open Group Policy Management Console (GPMC).
2. Expand Forest\Domains\\*Your_Domain*.
4. Right-click the **Windows 10 – Current Branch for Business Machines** OU, and then click **Create a GPO in this domain, and Link it here**.
![Example of UI](images/waas-sccm-fig2.png)
5. In the **New GPO** dialog box, type **Enable Current Branch for Business** for the name of the new GPO.
>[!NOTE]
>In this example, you’re linking the GPO to a specific OU. This is not a requirement. You can link the Windows Update for Business GPOs to any OU or the top-level domain, whichever is appropriate for your Active Directory Domain Services (AD DS) structure.
6. Right-click the **Enable Current Branch for Business** GPO, and then click **Edit**.
7. In the Group Policy Management Editor, go to Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Update.
8. Right-click the **Defer Upgrades and Updates** setting, and then click **Edit**.
![Example of UI](images/waas-sccm-fig3.png)
9. Enable the policy, and then click **OK**.
>[!NOTE]
>The additional options in this setting are only for Windows Update for Business, so be sure not to configure them when using System Center Configuration Manager for Windows 10 servicing.
10. Close the Group Policy Management Editor.
This policy will now be deployed to every device in the **Windows 10 – Current Branch for Business Machines** OU.
## Enable CBB clients in Windows 10, version 1607
When you use Configuration Manager to manage Windows 10 servicing, you must first set the **Select when Feature Updates** are received policy on the clients that should be on the CBB servicing branch so that you can use CBB servicing plans from Configuration Manager. You can do this either manually or through Group Policy. If you don’t set this policy, Configuration Manager discovers all clients, as it would in CB mode.
>[!NOTE]
>System Center Configuration Manager version 1606 is required to manage devices running Windows 10, version 1607.
**To use Group Policy to configure a client for the CBB servicing branch**
>[!NOTE]
>In this example, a specific organizational unit (OU) called **Windows 10 – Current Branch for Business Machines** contains the Windows 10 devices that should be configured for CBB. You can also use a security group to filter the computers to which the policy should be applied.
1. On a PC running the Remote Server Administration Tools or on a domain controller, open GPMC.
2. Expand Forest\Domains\\*Your_Domain*.
3. Right-click the **Windows 10 – Current Branch for Business Machines** OU, and then click **Create a GPO in this domain, and Link it here**.
![Example of UI](images/waas-sccm-fig2.png)
5. In the **New GPO** dialog box, type **Enable Current Branch for Business** for the name of the new GPO.
>[!NOTE]
>In this example, you’re linking the GPO to a specific OU. This is not a requirement. You can link the Windows Update for Business GPOs to any OU or the top-level domain, whichever is appropriate for your Active Directory Domain Services (AD DS) structure.
6. Right-click the **Enable Current Branch for Business** GPO, and then click **Edit**.
7. In the Group Policy Management Editor, go to Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Update\Defer Windows Updates.
8. Right-click the **Select when Feature Updates are received** setting, and then click **Edit**.
9. Enable the policy, select the **CBB** branch readiness level, and then click **OK**.
10. Close the Group Policy Management Editor.
This policy will now be deployed to every device in the **Windows 10 – Current Branch for Business Machines** OU.
## Create collections for deployment rings ## Create collections for deployment rings
Regardless of the method by which you deploy Windows 10 feature updates to your environment, you must start the Windows 10 servicing process by creating collections of computers that represent your deployment rings. In this example, you create two collections: **Windows 10 – All Current Branch for Business** and **Ring 4 Broad business users**. You’ll use the **Windows 10 – All Current Branch for Business** collection for reporting and deployments that should go to all CBB clients. You’ll use the **Ring 4 Broad business users** collection as a deployment ring for the first CBB users. Regardless of the method by which you deploy Windows 10 feature updates to your environment, you must start the Windows 10 servicing process by creating collections of computers that represent your deployment rings. In this example, you create two collections: **Windows 10 – All Current Branch for Business** and **Ring 4 Broad business users**. You’ll use the **Windows 10 – All Current Branch for Business** collection for reporting and deployments that should go to all CBB clients. You’ll use the **Ring 4 Broad business users** collection as a deployment ring for the first CBB users.