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

Merge pull request #7814 from tiaraquan/ap-updates-020123-1

Browse Source 
Tweaks based on feedback
This commit is contained in:
Tiara Quan 2023-02-01 11:49:31 -08:00 committed by GitHub
commit 3b30d2cf56
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 21 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
windows/deployment/windows-autopatch/TOC.yml
View File

@ -54,6 +54,8 @@
href: operate/windows-autopatch-wqu-end-user-exp.md
- name: Windows quality update signals
href: operate/windows-autopatch-wqu-signals.md
- name: Windows quality update communications
href: operate/windows-autopatch-wqu-communications.md
- name: Windows quality update reports
href: operate/windows-autopatch-wqu-reports-overview.md
items:
@ -72,8 +74,6 @@
items:
- name: Windows feature update end user experience
href: operate/windows-autopatch-fu-end-user-exp.md
- name: Windows quality and feature update communications
href: operate/windows-autopatch-wqu-communications.md
- name: Microsoft 365 Apps for enterprise
href: operate/windows-autopatch-microsoft-365-apps-enterprise.md
- name: Microsoft Edge

11
windows/deployment/windows-autopatch/operate/windows-autopatch-fu-end-user-exp.md
View File

@ -51,7 +51,16 @@ The deadline specified in the update policy is five days. Therefore, once this d
In the following example, the user is on holiday and the device is offline beyond the feature update deadline. The user then returns to work and the device is turned back on.
Since the deadline has already passed, the device is granted a two-day grace period to install the update and restart. The user will be notified of a pending installation and given options to choose from. Once the two-day grace period has expired, the user is forced to restart with a 15-minute warning notification.
The grace period to install the update and restart depends on the deployment ring the device is assigned to:
| Deployment ring | Grace period (in days) |
| ----- | ----- |
| Test | Zero days |
| First | Two days |
| Fast | Two days |
| Broad | Two days |
The user will be notified of a pending installation and given options to choose from. Once the grace period has expired, the user is forced to restart with a 15-minute warning notification.
:::image type="content" source="../media/windows-feature-update-grace-period.png" alt-text="Windows feature update grace period" lightbox="../media/windows-feature-update-grace-period.png":::

12
windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-communications.md
View File

@ -1,5 +1,5 @@
---
title: Windows quality and feature update communications
title: Windows quality update communications
description: This article explains Windows quality update communications
ms.date: 05/30/2022
ms.prod: windows-client
@ -12,7 +12,7 @@ manager: dougeby
msreviewer: hathind
---
# Windows quality and feature update communications
# Windows quality update communications
There are three categories of communication that are sent out during a Windows quality and feature update:
@ -20,7 +20,11 @@ There are three categories of communication that are sent out during a Windows q
- [Communications during release](#communications-during-release)
- [Incident communications](#incident-communications)
Communications are posted to Message center, Service health dashboard, and the Windows Autopatch messages section of the Microsoft Endpoint Manager admin center as appropriate for the type of communication.
Communications are posted to, as appropriate for the type of communication, to the:
- Message center
- Service health dashboard
- Windows Autopatch messages section of the Microsoft Endpoint Manager admin center
:::image type="content" source="../media/update-communications.png" alt-text="Update communications timeline" lightbox="../media/update-communications.png":::
@ -42,4 +46,4 @@ For example, new threat intelligence may require us to expedite a release, or we
## Incident communications
Despite the best intentions, every service should plan for failure and success. When there's an incident, timely and transparent communication is key to building and maintaining your trust. If insufficient numbers of devices have been updated to meet the service level objective, devices will experience an interruption to productivity and an incident will be raised. Microsoft will update the status of the incident at least once every 24 hours.
Despite the best intentions, every service should plan for failure and success. When there's an incident, timely and transparent communication is key to building and maintaining your trust. If insufficient numbers of devices have been updated to meet the service level objective, devices will experience an interruption to productivity, and an incident will be raised. Microsoft will update the status of the incident at least once every 24 hours.

2
windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-signals.md
View File

@ -56,4 +56,4 @@ Autopatch monitors the following reliability signals:
| Microsoft Edge reliability | Tracks the number of Microsoft Edge crashes and freezes per device. |
| Microsoft Teams reliability | Tracks the number of Microsoft Teams crashes and freezes per device. |
When the update is released to the First ring, the service crosses the 500 device threshold. Therefore, Autopatch can to detect regressions, which are common to all customers. At this point in the release, we'll decide if we need to change the release schedule or pause for all customers.
When the update is released to the First ring, the service crosses the 500 device threshold. Therefore, Autopatch can detect regressions that are common to all customers. At this point in the release, we'll decide if we need to change the release schedule or pause for all customers.