mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
edits, ren admin center page
This commit is contained in:
parent
143dfd7986
commit
5af9a2b727
@ -20144,7 +20144,12 @@
|
||||
"source_path": "windows/deployment/update/update-compliance-v2-use.md",
|
||||
"redirect_url": "/windows/deployment/update/wufb-reports-use",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/update/update-status-admin-center.md",
|
||||
"redirect_url": "/windows/deployment/update/wufb-reports-admin-center",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/update/update-compliance-v2-workbook.md",
|
||||
"redirect_url": "/windows/deployment/update/wufb-reports-workbook",
|
||||
|
@ -204,8 +204,8 @@
|
||||
items:
|
||||
- name: Windows Update for Business reports workbook
|
||||
href: update/wufb-reports-workbook.md
|
||||
- name: Software updates in the Microsoft admin center
|
||||
href: update/update-status-admin-center.md
|
||||
- name: Software updates in the Microsoft 365 admin center
|
||||
href: update/wufb-reports-admin-center.md
|
||||
- name: Use Windows Update for Business reports data
|
||||
href: update/wufb-reports-use.md
|
||||
- name: Feedback, support, and troubleshooting
|
||||
|
@ -8,15 +8,14 @@ ms.topic: include
|
||||
ms.date: 08/18/2022
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
<!--This file is shared by updates/wufb-reports-enable.md and the update/update-status-admin-center.md articles. Headings may be driven by article context. -->
|
||||
[Enabling Windows Update for Business reports](../wufb-reports-enable.md) requires access to the [Microsoft admin center software updates page](../update-status-admin-center.md) as does displaying Windows Update for Business reports data in the admin center. The following permissions are needed for access to the [Microsoft 365 admin center](https://admin.microsoft.com):
|
||||
<!--This file is shared by updates/wufb-reports-enable.md and the update/wufb-reports-admin-center.md articles. Headings may be driven by article context. -->
|
||||
|
||||
To enroll into Windows Update for Business reports, edit configuration settings, display and edit the workbook, and view the **Windows** tab in the **Software Updates** page from the [Microsoft 365 admin center](https://admin.microsoft.com) use one of the following roles:
|
||||
|
||||
- To enable Windows Update for Business reports, edit Windows Update for Business reports configuration settings, and view the **Windows** tab in the **Software Updates** page:
|
||||
- [Global Administrator role](/azure/active-directory/roles/permissions-reference#global-administrator)
|
||||
- [Intune Administrator](/azure/active-directory/roles/permissions-reference#intune-administrator)
|
||||
- To view the **Windows** tab in the **Software Updates** page:
|
||||
- [Global Administrator role](/azure/active-directory/roles/permissions-reference#global-administrator)
|
||||
- [Intune Administrator](/azure/active-directory/roles/permissions-reference#intune-administrator)
|
||||
- [Windows Update deployment administrator](/azure/active-directory/roles/permissions-reference#windows-update-deployment-administrator)
|
||||
- This role allows enrollment through the [workbook](../wufb-reports-enable.md#bkmk_enroll-workbook) but not the Microsoft 365 admin center
|
||||
|
||||
To display the workbook and view the **Windows** tab in the **Software Updates** page [Microsoft 365 admin center](https://admin.microsoft.com) use the following role:
|
||||
- [Global Reader role](/azure/active-directory/roles/permissions-reference#global-reader)
|
||||
|
||||
> [!NOTE]
|
||||
> These permissions for the Microsoft 365 admin center apply specifically to the **Windows** tab of the **Software Updates** page. For more information about the **Microsoft 365 Apps** tab, see [Microsoft 365 Apps updates in the admin center](/DeployOffice/updates/software-update-status).
|
||||
|
@ -8,7 +8,7 @@ ms.topic: include
|
||||
ms.date: 08/18/2022
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
<!--This file is shared by updates/wufb-reports-enable.md and the update/update-status-admin-center.md articles. Headings are driven by article context. -->
|
||||
<!--This file is shared by updates/wufb-reports-enable.md and the update/wufb-reports-admin-center.md articles. Headings are driven by article context. -->
|
||||
1. Go to the [Microsoft 365 admin center](https://admin.microsoft.com/) and sign in.
|
||||
1. Expand **Health**, then select **Software Updates**. You may need to use the **Show all** option to display **Health** in the navigation menu.
|
||||
1. In the **Software Updates** page, select the **Windows** tab.
|
||||
|
Binary file not shown.
Before Width: | Height: | Size: 322 KiB After Width: | Height: | Size: 237 KiB |
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Microsoft admin center software updates page
|
||||
title: Microsoft 365 admin center software updates page
|
||||
manager: dougeby
|
||||
description: Microsoft admin center populates Windows Update for Business reports data into the software updates page.
|
||||
ms.prod: windows-client
|
||||
@ -13,7 +13,7 @@ ms.date: 06/20/2022
|
||||
ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
# Microsoft admin center software updates page
|
||||
# Microsoft 365 admin center software updates page
|
||||
<!--37063317, 30141258, 37063041, ID2616577, ID2582518 -->
|
||||
***(Applies to: Windows 11 & Windows 10 using [Windows Update for Business reports](wufb-reports-overview.md) and the [Microsoft 365 admin center](/microsoft-365/admin/admin-overview/admin-center-overview))***
|
||||
|
||||
@ -25,12 +25,15 @@ The **Software updates** page has following tabs to assist you in monitoring upd
|
||||
- For more information about the **Microsoft 365 Apps** tab, see [Microsoft 365 Apps updates in the admin center](/DeployOffice/updates/software-update-status).
|
||||
- **Windows**: Displays compliance charts for cumulative updates and feature updates for Windows clients. This article contains information about the **Windows** tab.
|
||||
|
||||
:::image type="content" source="media/37063317-admin-center-software-updates.png" alt-text="Screenshot of the Microsoft 365 admin center displaying the software updates page with the Windows tab selected." lightbox="media/37063317-admin-center-software-updates.png":::
|
||||
:::image type="content" source="media/37063317-admin-center-software-updates.png" alt-text="Screenshot of the Microsoft 365 admin center displaying the software updates page with the Windows tab selected." lightbox="media/37063317-admin-center-software-updates.png":::
|
||||
|
||||
## Permissions
|
||||
<!--Using include Microsoft 365 admin center permissions-->
|
||||
[!INCLUDE [Windows Update for Business reports script error codes](./includes/wufb-reports-admin-center-permissions.md)]
|
||||
|
||||
<!--Using include Microsoft 365 admin center permissions-->
|
||||
[!INCLUDE [Windows Update for Business reports permissions](./includes/wufb-reports-admin-center-permissions.md)]
|
||||
|
||||
> [!NOTE]
|
||||
> These permissions for the Microsoft 365 admin center apply specifically to the **Windows** tab of the **Software Updates** page. For more information about the **Microsoft 365 Apps** tab, see [Microsoft 365 Apps updates in the admin center](/DeployOffice/updates/software-update-status).
|
||||
|
||||
## Limitations
|
||||
|
||||
@ -38,7 +41,6 @@ Windows Update for Business reports is a Windows service hosted in Azure that us
|
||||
|
||||
## Get started
|
||||
|
||||
|
||||
<!--Using include for onboarding Windows Update for Business reports through the Microsoft 365 admin center-->
|
||||
[!INCLUDE [Onboarding Windows Update for Business reports through the Microsoft 365 admin center](./includes/wufb-reports-onboard-admin-center.md)]
|
||||
|
@ -21,7 +21,7 @@ ms.technology: itpro-updates
|
||||
> As of August 17, 2022, a new step needs to be taken to ensure access to Windows Update for Business reports and the `CommercialID` is no longer required. For more information, see [Configure Windows Update for Business reports settings](wufb-reports-enable.md#bkmk_admin-center).
|
||||
|
||||
|
||||
This article is specifically targeted at configuring devices enrolled to [Microsoft Intune](/mem/intune/fundamentals/what-is-intune) for Windows Update for Business reports, within Microsoft Intune itself. Configuring devices for Windows Update for Business reports in Microsoft Intune breaks down to the following steps:
|
||||
This article is targeted at configuring devices enrolled to [Microsoft Intune](/mem/intune/fundamentals/what-is-intune) for Windows Update for Business reports, within Microsoft Intune itself. Configuring devices for Windows Update for Business reports in Microsoft Intune breaks down to the following steps:
|
||||
|
||||
1. [Create a configuration profile](#create-a-configuration-profile) for devices you want to enroll. The configuration profile contains settings for all the Mobile Device Management (MDM) policies that must be configured.
|
||||
1. Wait for data to populate. The length of this process depends on the computer being on, connected to the internet, and correctly configured. Some data types take longer to appear than others. For more information, see [Use Windows Update for Business reports](wufb-reports-use.md).
|
||||
@ -33,7 +33,7 @@ This article is specifically targeted at configuring devices enrolled to [Micros
|
||||
|
||||
Create a configuration profile that will set the required policies for Windows Update for Business reports. There are two profile types that can be used to create a configuration profile for Windows Update for Business reports:
|
||||
- The [settings catalog](#settings-catalog)
|
||||
- [Template](#custom-oma-uri-based-profile) for a custom OMA URI based profile
|
||||
- [Template](#custom-oma-uri-based-profile) for a custom OMA URI-based profile
|
||||
|
||||
### Settings catalog
|
||||
|
||||
@ -54,10 +54,10 @@ Create a configuration profile that will set the required policies for Windows U
|
||||
- **Setting**: Allow device name to be sent in Windows diagnostic data
|
||||
- **Value**: Allowed
|
||||
|
||||
1. Proceed through the next set of tabs **Scope tags**, **Assignments**, and **Applicability Rules** to assign the configuration profile to devices you wish to enroll.
|
||||
1. Continue through the next set of tabs **Scope tags**, **Assignments**, and **Applicability Rules** to assign the configuration profile to devices you wish to enroll.
|
||||
1. Review the settings and then select **Create**.
|
||||
|
||||
### Custom OMA URI based profile
|
||||
### Custom OMA URI-based profile
|
||||
|
||||
1. In the [Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431), go to **Devices** > **Windows** > **Configuration profiles**.
|
||||
1. On the **Configuration profiles** view, select **Create profile**.
|
||||
@ -86,7 +86,7 @@ Create a configuration profile that will set the required policies for Windows U
|
||||
- **Value**: 16
|
||||
1. (*Recommended, but not required*) Add settings for **disabling devices' Diagnostic Data opt-in settings interface**. If these aren't disabled, users of each device can potentially override the diagnostic data level of devices such that data won't be available for those devices in Windows Update for Business reports:
|
||||
- **Name**: Disable Telemetry opt-in interface
|
||||
- **Description**: Disables the ability for end-users of devices can adjust diagnostic data to levels lower than defined by the Allow Telemetry setting.
|
||||
- **Description**: Disables the ability for end users of devices can adjust diagnostic data to levels lower than defined by the Allow Telemetry setting.
|
||||
- **OMA-URI**: `./Vendor/MSFT/Policy/Config/System/ConfigureTelemetryOptInSettingsUx`
|
||||
- **Data type**: Integer
|
||||
- **Value**: 1
|
||||
@ -98,14 +98,14 @@ Create a configuration profile that will set the required policies for Windows U
|
||||
- **Value**: 1
|
||||
|
||||
|
||||
1. Proceed through the next set of tabs **Scope tags**, **Assignments**, and **Applicability Rules** to assign the configuration profile to devices you wish to enroll.
|
||||
1. Continue through the next set of tabs **Scope tags**, **Assignments**, and **Applicability Rules** to assign the configuration profile to devices you wish to enroll.
|
||||
1. Review the settings and then select **Create**.
|
||||
|
||||
## Deploy the configuration script
|
||||
|
||||
The [Windows Update for Business reports Configuration Script](wufb-reports-configuration-script.md) is a useful tool for properly enrolling devices in Windows Update for Business reports, though it isn't strictly necessary. It checks to ensure that devices have the required services running and checks connectivity to the endpoints detailed in the section on [Manually configuring devices for Windows Update for Business reports](wufb-reports-configuration-manual.md). You can deploy the script as a Win32 app. For more information, see [Win32 app management in Microsoft Intune](/mem/intune/apps/apps-win32-app-management).
|
||||
|
||||
When you deploy the configuration script as a Win32 app, you won't be able to retrieve the results of logs on the device without having access to the device, or saving results of the logs to a shared filesystem. We recommend deploying the script in pilot mode to a set of devices that you do have access to, or have a way to access the resultant log output the script provides, with as similar of a configuration profile as other devices which will be enrolled to Windows Update for Business reports, and analyzing the logs for any potential issues. Following this, you can deploy the configuration script in deployment mode as a Win32 app to all Windows Update for Business reports devices.
|
||||
When you deploy the configuration script as a Win32 app, you won't be able to retrieve the results of logs on the device without having access to the device, or saving results of the logs to a shared filesystem. We recommend deploying the script in pilot mode to a subset of devices that you can access. After following this guidance, you can deploy the configuration script in deployment mode as a Win32 app to all Windows Update for Business reports devices.
|
||||
|
||||
## Next steps
|
||||
|
||||
|
@ -45,8 +45,8 @@ Each MDM Policy links to its documentation in the configuration service provider
|
||||
|--------------------------|-|-|------------------------------------------------------------|
|
||||
|**System/**[**AllowTelemetry**](/windows/client-management/mdm/policy-csp-system#system-allowtelemetry) |Integer | 1 - Basic |Configures the maximum allowed diagnostic data to be sent to Microsoft. Individual users can still set this value lower than what the policy defines. For more information, see the following policy. |
|
||||
|**System/**[**ConfigureTelemetryOptInSettingsUx**](/windows/client-management/mdm/policy-csp-system#system-configuretelemetryoptinsettingsux) |Integer |1 - Disable Telemetry opt-in Settings | (in Windows 10, version 1803 and later) Determines whether users of the device can adjust diagnostic data to levels lower than the level defined by AllowTelemetry. We recommend that you disable this policy or the effective diagnostic data level on devices might not be sufficient. |
|
||||
|**System/**[**AllowDeviceNameInDiagnosticData**](/windows/client-management/mdm/policy-csp-system#system-allowdevicenameindiagnosticdata) |Integer | 1 - Allowed | Allows device name to be sent for Windows Diagnostic Data. If this policy is Not Configured or set to 0 (Disabled), Device Name will not be sent and won't be visible in Windows Update for Business reports, showing `#` instead. |
|
||||
| **System/**[**AllowUpdateComplianceProcessing**](/windows/client-management/mdm/policy-csp-system#system-allowUpdateComplianceProcessing) |Integer | 16 - Allowed | Enables data flow through Windows Update for Business reports's data processing system and indicates a device's explicit enrollment to the service. |
|
||||
|**System/**[**AllowDeviceNameInDiagnosticData**](/windows/client-management/mdm/policy-csp-system#system-allowdevicenameindiagnosticdata) |Integer | 1 - Allowed | Allows device name to be sent for Windows Diagnostic Data. If this policy is Not Configured or set to 0 (Disabled), Device Name won't be sent and won't be visible in Windows Update for Business reports, showing `#` instead. |
|
||||
| **System/**[**AllowUpdateComplianceProcessing**](/windows/client-management/mdm/policy-csp-system#system-allowUpdateComplianceProcessing) |Integer | 16 - Allowed | Enables data flow through Windows Update for Business report's data processing system and indicates a device's explicit enrollment to the service. |
|
||||
| **System/**[AllowCommercialDataPipeline](/windows/client-management/mdm/policy-csp-system#system-allowcommercialdatapipeline) | Integer | 1 - Enabled | Configures Microsoft to be the processor of the Windows diagnostic data collected from an Azure Active Directory-joined device. |
|
||||
|
||||
### Group policies
|
||||
@ -58,7 +58,7 @@ All Group policies that need to be configured for Windows Update for Business re
|
||||
|**Allow Telemetry** | 1 - Basic |Configures the maximum allowed diagnostic data to be sent to Microsoft. Individual users can still set this value lower than what the policy defines. For more information, see the **Configure telemetry opt-in setting user interface**. |
|
||||
|**Configure telemetry opt-in setting user interface** | 1 - Disable diagnostic data opt-in Settings |(in Windows 10, version 1803 and later) Determines whether users of the device can adjust diagnostic data to levels lower than the level defined by AllowTelemetry. We recommend that you disable this policy, otherwise the effective diagnostic data level on devices might not be sufficient. |
|
||||
|**Allow device name to be sent in Windows diagnostic data** | 1 - Enabled | Allows device name to be sent for Windows Diagnostic Data. If this policy is Not Configured or Disabled, Device Name won't be sent and won't be visible in Windows Update for Business reports, showing `#` instead. |
|
||||
|**Allow Update Compliance processing** | 16 - Enabled | Enables data flow through Windows Update for Business reports's data processing system and indicates a device's explicit enrollment to the service. |
|
||||
|**Allow Update Compliance processing** | 16 - Enabled | Enables data flow through Windows Update for Business report's data processing system and indicates a device's explicit enrollment to the service. |
|
||||
| **Allow commercial data pipeline** | 1 - Enabled | Configures Microsoft to be the processor of the Windows diagnostic data collected from an Azure Active Directory-joined device. |
|
||||
|
||||
## Required endpoints
|
||||
|
@ -32,7 +32,7 @@ There are several resources that you can use to find help with Windows Update fo
|
||||
|
||||
## Send product feedback
|
||||
|
||||
Use the product feedback option to offer suggestions for new features and functionality, or for suggesting changes to the current Windows Update for Business reports features. You can share feedback directly to the Windows Update for Business reports product group. To provide product feedback:
|
||||
Use the product feedback option to offer suggestions for new features and functionality, or to suggest changes to the current Windows Update for Business reports features. You can share feedback directly to the Windows Update for Business reports product group. To provide product feedback:
|
||||
|
||||
1. In the upper right corner of the Azure portal, select the feedback icon.
|
||||
1. Select either the smile or the frown to rate your satisfaction with your experience.
|
||||
@ -48,8 +48,8 @@ You can open support requests directly from the Azure portal. If the **Help + S
|
||||
1. Open the **Help + Support** page from the following locations:
|
||||
- In the [Send product feedback](#send-product-feedback) flyout, select the **contact support** link.
|
||||
- From the Azure portal, select **New support request** under the **Support + Troubleshooting** heading.
|
||||
1. Select **Create a support request** which opens the new support request page.
|
||||
1. On the **Problem description** tab, provide information about the issue. The below items in ***bold italics*** should be used to help ensure an Windows Update for Business reports engineer receives your support request:
|
||||
1. Select **Create a support request**, which opens the new support request page.
|
||||
1. On the **Problem description** tab, provide information about the issue. The following items in ***bold italics*** should be used to help ensure a Windows Update for Business reports engineer receives your support request:
|
||||
- **Summary** - Brief description of the issue
|
||||
- **Issue type** - ***Technical***
|
||||
- **Subscription** - Select the subscription used for Windows Update for Business reports
|
||||
@ -90,7 +90,7 @@ To share feedback about the Microsoft Learn platform, see [Microsoft Learn feedb
|
||||
|
||||
## Troubleshooting tips
|
||||
|
||||
Use the troubleshooting tips below to resolve commonly encountered problems when using Windows Update for Business reports:
|
||||
Use the following troubleshooting tips to resolve the most common problems when using Windows Update for Business reports:
|
||||
|
||||
### Verify client configuration
|
||||
|
||||
@ -103,8 +103,8 @@ The first step in troubleshooting Windows Update for Business reports is ensurin
|
||||
|
||||
### Devices have been correctly configured but aren't showing up in Windows Update for Business reports
|
||||
|
||||
It takes some time for data to appear in Windows Update for Business reports for the first time or if you moved to a new Log Analytics workspace. To learn more about data latencies for Windows Update for Business reports, review [Windows Update for Business reports data latency](wufb-reports-use.md#data-latency).
|
||||
It takes some time for data to appear in Windows Update for Business reports for the first time, or if you moved to a new Log Analytics workspace. To learn more about data latencies for Windows Update for Business reports, review [Windows Update for Business reports data latency](wufb-reports-use.md#data-latency).
|
||||
|
||||
### Devices are appearing, but without a device name
|
||||
|
||||
Device Name is an opt-in via policy starting in Windows 10 version 1803. Review the required policies for enabling device name in the [Manually configuring devices for Windows Update for Business reports](wufb-reports-configuration-manual.md) article.
|
||||
Device Name is an opt-in via policy. Review the required policies for enabling device name in the [Manually configuring devices for Windows Update for Business reports](wufb-reports-configuration-manual.md) article.
|
||||
|
@ -19,7 +19,7 @@ ms.technology: itpro-updates
|
||||
> [!Important]
|
||||
> As of August 17, 2022, a new step needs to be taken to ensure access to Windows Update for Business reports and the `CommercialID` is no longer required. For more information, see [Configure Windows Update for Business reports settings](wufb-reports-enable.md#bkmk_admin-center).
|
||||
|
||||
Windows Update for Business reports is a cloud-based solution that provides information about the compliance of your Azure Active Directory-joined devices with Windows updates. Windows Update for Business reports is offered through the [Azure portal](https://portal.azure.com), and it's included as part of the Windows 10 or Windows 11 prerequisite licenses. Windows Update for Business reports helps you:
|
||||
Windows Update for Business reports is a cloud-based solution that provides information about your Azure Active Directory-joined devices' compliance with Windows updates. Windows Update for Business reports is offered through the [Azure portal](https://portal.azure.com), and it's included as part of the Windows 10 or Windows 11 prerequisite licenses. Windows Update for Business reports helps you:
|
||||
|
||||
- Monitor security, quality, and feature updates for Windows 11 and Windows 10 devices
|
||||
- Report on devices with update compliance issues
|
||||
@ -37,7 +37,7 @@ Some of the benefits of Windows Update for Business reports are:
|
||||
Currently, Windows Update for Business reports contains the following features:
|
||||
|
||||
- [Windows Update for Business reports workbook](wufb-reports-workbook.md)
|
||||
- Compliance status [charts in the Microsoft 365 admin](update-status-admin-center.md)
|
||||
- Compliance status [charts in the Microsoft 365 admin](wufb-reports-admin-center.md)
|
||||
- Access to the following [Windows Update for Business reports tables](wufb-reports-schema.md):
|
||||
- UCClient
|
||||
- UCClientReadinessStatus
|
||||
@ -47,7 +47,7 @@ Currently, Windows Update for Business reports contains the following features:
|
||||
- UCUpdateAlert
|
||||
- Client data collection to populate the Windows Update for Business reports tables
|
||||
|
||||
Currently, these new tables are available to all Updates Compliance users. They will be displayed along with the original Updates Compliance tables.
|
||||
Currently, these new tables are available to all Updates Compliance users. They'll be displayed along with the original Updates Compliance tables.
|
||||
|
||||
:::image type="content" source="media/wufb-reports-query-table.png" alt-text="Screenshot of using a custom Kusto (KQL) query on Windows Update for Business reports data in Log Analytics." lightbox="media/wufb-reports-query-table.png":::
|
||||
|
||||
|
@ -19,34 +19,43 @@ ms.technology: itpro-updates
|
||||
> [!Important]
|
||||
> As of August 17, 2022, a new step needs to be taken to ensure access to Windows Update for Business reports, and the CommercialID is no longer required. For more information, see [Configure Windows Update for Business reports settings](wufb-reports-enable.md#bkmk_admin-center).
|
||||
|
||||
## Windows Update for Business reports prerequisites
|
||||
|
||||
Before you begin the process of adding Windows Update for Business reports to your Azure subscription, ensure you meet the prerequisites.
|
||||
|
||||
### Azure and Azure Active Directory
|
||||
## Azure and Azure Active Directory
|
||||
|
||||
- An Azure subscription with [Azure Active Directory](/azure/active-directory/)
|
||||
- Devices must be Azure Active Directory-joined and meet the below OS, diagnostic, and endpoint access requirements.
|
||||
- Devices can be [Azure AD joined](/azure/active-directory/devices/concept-azure-ad-join) or [hybrid Azure AD joined](/azure/active-directory/devices/concept-azure-ad-join-hybrid).
|
||||
- Devices that are [Azure AD registered](/azure/active-directory/devices/concept-azure-ad-register) only (Workplace joined) aren't supported with Windows Update for Business reports.
|
||||
- The Log Analytics workspace must be in a [supported region](#log-analytics-regions)
|
||||
|
||||
### Operating systems and editions
|
||||
## Permissions
|
||||
|
||||
[!INCLUDE [Windows Update for Business reports permissions](./includes/wufb-reports-admin-center-permissions.md)]
|
||||
|
||||
**Log Analytics permissions**:
|
||||
|
||||
- [Log Analytics Contributor](/azure/role-based-access-control/built-in-roles#log-analytics-contributor) role can be used to edit and write queries
|
||||
- [Log Analytics Reader](/azure/role-based-access-control/built-in-roles#log-analytics-reader) role can be used to read data
|
||||
|
||||
## Operating systems and editions
|
||||
|
||||
- Windows 11 Professional, Education, Enterprise, and [Enterprise multi-session](/azure/virtual-desktop/windows-10-multisession-faq) editions
|
||||
- Windows 10 Professional, Education, Enterprise, and [Enterprise multi-session](/azure/virtual-desktop/windows-10-multisession-faq) editions
|
||||
|
||||
Windows Update for Business reports only provides data for the standard Desktop Windows client version and isn't currently compatible with Windows Server, Surface Hub, IoT, or other versions.
|
||||
|
||||
### Windows client servicing channels
|
||||
## Windows client servicing channels
|
||||
|
||||
Windows Update for Business reports supports Windows client devices on the following channels:
|
||||
|
||||
- General Availability Channel
|
||||
- Windows Update for Business reports *counts* Windows Insider Preview devices, but doesn't currently provide detailed deployment insights for them.
|
||||
|
||||
### Diagnostic data requirements
|
||||
## Diagnostic data requirements
|
||||
|
||||
At minimum, Windows Update for Business reports requires devices to send diagnostic data at *Required* level (previously *Basic*). Some queries in Windows Update for Business reports require devices to send diagnostic data at the following levels:
|
||||
At minimum, Windows Update for Business reports requires devices to send diagnostic data at the *Required* level (previously *Basic*). Some queries in Windows Update for Business reports require devices to send diagnostic data at the following levels:
|
||||
|
||||
- *Optional* level (previously *Full*) for Windows 11 devices
|
||||
- *Enhanced* level for Windows 10 devices
|
||||
@ -58,7 +67,7 @@ At minimum, Windows Update for Business reports requires devices to send diagnos
|
||||
|
||||
For more information about what's included in different diagnostic levels, see [Diagnostics, feedback, and privacy in Windows](https://support.microsoft.com/windows/diagnostics-feedback-and-privacy-in-windows-28808a2b-a31b-dd73-dcd3-4559a5199319).
|
||||
|
||||
### Data transmission requirements
|
||||
## Data transmission requirements
|
||||
|
||||
<!--Using include for endpoint access requirements-->
|
||||
[!INCLUDE [Endpoints for Windows Update for Business reports](./includes/wufb-reports-endpoints.md)]
|
||||
@ -66,19 +75,7 @@ For more information about what's included in different diagnostic levels, see [
|
||||
> [!NOTE]
|
||||
> Enrolling into Windows Update for Business reports from the [Azure CLI](/cli/azure) or enrolling programmatically another way currently isn't supported. You must manually add Windows Update for Business reports to your Azure subscription.
|
||||
|
||||
## Microsoft 365 admin center permissions
|
||||
<!--Using include Microsoft 365 admin center permissions-->
|
||||
[!INCLUDE [Windows Update for Business reports script error codes](./includes/wufb-reports-admin-center-permissions.md)]
|
||||
|
||||
## Log Analytics prerequisites
|
||||
|
||||
### Log Analytics permissions
|
||||
|
||||
- To edit and write queries, we recommend the [Log Analytics Contributor](/azure/role-based-access-control/built-in-roles#log-analytics-contributor) role.
|
||||
- To read and only view data, we recommend the [Log Analytics Reader](/azure/role-based-access-control/built-in-roles#log-analytics-reader) role.
|
||||
|
||||
|
||||
### Log Analytics regions
|
||||
## Log Analytics regions
|
||||
|
||||
Windows Update for Business reports can use a Log Analytics workspace in the following regions:
|
||||
|
||||
|
@ -20,7 +20,7 @@ These alerts are activated as a result of an issue that is device-specific. It i
|
||||
|
||||
|Field |Type |Example |Description |
|
||||
|---|---|---|---|
|
||||
| **AlertClassification** | [string](/azure/kusto/query/scalar-data-types/string) | `Error` | Whether this alert is an Error, a Warning, or Informational. |
|
||||
| **AlertClassification** | [string](/azure/kusto/query/scalar-data-types/string) | `Error` | Whether this alert is an Error, a Warning, or Informational |
|
||||
| **AlertId** | [string](/azure/kusto/query/scalar-data-types/string) | `9e107d9d372bb6826bd81d3542a419d6` | The unique identifier of this alert |
|
||||
| **AlertRank** | [int](/azure/kusto/query/scalar-data-types/int) | `1000` | Integer ranking of alert for prioritization during troubleshooting |
|
||||
| **AlertStatus** | [string](/azure/kusto/query/scalar-data-types/string) | `Active` | Whether this alert is Active, Resolved, or Deleted |
|
||||
|
@ -16,7 +16,7 @@ ms.technology: itpro-updates
|
||||
<!--37063317, 30141258, 37063041-->
|
||||
***(Applies to: Windows 11 & Windows 10)***
|
||||
|
||||
Update Event that comes directly from the service-side. The event has only service-side information for one device (client), and one update, in one deployment. This event has certain fields removed from it in favor of being able to show data in near real-time.
|
||||
Update Event that comes directly from the service-side. The event has only service-side information for one device (client), and one update, in one deployment. This event has certain fields removed from it in favor of being able to show data in near real time.
|
||||
|
||||
| Field | Type | Example | Description |
|
||||
|---|---|---|---|
|
||||
|
@ -23,7 +23,7 @@ When the visualizations provided in the default experience don't fulfill your re
|
||||
|
||||
## Schema
|
||||
|
||||
The table below summarizes the different tables that are part of the Windows Update for Business reports solution. To learn how to navigate Azure Monitor Logs to find this data, see [Get started with log queries in Azure Monitor](/azure/azure-monitor/log-query/get-started-queries).
|
||||
The following table summarizes the different tables that are part of the Windows Update for Business reports solution. To learn how to navigate Azure Monitor Logs to find this data, see [Get started with log queries in Azure Monitor](/azure/azure-monitor/log-query/get-started-queries).
|
||||
|
||||
> [!NOTE]
|
||||
> Data is collected daily. The TimeGenerated field shows the time data was collected. It's added by Log Analytics when data is collected. Device data from the past 28 days is collected, even if no new data has been generated since the last time. LastScan is a clearer indicator of data freshness (that is, the last time the values were updated), while TimeGenerated indicates the freshness of data within Log Analytics.
|
||||
|
@ -2,7 +2,7 @@
|
||||
title: Use the Windows Update for Business reports data
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
description: How to use the Windows Update for Business reports data.
|
||||
description: How to use the Windows Update for Business reports data for custom solutions using tools like Azure Monitor Logs.
|
||||
ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
@ -40,7 +40,7 @@ UCUpdateAlert
|
||||
|
||||
Windows Update for Business reports uses Windows client diagnostic data as its data source. After you add Windows Update for Business reports and appropriately configure your devices, it could take 48-72 hours before they first appear.
|
||||
|
||||
The data powering Windows Update for Business reports is refreshed every 24 hours, and refreshes with the latest data from all of your organization's devices that have been seen in the past 28 days. The entire set of data is refreshed in each daily snapshot, which means that the same data can be ingested again even if no new data actually arrived from the device since the last snapshot. Snapshot time can be determined by the TimeGenerated field for each record, while LastScan can be used to roughly determine the freshness of each record's data. Device connectivity to the internet and generally how active the device is influences how long it will take before it appears in Windows Update for Business reports.
|
||||
The data powering Windows Update for Business reports is refreshed every 24 hours, and refreshes with the latest data from all of your organization's devices that have been seen in the past 28 days. The entire set of data is refreshed in each daily snapshot, which means that the same data can be ingested again even if no new data arrived from the device since the last snapshot. Snapshot time can be determined by the TimeGenerated field for each record, while LastScan can be used to roughly determine the freshness of each record's data. Device connectivity to the internet and generally how active the device is influences how long it will take before it appears in Windows Update for Business reports.
|
||||
|
||||
| Data Type | Data upload rate from device | Data Latency |
|
||||
|--|--|--|
|
||||
@ -57,7 +57,7 @@ The data powering Windows Update for Business reports is refreshed every 24 hour
|
||||
|
||||
Windows Update for Business reports is built on the Azure Monitor Logs platform. All Windows Update for Business reports-related data is collected in a Log Analytics workspace, where the data is available for querying. Understanding the Azure Monitor Logs tools and features at your disposal, all integrated within Azure portal, can deeply enhance your experience and complement Windows Update for Business reports.
|
||||
|
||||
See the Azure Monitor Logs articles below to learn how to:
|
||||
See the following Azure Monitor Logs articles to learn how to:
|
||||
- [Query log data effectively in Azure Monitor Logs](/azure/log-analytics/log-analytics-log-searches).
|
||||
- [Create and share dashboards of data in a Log Analytics workspace](/azure/log-analytics/log-analytics-dashboards).
|
||||
- [Set up alerts in Azure Monitor](/azure/log-analytics/log-analytics-alerts) to always stay informed about the critical issues you care about most.
|
||||
|
@ -19,7 +19,7 @@ ms.technology: itpro-updates
|
||||
> [!IMPORTANT]
|
||||
> As of August 17, 2022, a new step needs to be taken to ensure access to Windows Update for Business reports and the `CommercialID` is no longer required. For more information, see [Configure Windows Update for Business reports settings](wufb-reports-enable.md#bkmk_admin-center).
|
||||
|
||||
[Windows Update for Business reports](wufb-reports-overview.md) presents information commonly needed by updates administrators in an easy to use format. Windows Update for Business reports uses [Azure Workbooks](/azure/azure-monitor/visualize/workbooks-getting-started) to give you a visual representation of your compliance data. The workbook is broken down into four tab sections:
|
||||
[Windows Update for Business reports](wufb-reports-overview.md) presents information commonly needed by updates administrators in an easy-to-use format. Windows Update for Business reports uses [Azure Workbooks](/azure/azure-monitor/visualize/workbooks-getting-started) to give you a visual representation of your compliance data. The workbook is broken down into four tab sections:
|
||||
|
||||
- [Summary](#summary-tab)
|
||||
- [Quality updates](#quality-updates-tab)
|
||||
@ -76,7 +76,7 @@ The **Quality updates** tab displays generalized data at the top by using tiles.
|
||||
Selecting **View details** on any of the tiles displays a flyout with a chart that displays the first 250 items. Select `...` from the flyout to export the full list, or display the query in [Log Analytics](/azure/azure-monitor/logs/log-analytics-tutorial).
|
||||
|
||||
|
||||
Below the tiles, the **Quality updates** tab is subdivided into **Update status** and **Device status** groups. These different chart groups allow you to easily discover trends in compliance data. For instance, you may remember that about third of your devices were in the installing state yesterday, but this number didn't change as much as you were expecting. That unexpected trend may cause you to investigate and resolve a potential issue before end-users are impacted.
|
||||
Below the tiles, the **Quality updates** tab is subdivided into **Update status** and **Device status** groups. These different chart groups allow you to easily discover trends in compliance data. For instance, you may remember that about third of your devices were in the installing state yesterday, but this number didn't change as much as you were expecting. That unexpected trend may cause you to investigate and resolve a potential issue before end users are impacted.
|
||||
|
||||
### <a name="bkmk_update-group-quality"></a> Update status group for quality updates
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user