windows-itpro-docs/windows/plan/setup-and-deployment.md
jdeckerMS 4a6e83b81f Squashed commit of the following:
commit 8329185a7e5119d2a43a9606a8e3476fba8a3846
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Sep 21 09:08:15 2016 -0700

    tweak

commit 99d0961d0148578322908ade9862f8b45d045e32
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Sep 21 09:04:55 2016 -0700

    updates for pushing live

commit affc30449b7656ed0871e106620d16a0c2ce9c06
Merge: 0dd8a59 1dce84a
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Sep 21 08:59:51 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdwaas

commit 0dd8a5995efdc62da387f53a141b021ebaccbf91
Merge: 2aceee2 cb28398
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Sep 21 07:21:00 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdwaas

commit 2aceee2831067b9b338484d86ac7cdf5a25b0e58
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Sep 14 12:58:03 2016 -0700

    waas-wsus.fig9

commit 7a826aa540b40e69b9da963f486aecc3fdb3816a
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Sep 14 12:36:31 2016 -0700

    re-save each image

commit b700ba2cf3b70e49537b3dd313575aba90a448b6
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Sep 14 12:18:34 2016 -0700

    testing new fix

commit 30c3353173ffcfd40affed79ceb74ce029a6492a
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Sep 14 12:10:17 2016 -0700

    rename images

commit a7995ca7999303215616fc6c197677bfc91589e9
Merge: 4b77449 e262949
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Sep 14 11:54:28 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdwaas

commit 4b77449f242ceb1a3bbd87cc8003ffa119b6b75d
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Sep 14 11:52:21 2016 -0700

    renamed image file

commit 741fab2cf53e1558227a62c5b3422e472acab88d
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Sep 14 11:42:33 2016 -0700

    troubleshooting images

commit 521cb7e1f9701b9de29414c12e918992d8afb7d5
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Sep 14 11:30:59 2016 -0700

    add art

commit d65533c3ac4c0880fa2f75030c9ec1bbc49c8840
Merge: d9f0c9c bd846ca
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Sep 14 11:08:43 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdwaas

commit d9f0c9cd1acfc0caf3c94e62d23cefc38aa06dac
Merge: 60cc5a5 ffab5db
Author: Elizabeth Ross <lizross@microsoft.com>
Date:   Wed Sep 14 07:35:13 2016 -0700

    Merge pull request #182 from mtniehaus/patch-5

    Update waas-update-windows-10.md

commit 60cc5a58149ffbb219b34a87eae3d67b132b45f5
Merge: 7efbed7 cd4c88a
Author: Elizabeth Ross <lizross@microsoft.com>
Date:   Wed Sep 14 07:35:02 2016 -0700

    Merge pull request #183 from mtniehaus/patch-6

    Update waas-overview.md

commit cd4c88aeebc893f64bf6517c23edff9516c8b94c
Author: Michael Niehaus <niehaus@live.com>
Date:   Tue Sep 13 22:57:17 2016 -0700

    Update waas-overview.md

    Fixed up wording, changed to "two to three times per year", added "minimum of 18 months" text.

commit ffab5dbdf6ba91ae7bf271f6958aed0c5a116070
Author: Michael Niehaus <niehaus@live.com>
Date:   Tue Sep 13 21:19:42 2016 -0700

    Update waas-update-windows-10.md

    Fixing the text in the first paragraph to remove PR objections and to make it sound less like "cheery marketing" content.

commit 7efbed7a79b212cb04dcae298e0ab1da977b7c20
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Sep 13 10:27:36 2016 -0700

    8807924

commit 27926055ea9eeb082d731dcb91cd043cd996ccbf
Merge: 49b877a d048580
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Sep 13 10:03:31 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdwaas

commit 49b877aa73957f9aba369e0bb3d69c408200be18
Merge: 91dc45b 7d1348e
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Sep 13 07:24:02 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdwaas

commit 91dc45bcd571532aeddceff775a401d727ec74e6
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Sep 1 11:21:52 2016 -0700

    change pixel size

commit f2aa45f0f1806a4d6208c2d66a1b897dfd5a9c85
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Sep 1 11:19:23 2016 -0700

    2d tweak

commit fac4a1c9d58b7c176732235db37a2c4fa37d269d
Merge: d05c373 d075214
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Sep 1 11:15:10 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdwaas

