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

deleted draft files that got absorbed into manage-updates

Browse Source
This commit is contained in:
jaimeo 2020-05-26 12:45:42 -07:00
parent aacff08726
commit 110f715cf2
2 changed files with 0 additions and 85 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
windows/deployment/update/waas-wufb-end-user.md
View File

@ -1,28 +0,0 @@
---
title: Manage the end-user experience with updates
ms.reviewer:
manager: laurawi
description: Windows Update for Business lets you manage when devices received updates from Windows Update.
ms.prod: w10
ms.mktglfcycl: manage
author: jaimeo
ms.localizationpriority: medium
ms.author: jaimeo
ms.topic: article
---
# Manage the end-user experience
Windows Update for Business provides controls to help meet your organization’s security standards as well as provide a great end-user experience. You can do this by setting automatic updates to occur at times that work well for those in your organization, setting deadlines for quality and feature updates, etc {if we could list a third thing instead of "etc." it would read better}. For the best experience, it is usually better to employ fewer controls. {are we trying to say "set as few of these as possible"?}
## Recommended settings for the end-user experience
Features such as smart busy check, ensuring that we don’t update when the user is logged on, and configurable active hours help keep devices secure while preserving a great user experience. Follow these steps to take advantage of these features: {not sure I'm really understanding these steps--given the intro, I'd expect to see more specific steps. Some of the "steps" seem to be settings, but one is an action?}
1. Automatically download, install, and restart (default if no restart policies are configured or enabled)
2. Use the default notifications
3. Set update deadlines
## Set Deadlines
The compliance deadline policy {keep the topic we already have on this (https://docs.microsoft.com/en-us/windows/deployment/update/wufb-compliancedeadlines) and link to it from here maybe?} released in June 2019 enables the IT admin to set separate deadlines and grace periods for feature and quality updates. This policy enables you to specify the number of days after an update is published by which a device must install the update. The policy also includes a configurable grace period that specifies the number of days from when the update is installed on the device to when the device is forced to restart. This is extremely beneficial in a vacation scenario as it allows, for example, users who have been away to have a bit of time before being forced to restart devices when they return from vacation.

57
windows/deployment/update/waas-wufb-when.md
View File

@ -1,57 +0,0 @@
---
title: Manage when Windows Update for Business updates are offered
ms.reviewer:
manager: laurawi
description: Windows Update for Business lets you manage when devices received updates from Windows Update.
ms.prod: w10
ms.mktglfcycl: manage
author: jaimeo
ms.localizationpriority: medium
ms.author: jaimeo
ms.topic: article
---
# Manage when updates are offered
By grouping devices into different deployment groups, you can control the deployment of updates in waves by setting up different branch readiness levels and update deferral policies for each group. All updates from Windows Update include built-in compatibility checks to prevent against a poor update experience for your devices as well as a check to prevent repeated rollbacks.
## Enroll in a pre-release branch
You control which release channel for feature updates by setting the branch readiness level. Today, you can only select pre-release branches for feature updates.
Currently there are four branch readiness levels:
- Windows Insider Program for Business (for pre-release updates)
- Windows Insider Fast
- Windows Insider Slow
- Windows Insider Release Preview {isn't this also pre-release by definition?}
- Semi-annual Channel
> [!NOTE]
> Prior to Windows 10, version 1903, there were two channels for released updates: Semi-annual Channel and Semi-annual Channel (Targeted). Starting with Windows 10, version 1903 there is only the one release channel: Semi-annual Channel.
You can set the branch readiness level by using the **Select when Preview Builds and Feature Updates are Received** policy. In order to use this to manage pre-release builds, first enable preview builds by using the **Manage preview Builds** policy.
## Defer an update
A Windows Update for Business administrator {is this a formal role name?} can defer the installation of both feature and quality updates on devices within a bounded range of time from when those updates are first made available on the Windows Update service. You can use this deferral to allow time to validate deployments before they are installed on devices. Deferrals work by allowing you to specify the number of days after an update is released before it is offered to a device. For example, if you set a feature update deferral period of 365 days, the device will not install a feature update that has been released for less than 365 days. To defer feature updates use the **Select when Preview Builds and Feature Updates are Received** policy. The maximum deferral period differs by the type of update. Certain updates cannot be deferred. {can we give any examples of those?}
|Update type |Maximum deferral |
|---------|---------|
|Feature updates | 365 days |
|Quality updates | 30 days |
|Non-deferrable updates | none |
All deferral days are calculated from the date a release is offered in the Semi-annual Channel. See [Windows Release Information](https://docs.microsoft.com/windows/release-information/) for these dates.
{Example: Using deferrals to deploy in waves
[Insert graphic with the deferrals set to different values showing a feature update rollout)}
## Pause an update
If you discover a problem while deploying a feature or quality update, the IT administrator can pause the update for 35 days from a specified start date to prevent other devices from installing it until the issue is mitigated.
If you pause a feature update, quality updates are still offered to devices to ensure they stay secure. The pause period for both feature and quality updates is calculated from a start date that you set.