mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-21 21:33:38 +00:00
Merge branch 'main' into ADO-9517656-Update-for-Business
This commit is contained in:
Gary Moore
@ -116,8 +116,6 @@
|
||||
href: monitor/windows-autopatch-windows-quality-update-status-report.md
|
||||
- name: Quality update trending report
|
||||
href: monitor/windows-autopatch-windows-quality-update-trending-report.md
|
||||
- name: Reliability report
|
||||
href: monitor/windows-autopatch-reliability-report.md
|
||||
- name: Hotpatch quality update report
|
||||
href: monitor/windows-autopatch-hotpatch-quality-update-report.md
|
||||
- name: Windows feature and quality update device alerts
|
||||
|
||||
@ -1,122 +0,0 @@
|
||||
---
|
||||
title: Reliability report
|
||||
description: This article describes the reliability score for each Windows quality update cycle based on stop error codes detected on managed devices.
|
||||
ms.date: 04/09/2024
|
||||
ms.service: windows-client
|
||||
ms.subservice: autopatch
|
||||
ms.topic: how-to
|
||||
ms.localizationpriority: medium
|
||||
author: tiaraquan
|
||||
ms.author: tiaraquan
|
||||
manager: aaroncz
|
||||
ms.reviewer: hathind
|
||||
ms.collection:
|
||||
- highpri
|
||||
- tier1
|
||||
---
|
||||
|
||||
# Reliability report (public preview)
|
||||
|
||||
[!INCLUDE [windows-autopatch-enterprise-e3-f3-licenses](../includes/windows-autopatch-enterprise-e3-f3-licenses.md)]
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This feature is in **public preview**. It's being actively developed, and might not be complete.
|
||||
|
||||
The Reliability report provides a reliability score for each Windows quality update cycle based on [stop error codes](/troubleshoot/windows-client/performance/stop-error-or-blue-screen-error-troubleshooting) detected on managed devices. Scores are determined at both the service and tenant level. Details on modules associated with stop error codes at the tenant level are provided to better understand how devices are affected.
|
||||
|
||||
> [!NOTE]
|
||||
> **The Reliability report applies to quality updates only**. The Reliability report doesn't currently support Windows feature updates.<p>Scores used in this report are calculated based on devices running both Windows 10 and Windows 11 versions.</p>
|
||||
|
||||
With this feature, IT admins can access the following information:
|
||||
|
||||
| Information type | Description |
|
||||
| ----- | ----- |
|
||||
| Your score | **Your score** is a calculated tenant reliability score based on stop error codes detected on managed devices that updated successfully during the current update cycle. **Your score** is the latest single-day score in the current Windows quality update cycle. The monthly score values can be viewed under the **Trending** tab. |
|
||||
| Baseline | Use the **Baseline** to compare your score with past quality update cycles. You can choose the desired historical record from the **Comparison baseline** dropdown menu at the top of the page. **Baseline** is a single-day score calculated the same number of days from the start of patching as your score. |
|
||||
| Service-level | Use the **Service-level** to compare **your score** with a score computed across tenants in the Azure Data Scale Unit covering your geographic region. **Service-level** is a single-day score calculated the same number of days from the start of patching as **your score**. |
|
||||
| Score details | **Score details** provides information about specific modules associated with stop error code occurrence, occurrence rate, and affected devices. View single-day or multi-day results by selecting from the **Duration** menu. Data can be exported for offline reference. |
|
||||
| Trending | **Trending** provides a graphical visualization of reliability scores at both tenant and service level on a customizable timeline of 1 - 12 months. Monthly scores represent the aggregated value for a complete update cycle (second Tuesday of the month). |
|
||||
| Insights | **Insights** identifies noteworthy trends that might be useful in implementing reliability improvement opportunities. |
|
||||
| Affected devices | **Affected devices** are the number of unique devices associated with stop error code events. |
|
||||
|
||||
## Report availability
|
||||
|
||||
The Reliability report relies on device policies being configured properly. It's important to confirm that the minimum requirements are met to access the full Reliability report.
|
||||
|
||||
| Data collection policies set | Devices registered in Autopatch | Devices updated | Report availability |
|
||||
| ----- | ------ | ----- | ----- |
|
||||
| No | - | - | No report available.<p>In this state, a ribbon appears on the landing page alerting the user that the diagnostic data needed to generate a report appears to be turned off. The report is available 24 and 48 hours after the following conditions are met:<ul><li>[Diagnostic data device configuration policies enabled](../references/windows-autopatch-changes-to-tenant.md#device-configuration-policies)</li><li>At least 100 devices registered in Autopatch</li><li>At least 100 of these registered devices completed a quality update in the current update cycle (second Tuesday of the month)</li></ul></p> |
|
||||
| Yes | 0 | - | The report includes only the historical comparison baseline and service-level score. The tenant and module impact scores are unavailable until 100 devices are updated. |
|
||||
| Yes | 0 < n < 100 | 0 < n < 100 | The report includes module failure details, historical comparison baseline, and service-level score. The tenant score is unavailable until 100 devices are updated. |
|
||||
| Yes | n >= 100 | 0 < n < 100 | The report includes module failure details, historical comparison baseline score, and service-level score. The tenant and module impact scores are unavailable until 100 devices are updated. |
|
||||
| Yes | n >= 100 | n >= 100 | Full reporting available |
|
||||
|
||||
## View the Reliability report
|
||||
|
||||
**To view the Reliability report:**
|
||||
|
||||
1. Go to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
|
||||
2. Navigate to **Reports** > **Windows Autopatch** > **Windows quality updates**.
|
||||
3. Select the **Reports** tab.
|
||||
4. Select **Reliability report**.
|
||||
|
||||
> [!NOTE]
|
||||
> To use the Reliability report capability, ensure that at least 100 devices are registered in the Windows Autopatch service and capable of successfully completing a quality update. The report relies on device stop error code data being available to Microsoft (transmission of this data may take up to 24 hours).<p>A score is generated when:<ul><li>100 or more devices have completed updating to the latest quality update</li><li>Windows Autopatch receives the stop error code data related to that update cycle</li></ul><p>Windows Autopatch data collection must be enabled according to the [configuration policies](../references/windows-autopatch-changes-to-tenant.md#device-configuration-policies) set during tenant onboarding. For more information about data collection, see [Privacy](../overview/windows-autopatch-privacy.md)</p></p>
|
||||
|
||||
## Report information
|
||||
|
||||
The following information is available as default columns in the Reliability report:
|
||||
|
||||
> [!NOTE]
|
||||
> The report is refreshed no more than once every 24 hours with data received from your Windows Autopatch managed devices. Manual data refresh is not supported. The last refreshed date and time can be found at the top of the page. For more information about how often Windows Autopatch receives data from your managed devices, see [Data latency](../operate/windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md#about-data-latency).
|
||||
|
||||
### Score details
|
||||
|
||||
| Column | Description |
|
||||
| ----- | ----- |
|
||||
| Module name | Name of module associated with stop error code detection. |
|
||||
| Version | Version of module associated with stop error code detection. |
|
||||
| Unique devices | Number of unique devices seeing a stop error code occurrence associated with a specific module name and version. This information is hyperlinked to the **Devices affected** flyout. |
|
||||
| Total events | Total number of stop error codes detected associated with a specific module name and version. |
|
||||
| Module score impact | **Your score** associated with specific module name and version. |
|
||||
| Timeline | This information is hyperlinked to **Module details** flyout. |
|
||||
|
||||
### Export file
|
||||
|
||||
| Column | Description |
|
||||
| ----- | ----- |
|
||||
| DeviceName | Device name |
|
||||
| MicrosoftEntraDeviceId | Microsoft Entra device ID |
|
||||
| Model | Device model |
|
||||
| Manufacturer | Device manufacturer |
|
||||
| AutopatchGroup | Autopatch group assignment for the affected device |
|
||||
| LatestOccurrence | Time of the most recent reported failure |
|
||||
| WindowsVersion | Windows version (Windows 10 or Windows 11) |
|
||||
| OSVersion | OS version |
|
||||
| ModuleName | Name of the module associated with stop error code detection |
|
||||
| Version | Version of the module associated with stop error code detection |
|
||||
| BugCheckCode | Bug check code associated with stop error code |
|
||||
| TenantId | Your Microsoft Entra tenant ID |
|
||||
|
||||
### Devices affected
|
||||
|
||||
| Column | Description |
|
||||
| ----- | ----- |
|
||||
| Device name | Device name |
|
||||
| Microsoft Entra device ID | Microsoft Entra device ID |
|
||||
| Model | Device model |
|
||||
| Manufacturer | Device manufacturer |
|
||||
| Autopatch group | Autopatch group assignment for the affected device |
|
||||
| Latest occurrence | Time of the most recent reported failure |
|
||||
|
||||
### Module details
|
||||
|
||||
| Display selection | Description |
|
||||
| ----- | ----- |
|
||||
| Unique devices | Number of unique devices affected by module failure and the associated version |
|
||||
| Total events | Number of occurrences by module failure and the associated version |
|
||||
| Module impact | Score impact by module and version representing the relative importance of module failure. Higher positive values describe module failures that have a greater impact on the tenant and should be addressed with higher priority. Negative values describe module failures that have a lower-than-average impact on the tenant and thus can be treated with lower priority. Values around `0` describe module failures with average impact on the tenant. |
|
||||
|
||||
## Known limitations
|
||||
|
||||
The Reliability report supports tenant and service-level score data going back to September 2023. Data before that date isn't supported. A full 12 months of score data are available to select from the menu dropdowns in September 2024.
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Windows quality and feature update reports overview
|
||||
description: This article details the types of reports available and info about update device eligibility, device update health, device update trends in Windows Autopatch.
|
||||
ms.date: 11/20/2024
|
||||
ms.date: 03/03/2025
|
||||
ms.service: windows-client
|
||||
ms.subservice: autopatch
|
||||
ms.topic: overview
|
||||
@ -19,6 +19,15 @@ ms.collection:
|
||||
|
||||
[!INCLUDE [windows-autopatch-enterprise-e3-f3-licenses](../includes/windows-autopatch-enterprise-e3-f3-licenses.md)]
|
||||
|
||||
## Prerequisites
|
||||
|
||||
Windows Autopatch requires, and uses Windows diagnostic data to display device update statuses in Autopatch reports.
|
||||
|
||||
- Service state and substate data are included for all devices configured for Windows quality and feature updates. No data collection configuration is required.
|
||||
- Client and substate data are collected from devices only if Windows data collection data is properly configured.
|
||||
|
||||
This data collection configuration method using Windows diagnostic data in Intune is shared across Autopatch reports. To support Autopatch reporting, you must configure the [Enable Windows diagnostic data collection settings](/windows/privacy/configure-windows-diagnostic-data-in-your-organization#diagnostic-data-settings) from devices at the **Required** or higher level.
|
||||
|
||||
## Windows quality update reports
|
||||
|
||||
The Windows quality reports provide you with information about:
|
||||
@ -35,7 +44,6 @@ The Windows quality report types are organized into the following focus areas:
|
||||
| ----- | ----- |
|
||||
| Organizational | The [Summary dashboard](../operate/windows-autopatch-groups-windows-quality-update-summary-dashboard.md) provide the current update status summary for all devices.<p>The [Quality update status report](../operate/windows-autopatch-groups-windows-quality-update-status-report.md) provides the current update status of all devices at the device level. |
|
||||
| Device trends | The [Quality update trending report](../operate/windows-autopatch-groups-windows-quality-update-trending-report.md) provides the update status trend of all devices over the last 90 days. |
|
||||
| [Reliability report](../operate/windows-autopatch-reliability-report.md) | The Reliability report provides a reliability score for each Windows quality update cycle based on stop error codes detected on managed devices. |
|
||||
|
||||
## Windows feature update reports
|
||||
|
||||
@ -87,7 +95,7 @@ Up to date devices are devices that meet all of the following prerequisites:
|
||||
- Applied the current monthly cumulative updates
|
||||
|
||||
> [!NOTE]
|
||||
> Device that are [Up to Date](#up-to-date-devices) will remain with the **In Progress** status until either the current monthly cumulative update is applied, or an [alert](../operate/windows-autopatch-device-alerts.md) is received. If the device receives an alert, the device's status will change to [Not up to Date](#not-up-to-date-devices).
|
||||
> Devices that are [Up to Date](#up-to-date-devices) remain with the **In Progress** status until either the current monthly cumulative update is applied, or an [alert](../operate/windows-autopatch-device-alerts.md) is received. If the device receives an alert, the device's status changes to [Not up to Date](#not-up-to-date-devices).
|
||||
|
||||
#### Up to Date sub statuses
|
||||
|
||||
|
||||
@ -174,15 +174,18 @@ You can add the *Device configurations* permission with one or more rights to yo
|
||||
|
||||
### [Windows Enterprise E3+ and F3](#tab/windows-enterprise-e3-f3-intune-permissions)
|
||||
|
||||
Your account must be assigned an [Intune role-based access control](/mem/intune/fundamentals/role-based-access-control) (RBAC) role that includes the following permissions:
|
||||
|
||||
- **Device configurations**:
|
||||
- Assign
|
||||
- Create
|
||||
- Delete
|
||||
- View Reports
|
||||
- Update
|
||||
- Read
|
||||
|
||||
After you [activate Windows Autopatch features](../prepare/windows-autopatch-feature-activation.md#activate-windows-autopatch-features), use the Intune Service Administrator role to register devices, manage your update deployments, and reporting tasks.
|
||||
|
||||
If you want to assign less-privileged user accounts to perform specific tasks in the Windows Autopatch portal, such as register devices with the service, you can add these user accounts into one of the two Microsoft Entra groups created during the [Start using Windows Autopatch](../prepare/windows-autopatch-feature-activation.md) process:
|
||||
|
||||
| Microsoft Entra group name | Discover devices | Modify columns | Refresh device list | Export to .CSV | Device actions |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| Modern Workplace Roles - Service Administrator | Yes | Yes | Yes | Yes | Yes |
|
||||
| Modern Workplace Roles - Service Reader | No | Yes | Yes | Yes | Yes |
|
||||
|
||||
For more information, see [Microsoft Entra built-in roles](/entra/identity/role-based-access-control/permissions-reference) and [Role-based access control (RBAC) with Microsoft Intune](/mem/intune/fundamentals/role-based-access-control).
|
||||
|
||||
> [!TIP]
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Changes made at feature activation
|
||||
description: This reference article details the changes made to your tenant when you activate Windows Autopatch
|
||||
ms.date: 09/16/2024
|
||||
ms.date: 03/03/2025
|
||||
ms.service: windows-client
|
||||
ms.subservice: autopatch
|
||||
ms.topic: concept-article
|
||||
@ -49,14 +49,6 @@ The following groups target Windows Autopatch configurations to devices and mana
|
||||
| Modern Workplace Devices-Windows Autopatch-Fast | Fast deployment ring for quick rollout and adoption |
|
||||
| Modern Workplace Devices-WindowsAutopatch-Broad | Final deployment ring for broad rollout into the organization |
|
||||
|
||||
## Device configuration policies
|
||||
|
||||
- Windows Autopatch - Data Collection
|
||||
|
||||
| Policy name | Policy description | Properties | Value |
|
||||
| ----- | ----- | ----- | ----- |
|
||||
| Windows Autopatch - Data Collection | Windows Autopatch and Telemetry settings processes diagnostic data from the Windows device.<p>Assigned to:<ul><li>Modern Workplace Devices-Windows Autopatch-Test</li><li>Modern Workplace Devices-Windows Autopatch-First</li><li>Modern Workplace Devices-Windows Autopatch-Fast</li><li>Modern Workplace Devices-Windows Autopatch-Broad</li></ul>|<ol><li>[Allow Telemetry](/windows/client-management/mdm/policy-csp-system#system-allowtelemetry)</li><li>[Limit Enhanced Diagnostic Data Windows Analytics](/windows/client-management/mdm/policy-csp-system#system-limitenhanceddiagnosticdatawindowsanalytics)</li><li>[Limit Dump Collection](/windows/client-management/mdm/policy-csp-system#system-limitdumpcollection)</li><li>[Limit Diagnostic Log Collection](/windows/client-management/mdm/policy-csp-system#system-limitdiagnosticlogcollection)</li></ol>|<ol><li>Full</li><li>Enabled</li><li>Enabled</li><li>Enabled</li></ol> |
|
||||
|
||||
## Windows feature update policies
|
||||
|
||||
- Windows Autopatch - Global DSS Policy
|
||||
@ -68,7 +60,7 @@ The following groups target Windows Autopatch configurations to devices and mana
|
||||
## Microsoft Office update policies
|
||||
|
||||
> [!IMPORTANT]
|
||||
> By default, these policies are not deployed. You can opt-in to deploy these policies when you [activate Windows Autopatch features](../prepare/windows-autopatch-feature-activation.md).<p>To update Microsoft Office, you must [create at least one Autopatch group](../manage/windows-autopatch-manage-autopatch-groups.md) and the toggle the must be set to [**Allow**](../manage/windows-autopatch-microsoft-365-apps-enterprise.md#allow-or-block-microsoft-365-app-updates).</p>
|
||||
> By default, these policies aren't deployed. You can opt in to deploy these policies when you [activate Windows Autopatch features](../prepare/windows-autopatch-feature-activation.md).<p>To update Microsoft Office, you must [create at least one Autopatch group](../manage/windows-autopatch-manage-autopatch-groups.md) and the toggle must be set to [**Allow**](../manage/windows-autopatch-microsoft-365-apps-enterprise.md#allow-or-block-microsoft-365-app-updates).</p>
|
||||
|
||||
- Windows Autopatch - Office Configuration
|
||||
- Windows Autopatch - Office Update Configuration [Test]
|
||||
@ -87,7 +79,7 @@ The following groups target Windows Autopatch configurations to devices and mana
|
||||
## Microsoft Edge update policies
|
||||
|
||||
> [!IMPORTANT]
|
||||
> By default, these policies are not deployed. You can opt-in to deploy these policies when you [activate Windows Autopatch features](../prepare/windows-autopatch-feature-activation.md).<p>To update Microsoft Edge, you must [create at least one Autopatch group](../manage/windows-autopatch-manage-autopatch-groups.md) and the toggle the must be set to [**Allow**](../manage/windows-autopatch-edge.md#allow-or-block-microsoft-edge-updates).</p>
|
||||
> By default, these policies aren't deployed. You can opt in to deploy these policies when you [activate Windows Autopatch features](../prepare/windows-autopatch-feature-activation.md).<p>To update Microsoft Edge, you must [create at least one Autopatch group](../manage/windows-autopatch-manage-autopatch-groups.md) and the toggle must be set to [**Allow**](../manage/windows-autopatch-edge.md#allow-or-block-microsoft-edge-updates).</p>
|
||||
|
||||
- Windows Autopatch - Edge Update Channel Stable
|
||||
- Windows Autopatch - Edge Update Channel Beta
|
||||
@ -100,7 +92,7 @@ The following groups target Windows Autopatch configurations to devices and mana
|
||||
## Driver updates for Windows 10 and later
|
||||
|
||||
> [!IMPORTANT]
|
||||
> By default, these policies are not deployed. You can opt-in to deploy these policies when you [activate Windows Autopatch features](../prepare/windows-autopatch-feature-activation.md).<p>To update drivers and firmware, you must [create at least one Autopatch group](../manage/windows-autopatch-manage-autopatch-groups.md) and the toggle the must be set to [**Allow**](../manage/windows-autopatch-manage-autopatch-groups.md#create-an-autopatch-group).</p>
|
||||
> By default, these policies aren't deployed. You can opt in to deploy these policies when you [activate Windows Autopatch features](../prepare/windows-autopatch-feature-activation.md).<p>To update drivers and firmware, you must [create at least one Autopatch group](../manage/windows-autopatch-manage-autopatch-groups.md) and the toggle must be set to [**Allow**](../manage/windows-autopatch-manage-autopatch-groups.md#create-an-autopatch-group).</p>
|
||||
|
||||
- Windows Autopatch - Driver Update Policy [Test]
|
||||
- Windows Autopatch - Driver Update Policy [First]
|
||||
|
||||
@ -70,7 +70,6 @@ Minor corrections such as typos, style, or formatting issues aren't listed.
|
||||
| ----- | ----- |
|
||||
| [MC678305](https://admin.microsoft.com/adminportal/home#/MessageCenter) | September 2023 Windows Autopatch baseline configuration update |
|
||||
| [MC678303](https://admin.microsoft.com/adminportal/home#/MessageCenter) | Windows Autopatch availability within Microsoft Intune Admin Center |
|
||||
| [MC674422](https://admin.microsoft.com/adminportal/home#/MessageCenter) | Public Preview: Windows Autopatch Reliability Report |
|
||||
| [MC672750](https://admin.microsoft.com/adminportal/home#/MessageCenter) | August 2023 Windows Autopatch baseline configuration update |
|
||||
|
||||
## August 2023
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: What's new 2024
|
||||
description: This article lists the 2024 feature releases and any corresponding Message center post numbers.
|
||||
ms.date: 11/19/2024
|
||||
ms.date: 02/27/2025
|
||||
ms.service: windows-client
|
||||
ms.subservice: autopatch
|
||||
ms.topic: whats-new
|
||||
@ -37,14 +37,6 @@ Minor corrections such as typos, style, or formatting issues aren't listed.
|
||||
| ----- | ----- |
|
||||
| All articles | Windows Update for Business deployment service (WUfB-DS) unified under Windows Autopatch. Unification is going through a gradual rollout over the next several weeks. If your experience looks different from the documentation, you didn't receive the unified experience yet. Review [Prerequisites](../prepare/windows-autopatch-prerequisites.md) and [Features and capabilities](../overview/windows-autopatch-overview.md#features-and-capabilities) to understand licensing and feature entitlement.|
|
||||
|
||||
## March 2024
|
||||
|
||||
### March feature releases or updates
|
||||
|
||||
| Article | Description |
|
||||
| ----- | ----- |
|
||||
| [Reliability report](../operate/windows-autopatch-reliability-report.md) | Added the [Reliability report](../operate/windows-autopatch-reliability-report.md) feature |
|
||||
|
||||
## February 2024
|
||||
|
||||
## February service releases
|
||||
|
||||
Reference in New Issue
Block a user