From 336d07eb34c8a8883cc19fc3f8461421674cf211 Mon Sep 17 00:00:00 2001 From: tiaraquan Date: Fri, 23 Feb 2024 11:23:19 -0800 Subject: [PATCH 1/9] Reliability report --- windows/deployment/windows-autopatch/TOC.yml | 2 + ...ity-and-feature-update-reports-overview.md | 7 +- .../windows-autopatch-reliability-report.md | 120 ++++++++++++++++++ 3 files changed, 126 insertions(+), 3 deletions(-) create mode 100644 windows/deployment/windows-autopatch/operate/windows-autopatch-reliability-report.md diff --git a/windows/deployment/windows-autopatch/TOC.yml b/windows/deployment/windows-autopatch/TOC.yml index 1592090c59..b47512b08a 100644 --- a/windows/deployment/windows-autopatch/TOC.yml +++ b/windows/deployment/windows-autopatch/TOC.yml @@ -90,6 +90,8 @@ href: operate/windows-autopatch-groups-windows-quality-update-status-report.md - name: Quality update trending report href: operate/windows-autopatch-groups-windows-quality-update-trending-report.md + - name: Reliability report + href: operate/windows-autopatch-reliability-report.md - name: Windows feature update reports href: items: diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md index fdacc1576c..8083b5dcdc 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md @@ -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 groups -ms.date: 07/25/2023 +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: 02/26/2024 ms.service: windows-client ms.subservice: itpro-updates ms.topic: conceptual @@ -33,6 +33,7 @@ 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.

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 | The [Reliability report](../operate/windows-autopatch-reliability-report.md) provides a reliability score calculated for each Windows quality update cycle based on stop error codes detected on managed devices. | ## Windows feature update reports @@ -79,7 +80,7 @@ Up to date devices are devices that meet all of the following prerequisites: - [Prerequisites for device registration](../deploy/windows-autopatch-register-devices.md#prerequisites-for-device-registration) - [Windows quality and feature update device readiness](../deploy/windows-autopatch-post-reg-readiness-checks.md) - [Post-device readiness checks](../deploy/windows-autopatch-post-reg-readiness-checks.md) -- Have applied the current monthly cumulative updates +- Applied the current monthly cumulative updates > [!NOTE] > [Up to Date devices](#up-to-date-devices) will remain with the **In Progress** status for the 21-day service level objective period until the device either applies the current monthly cumulative update or receives an [alert](../operate/windows-autopatch-device-alerts.md). If the device receives an alert, the device's status will change to [Not up to Date](#not-up-to-date-devices). diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-reliability-report.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-reliability-report.md new file mode 100644 index 0000000000..2102bb83bb --- /dev/null +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-reliability-report.md @@ -0,0 +1,120 @@ +--- +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: 02/26/2024 +ms.prod: windows-client +ms.technology: itpro-updates +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) + +> [!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 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.

Scores used in this report are calculated based on devices running both Windows 10 and Windows 11 versions.

+ +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.

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:

| +| 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 | 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).

A score is generated when:

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)