commit d05c373be521d0b1a4f908ff34729e069d3783ee
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Sep 1 11:13:57 2016 -0700

    tweak width

commit 7c5de66b7a7b5454bf49fed42ae0cc94ddc4f51a
Merge: b71bfe5 decfdee
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Sep 1 11:12:16 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdwaas

commit b71bfe57fe1d55e23e303d92f572d8c07c19ebb8
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Sep 1 07:49:05 2016 -0700

    add link to Upgrade Analytics

commit 04fb2371a6be88f014f75bff39b263098f721170
Merge: b152ae6 1995a49
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Sep 1 07:36:48 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdwaas

commit b152ae60eceefd237984a8acbdc8a6a7bd3f2dae
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Sep 1 07:22:09 2016 -0700

    add LTSB note

commit ef94546e0e457ad86bbbfb77432be2dae5896de5
Merge: ba5399a 48b4b10
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Aug 30 17:51:03 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdwaas

    # Conflicts:
    #	windows/manage/index.md

commit ba5399abc0161d877650915e326e70bdeef7309f
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Aug 30 17:28:17 2016 -0700

    put waas content back in
2016-09-21 09:26:02 -07:00

9.9 KiB
Raw Blame History

title, description, ms.assetid, keywords, ms.prod, ms.mktglfcycl, ms.sitesec, ms.pagetype, author, redirect_url
title description ms.assetid keywords ms.prod ms.mktglfcycl ms.sitesec ms.pagetype author redirect_url
Setup and deployment (Windows 10) This article describes the basic features of a Windows Update for Business deployment. E176BB36-3B1B-4707-9665-968D80050DD1 update, upgrade, deployment w10 plan library servicing, devices jdeckerMS https://technet.microsoft.com/en-us/itpro/windows/manage/waas-manage-updates-wufb

Setup and deployment

Applies to

  • Windows 10

This article describes the basic features of a Windows Update for Business deployment. Use this information to familiarize yourself with a simple deployment with a single group of machines connected to Windows Update, in addition to more complex scenarios such as the creation of Windows Update for Business validation groups that receive updates from Windows Update at different time intervals, as well as Windows Update for Business deployments integrated with existing management tools such as Windows Server Update Services (WSUS), System Center Configuration Manager, or Microsoft Intune.

Configure your systems to receive updates on CBB

To use Windows Update for Business, Windows 10-based devices must first be configured for the Current Branch for Business (CBB). You can configure devices manually, by using Group Policy, or by using mobile device management (MDM).

figure 1

figure 2

figure 3

Defer OS upgrade and update deployments

Windows Update for Business allows administrators to control when upgrades and updates are deployed to their Windows 10 clients by specifying deferral windows from when they are initially made available on the Windows Update service. As mentioned, there are restrictions as to how long you can delay upgrades and updates. The following table details these restrictions, per deployment category type:

Group Policy keys

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate\DeferUpgradePeriod

  • Values: 0-8 where each unit for upgrade is a month

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate\DeferUpdatePeriod

  • Values: 0-4 where each unit for update is a week

MDM

./Vendor/MSFT/Update/DeferUpgrade

Software\Microsoft\PolicyManager\current\Update\RequireDeferUpgrade

  • Values: 0-8 where each unit for upgrade is a month