+ +## 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 will be available to select from the menu dropdowns in September 2024. From bfcdd3ea33dbe9e3be89f56b8689da365134ff72 Mon Sep 17 00:00:00 2001 From: tiaraquan Date: Fri, 23 Feb 2024 11:33:20 -0800 Subject: [PATCH 2/9] Reliability report release --- windows/deployment/windows-autopatch/TOC.yml | 2 +- ...roups-windows-quality-and-feature-update-reports-overview.md | 2 +- .../operate/windows-autopatch-reliability-report.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/deployment/windows-autopatch/TOC.yml b/windows/deployment/windows-autopatch/TOC.yml index b47512b08a..6cf4d8ec54 100644 --- a/windows/deployment/windows-autopatch/TOC.yml +++ b/windows/deployment/windows-autopatch/TOC.yml @@ -90,7 +90,7 @@ href: operate/windows-autopatch-groups-windows-quality-update-status-report.md - name: Quality update trending report href: operate/windows-autopatch-groups-windows-quality-update-trending-report.md - - name: Reliability report + - name: Reliability report href: operate/windows-autopatch-reliability-report.md - name: Windows feature update reports href: diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md index 8083b5dcdc..108eb835d0 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md @@ -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: 02/26/2024 +ms.date: 02/26/2024 ms.service: windows-client ms.subservice: itpro-updates ms.topic: conceptual diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-reliability-report.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-reliability-report.md index 2102bb83bb..4fa117e8c7 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-reliability-report.md +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-reliability-report.md @@ -1,7 +1,7 @@ --- 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: 02/26/2024 +ms.date: 02/26/2024 ms.prod: windows-client ms.technology: itpro-updates ms.topic: how-to From 80f3d7cf9ac562975d688e080b9f55f8a82a77a8 Mon Sep 17 00:00:00 2001 From: tiaraquan Date: Fri, 23 Feb 2024 11:42:58 -0800 Subject: [PATCH 3/9] Updated ms.prod metadata value to ms.service --- .../operate/windows-autopatch-reliability-report.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-reliability-report.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-reliability-report.md index 4fa117e8c7..8a218cc0aa 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-reliability-report.md +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-reliability-report.md @@ -1,8 +1,8 @@ --- 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: 02/26/2024 -ms.prod: windows-client +ms.date: 02/26/2024 +ms.service: windows-client ms.technology: itpro-updates ms.topic: how-to ms.localizationpriority: medium From 1e54e86cf70544cd3a0025614a2270df184435b9 Mon Sep 17 00:00:00 2001 From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com> Date: Thu, 21 Mar 2024 12:01:20 -0700 Subject: [PATCH 4/9] Update windows-autopatch-reliability-report.md --- .../operate/windows-autopatch-reliability-report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-reliability-report.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-reliability-report.md index 8a218cc0aa..80b1af0b8c 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-reliability-report.md +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-reliability-report.md @@ -3,7 +3,7 @@ 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: 02/26/2024 ms.service: windows-client -ms.technology: itpro-updates +ms.subservice: itpro-updates ms.topic: how-to ms.localizationpriority: medium author: tiaraquan From 087b8f60ff4df20a66852525719237888c92dcef Mon Sep 17 00:00:00 2001 From: tiaraquan Date: Mon, 8 Apr 2024 18:41:38 -0700 Subject: [PATCH 5/9] Resolve policy conflicts --- windows/deployment/windows-autopatch/TOC.yml | 9 +- ...dows-autopatch-resolve-policy-conflicts.md | 93 +++++++++++++++++++ .../windows-autopatch-whats-new-2024.md | 10 +- 3 files changed, 109 insertions(+), 3 deletions(-) create mode 100644 windows/deployment/windows-autopatch/operate/windows-autopatch-resolve-policy-conflicts.md diff --git a/windows/deployment/windows-autopatch/TOC.yml b/windows/deployment/windows-autopatch/TOC.yml index 6cf4d8ec54..a9d9291cc8 100644 --- a/windows/deployment/windows-autopatch/TOC.yml +++ b/windows/deployment/windows-autopatch/TOC.yml @@ -103,8 +103,13 @@ href: operate/windows-autopatch-groups-windows-feature-update-trending-report.md - name: Windows quality and feature update device alerts href: operate/windows-autopatch-device-alerts.md - - name: Policy health and remediation - href: operate/windows-autopatch-policy-health-and-remediation.md + - name: Policy health + href: + items: + - name: Policy health and remediation + href: operate/windows-autopatch-policy-health-and-remediation.md + - name: Resolve policy conflicts + href: operate/windows-autopatch-resolve-policy-conflicts.md - name: Maintain the Windows Autopatch environment href: operate/windows-autopatch-maintain-environment.md - name: Manage driver and firmware updates diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-resolve-policy-conflicts.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-resolve-policy-conflicts.md new file mode 100644 index 0000000000..3967e6a3f5 --- /dev/null +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-resolve-policy-conflicts.md @@ -0,0 +1,93 @@ +--- +title: Resolve policy conflicts +description: This article describes how to resolve Windows Autopatch policy conflicts. +ms.date: 04/09/2024 +ms.service: windows-client +ms.subservice: itpro-updates +ms.topic: how-to +ms.localizationpriority: medium +author: tiaraquan +ms.author: tiaraquan +manager: aaroncz +ms.reviewer: hathind +ms.collection: + - highpri + - tier1 +--- + +# Resolve policy conflicts (public preview) + +> [!IMPORTANT] +> This feature is in **public preview**. It's being actively developed, and might not be complete. + +Windows Autopatch deploys Microsoft Intune policies to enrolled tenants, and continuously monitors the Microsoft Intune policies. Conflicts occur when there are two policies in the tenant, and they update the same setting to different values. For Windows Autopatch to successfully deliver updates to registered devices, it’s critical for the devices in the service to have the policy targeted and assigned successfully. + +> [!IMPORTANT] +> Don't change, edit, add to, or remove any of the Windows Autopatch policies or groups. Doing so can cause unintended configuration changes and impact the Windows Autopatch service. For more information about Windows Autopatch configurations, see [Changes made at tenant enrollment](../references/windows-autopatch-changes-to-tenant.md). + +When the Windows Autopatch service detects policies in the tenant that conflict with a setting in another Intune device policy, this conflict is displayed. It’s necessary to review the policies and their settings and manually resolve these conflicts. + +With this feature, IT admins can view: + +- List of all Autopatch policies that conflict with other device policies in the tenant +- A summary view of conflicting policies, affected devices, and open alerts +- A detailed view of affected devices +- Alerts that include details of conflicting policies, the settings, and the Azure AD groups they're assigned to. Admins must take necessary action so the expected policy is successfully assigned to the device + +## Resolve policy conflicts overview + +Alerts are raised when devices report policy conflicts. Autopatch policies are assigned to Autopatch groups. Devices that are members of Autopatch groups are expected to receive only Windows Autopatch policies. + +Once you resolve the conflict, it takes effect on the device at the next Intune sync. This view is refreshed every 24 hours. It can take up to 72 hours after the conflict is resolved for the view to be updated. + +> [!NOTE] +> This view only includes policy conflicts between Microsoft Intune policies. This view doesn’t include policy issues caused by other configurations, for example, group policy settings, registry settings that are changed by scripts and prevent Windows Autopatch from deploying updates.

When Windows Autopatch detects Intune based policies are missing or modified, this information is displayed with detailed recommended actions, and described in [Policy health and remediation](../operate/windows-autopatch-policy-health-and-remediation.md).

To ensure devices remain healthy and not affected by group policies, see [Post-device registration readiness checks](../deploy/windows-autopatch-post-reg-readiness-checks.md#details-about-the-post-device-registration-readiness-checks).

+ +## Policy conflict view + +This view includes the list of Windows Autopatch policies ([Expected policies](#policy-conflict-alert-details)) that are assigned to various Windows Autopatch groups that include devices. When the Expected policy can't be successfully assigned to one or more devices, because of an equivalent setting in another Intune policy targeting the device, the conflict is detected, and reported as a [Conflicting policy](#policy-conflict-alert-details). + +If the Expected policy conflicts with multiple Intune policies, each conflict is displayed in different lines in the Policy conflict view. + +**To view all policies conflicting with the expected policies:** + +1. Go to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431). +2. Navigate to **Devices** > **Windows Autopatch** > **Policy health**. +3. In the **Policy conflicts** tab, the list of expected policies and conflicting policies is displayed. +4. Select **View alert** and review the details of the **Recommended action** and alert details. + +### Policy conflict alert details + +All alerts displayed in this flyout include the following details. You must review the details and take action to resolve the conflict. + +| Alert column | Description | +| ----- | ----- | +| Expected Policy | The Windows Autopatch policy that is assigned to the Windows Autopatch group and is the policy that the service is expecting to be assigned. | +| Expected Microsoft Entra Group | The device is a member of the Windows Autopatch group that the service assigned the policy to. | +| Conflicting Policy | Other policies on the tenant are configuring the same settings and with different values. This policy is also targeted to the same devices, which is causing the policy state to report a conflict. | +| Conflicting Microsoft Entra Group | The device is also a member of this Microsoft Entra group that the conflicting policy is assigned to. | +| Affected devices | Number of devices reporting the policy conflict. This check is only performed on devices where the last sync is within 28 days. | +| Conflicting settings | Includes the specific setting values causing the conflict. | + +## Affected devices view + +This view includes the list of devices with policy conflicts with the [Expected policy](#policy-conflict-alert-details). It’s possible for devices to have multiple conflicting policies, due to their membership in various groups. + +You can navigate to this view from the Affected devices column link in the Policy conflicts view, or directly from Policy health blade. This page displays a filtered device list, when navigating from the Policy conflicts view. Affected devices only include devices that have a successful Intune sync status in the last 28 days. + +**To view the alert details and perform the recommended actions:** + +1. Go to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431). +2. Navigate to **Windows Autopatch** > **Policy health** > **Affected devices** tab. +3. Select **View alert** to see the alert details. + +### Affected devices alert details + +In this flyout, when the device is reporting conflicts due to multiple policies, each policy is displayed as a separate section in this alert. Alerts occur when the device is a member of multiple groups, and each policy conflicts with the [Expected Windows Autopatch policy](#policy-conflict-view). + +## Options + +| Options | Description | +| ----- | ----- | +| Export alerts | You can use this option in either the Policy conflicts or Affected devices tabs. Select Export to export all alert details into a CSV file. The CSV file includes the following information:
  • Device name
  • Deployment ring
  • Conflicting policies count
  • Last check-in
  • Expected policy name
  • Expected policy group
  • Conflicting policy group
  • Conflicting policy name
| +| Search | Use the Search option to find the policies of affected devices. In the Search, enter either the Expected policy name or the Conflicting policy name. | diff --git a/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2024.md b/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2024.md index e450ef2a41..af55139038 100644 --- a/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2024.md +++ b/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2024.md @@ -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: 02/07/2024 +ms.date: 04/09/2024 ms.service: windows-client ms.subservice: itpro-updates ms.topic: whats-new @@ -21,6 +21,14 @@ This article lists new and updated feature releases, and service releases, with Minor corrections such as typos, style, or formatting issues aren't listed. +## March 2024 + +### March feature releases or updates + +| Article | Description | +| ----- | ----- | +| [Resolve policy conflicts](../operate/windows-autopatch-resolve-policy-conflicts.md) | Added [Resolve policy conflicts](../operate/windows-autopatch-resolve-policy-conflicts.md) feature | + ## February 2024 ## February service releases From 1ef313dbe25311c14d5916940f98c84f4540d515 Mon Sep 17 00:00:00 2001 From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com> Date: Mon, 8 Apr 2024 18:47:33 -0700 Subject: [PATCH 6/9] Update TOC.yml Removed reliability report. Shouldn't be in this PR. --- windows/deployment/windows-autopatch/TOC.yml | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/windows/deployment/windows-autopatch/TOC.yml b/windows/deployment/windows-autopatch/TOC.yml index a9d9291cc8..619348bcdd 100644 --- a/windows/deployment/windows-autopatch/TOC.yml +++ b/windows/deployment/windows-autopatch/TOC.yml @@ -90,8 +90,6 @@ href: operate/windows-autopatch-groups-windows-quality-update-status-report.md - name: Quality update trending report href: operate/windows-autopatch-groups-windows-quality-update-trending-report.md - - name: Reliability report - href: operate/windows-autopatch-reliability-report.md - name: Windows feature update reports href: items: @@ -142,4 +140,4 @@ - name: What's new 2023 href: whats-new/windows-autopatch-whats-new-2023.md - name: What's new 2022 - href: whats-new/windows-autopatch-whats-new-2022.md \ No newline at end of file + href: whats-new/windows-autopatch-whats-new-2022.md From c4f9cc2f623735ec99fb1a0c8cdeac12888af3c1 Mon Sep 17 00:00:00 2001 From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com> Date: Mon, 8 Apr 2024 18:48:46 -0700 Subject: [PATCH 7/9] Update windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md Removed Reliability report. Shouldn't be in this PR. --- ...groups-windows-quality-and-feature-update-reports-overview.md | 1 - 1 file changed, 1 deletion(-) diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md index 15120b5c08..27084fdcdf 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md @@ -33,7 +33,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.

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 | The [Reliability report](../operate/windows-autopatch-reliability-report.md) provides a reliability score calculated for each Windows quality update cycle based on stop error codes detected on managed devices. | ## Windows feature update reports From 4ca2fef066276923ed2b34c16641aaf9b75185d9 Mon Sep 17 00:00:00 2001 From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com> Date: Mon, 8 Apr 2024 18:50:11 -0700 Subject: [PATCH 8/9] Delete windows/deployment/windows-autopatch/operate/windows-autopatch-reliability-report.md This shouldn't be in here. Not sure why it's showing up as I didn't commit the other PR that has this file. --- .../windows-autopatch-reliability-report.md | 120 ------------------ 1 file changed, 120 deletions(-) delete mode 100644 windows/deployment/windows-autopatch/operate/windows-autopatch-reliability-report.md diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-reliability-report.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-reliability-report.md deleted file mode 100644 index 80b1af0b8c..0000000000 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-reliability-report.md +++ /dev/null @@ -1,120 +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: 02/26/2024 -ms.service: windows-client -ms.subservice: itpro-updates -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) - -> [!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 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.

Scores used in this report are calculated based on devices running both Windows 10 and Windows 11 versions.

- -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.

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:

  • [Diagnostic data device configuration policies enabled](../references/windows-autopatch-changes-to-tenant.md#device-configuration-policies)
  • At least 100 devices registered in Autopatch
  • At least 100 of these registered devices completed a quality update in the current update cycle (second Tuesday of the month)

| -| 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 | 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).

A score is generated when:

  • 100 or more devices have completed updating to the latest quality update
  • Windows Autopatch receives the stop error code data related to that update cycle

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)

- -## 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 will be available to select from the menu dropdowns in September 2024. From ad186dddfe000e0370b4b604f1444b90ad9378fd Mon Sep 17 00:00:00 2001 From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com> Date: Mon, 8 Apr 2024 18:51:26 -0700 Subject: [PATCH 9/9] Update windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md Date --- ...roups-windows-quality-and-feature-update-reports-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md index 27084fdcdf..91f758db48 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md @@ -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: 04/04/2024 +ms.date: 04/09/2024 ms.service: windows-client ms.subservice: itpro-updates ms.topic: conceptual