Software\Microsoft\PolicyManager\current\Update\RequireDeferUpdate

  • Values: 0-4 where each unit for update is a week

  Administrators can control deferral periods with Group Policy Objects by using the [Local Group Policy Editor (GPEdit)](https://go.microsoft.com/fwlink/p/?LinkId=734030) or, for domain joined systems, [Group Policy Management Console (GPMC)](https://go.microsoft.com/fwlink/p/?LinkId=699325). For additional details on Group Policy management see [Group Policy management for IT pros](https://go.microsoft.com/fwlink/p/?LinkId=699282). **Set different deferrals based on update classification in GPedit.msc** ![figure 4](images/wuforbusiness-fig4-localpoleditor.png) ![figure 5](images/wuforbusiness-fig5-deferupgrade.png) ## Pause upgrades and updates Although administrators can use deferral periods to stagger the rate at which deployments go out to their organization (which provides time to verify quality and address any issues), there may be cases where additional time is needed before an update is set to deploy to a machine, or group of machines. Windows Update for Business provides a means for administrators to *pause* updates and upgrades on a per-machine basis. This pause functionality ensures that no updates or upgrades will be made available for the specified machine; the machine will remain in this state until the machine is specifically “unpaused”, or when a period of five weeks (35 days) has passed, at which point updates are auto-resumed. **Note**   The five-week period ensures that pause functionality overlaps a possible subsequent Update Tuesday release.   **Note**   Group Policy does not allow you to set a future "unpause” — administrators must actively select to unpause a deployment if they wish to do so before the time expiration.  

Group Policy keys

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate\Pause

MDM

./Vendor/MSFT/Update/DeferUpgrade

Software\Microsoft\PolicyManager\current\Update\Pause

  • Values (bool): 0, 1

  ![figure 6](images/wuforbusiness-fig6-pause.png)

Create validation groups for deployments

By grouping machines into similar deferral periods, administrators are able to cluster devices into deployment or validation groups which can be used as a quality control measure as updates are deployed in Windows 10. With deferral windows and the ability to pause, administrators can effectively control and measure update deployments by rolling out to a small pool of devices first to verify quality, prior to a broader roll-out to their organization.

Administrators can establish validation groups to maintain a level of control over update/driver deployments which allows them to:

  • Control the date, time, and frequency updates will be applied and devices rebooted
  • Deploy a small set of machines to verify quality prior to broad roll-out
  • Stage broad roll-out in waves to continue quality verification and minimize disruptions
  • Manage membership of waves based on criteria defined by IT
  • Halt and roll-back deployment of updates/drivers that may be causing trouble

figure 7

Peer-to-peer networking for deployments

Windows Update Delivery Optimization enables Windows Update for Business enrolled devices to download Windows updates and Windows Store apps from sources other than Microsoft. With multiple devices, Delivery Optimization can reduce the amount of Internet bandwidth that is required to keep all of your Windows Update for Business enrolled systems up to date. It can also help ensure that devices get updates and apps more quickly if they have a limited or unreliable Internet connection.

In addition to downloading updates and apps from Microsoft, Windows will get updates and apps from other PCs that already have them. You can choose which PCs you get these updates from.

How Delivery Optimization works

  • PCs on your local network. When Windows downloads an update or app, it will look for other PCs on your local network that have already downloaded the update or app using Delivery Optimization. Windows then downloads parts of the file from those PCs and parts of the file from Microsoft. Windows doesnt download the entire file from one place. Instead, the download is broken down into smaller parts. Windows uses the fastest, most reliable download source for each part of the file.
  • PCs on your local network and PCs on the Internet. Windows uses the same process as when getting updates and apps from PCs on your local network, and also looks for PCs on the Internet that can be used as a source to download parts of updates and apps.

Delivery Optimization settings

Delivery Optimization is turned on by default for the Enterprise and Education editions of Windows 10, where the default option is that updates will only be pulled and shared from PCs on your LAN and not the Internet. Delivery Optimization configuration settings can be viewed by going to: Settings > Update and Security > Advanced Options > Choose how your updates are delivered

figure 8

Use Group Policy to configure Windows Update Delivery Optimization

You can use Group Policy to configure Windows Update Delivery Optimization. To do this, use the following steps:

  1. Download the Administrative Templates (.admx) file for Windows 10 from the Microsoft Download Center.

  2. Copy the following files to the SYSVOL central store:

    • DeliveryOptimization.admx from C:\Program Files (x86)\Microsoft Group Policy\Windows 10\PolicyDefinitions
    • DeliveryOptimization.adml from C:\Program Files (x86)\Microsoft Group Policy\Windows 10\PolicyDefinitions\en-US
  3. Start the Gpeditor tool.

  4. Browse to the following location:

    • Computer Configuration\Administrative Templates\Windows Components\Delivery Optimization
  5. Make the following Windows Update Delivery Optimization settings, as appropriate.

    figure 9

Virus-scan claim

Microsoft scanned this file for viruses, using the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to it.

For more information about Windows Update Delivery Optimization in Windows 10, see the Windows Update Delivery Optimization FAQ.

For additional resources, see How to use Group Policy to configure Windows Update Delivery Optimization in Windows 10.

Windows Update for Business

Integration with management solutions