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

rename files and update links

Browse Source
This commit is contained in:
Meghan Stewart 2022-11-02 14:04:14 -07:00
parent 914dc79899
commit d42c8c394c
26 changed files with 168 additions and 88 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

82
.openpublishing.redirection.json
View File

@ -20069,6 +20069,86 @@
"source_path": "windows/deployment/upgrade/upgrade-error-codes.md", "source_path": "windows/deployment/upgrade/upgrade-error-codes.md",
"redirect_url": "/troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json", "redirect_url": "/troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json",
"redirect_document_id": false "redirect_document_id": false
} },
{
"source_path": "windows/deployment/update/update-compliance-v2-configuration-manual.md",
"redirect_url": "/windows/deployment/update/wufb-reports-configuration-manual",
"redirect_document_id": false
},
{
"source_path": "windows/deployment/update/update-compliance-v2-configuration-mem.md",
"redirect_url": "/windows/deployment/update/wufb-reports-configuration-intune",
"redirect_document_id": false
},
{
"source_path": "windows/deployment/update/update-compliance-v2-configuration-script.md",
"redirect_url": "/windows/deployment/update/wufb-reports-configuration-script",
"redirect_document_id": false
},
{
"source_path": "windows/deployment/update/update-compliance-v2-enable.md",
"redirect_url": "/windows/deployment/update/wufb-reports-enable",
"redirect_document_id": false
},
{
"source_path": "windows/deployment/update/update-compliance-v2-help.md",
"redirect_url": "/windows/deployment/update/wufb-reports-help",
"redirect_document_id": false
},
{
"source_path": "windows/deployment/update/update-compliance-v2-overview.md",
"redirect_url": "/windows/deployment/update/wufb-reports-overview",
"redirect_document_id": false
},
{
"source_path": "windows/deployment/update/update-compliance-v2-prerequisites.md",
"redirect_url": "/windows/deployment/update/wufb-reports-prerequisites",
"redirect_document_id": false
},
{
"source_path": "windows/deployment/update/update-compliance-v2-schema-ucclient.md",
"redirect_url": "/windows/deployment/update/wufb-reports-schema-ucclient",
"redirect_document_id": false
},
{
"source_path": "windows/deployment/update/update-compliance-v2-schema-ucclientreadinessstatus.md",
"redirect_url": "/windows/deployment/update/wufb-reports-schema-ucclientreadinessstatus",
"redirect_document_id": false
},
{
"source_path": "windows/deployment/update/update-compliance-v2-schema-ucclientupdatestatus.md",
"redirect_url": "/windows/deployment/update/wufb-reports-schema-ucclientupdatestatus",
"redirect_document_id": false
},
{
"source_path": "windows/deployment/update/update-compliance-v2-schema-ucdevicealert.md",
"redirect_url": "/windows/deployment/update/wufb-reports-schema-ucdevicealert",
"redirect_document_id": false
},
{
"source_path": "windows/deployment/update/update-compliance-v2-schema-ucserviceupdatestatus.md",
"redirect_url": "/windows/deployment/update/wufb-reports-schema-ucserviceupdatestatus",
"redirect_document_id": false
},
{
"source_path": "windows/deployment/update/update-compliance-v2-schema-ucupdatealert.md",
"redirect_url": "/windows/deployment/update/wufb-reports-schema-ucupdatealert",
"redirect_document_id": false
},
{
"source_path": "windows/deployment/update/update-compliance-v2-schema.md",
"redirect_url": "/windows/deployment/update/wufb-reports-schema",
"redirect_document_id": false
},
{
"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-compliance-v2-workbook.md",
"redirect_url": "/windows/deployment/update/wufb-reports-workbook",
"redirect_document_id": false
}
] ]
} }

32
windows/deployment/TOC.yml
View File

@ -187,45 +187,45 @@
- name: Windows Update for Business reports - name: Windows Update for Business reports
items: items:
- name: Windows Update for Business reports overview - name: Windows Update for Business reports overview
href: update/update-compliance-v2-overview.md href: update/wufb-reports-overview.md
- name: Enable Windows Update for Business reports - name: Enable Windows Update for Business reports
items: items:
- name: Windows Update for Business reports prerequisites - name: Windows Update for Business reports prerequisites
href: update/update-compliance-v2-prerequisites.md href: update/wufb-reports-prerequisites.md
- name: Enable Windows Update for Business reports - name: Enable Windows Update for Business reports
href: update/update-compliance-v2-enable.md href: update/wufb-reports-enable.md
- name: Configure clients with a script - name: Configure clients with a script
href: update/update-compliance-v2-configuration-script.md href: update/wufb-reports-configuration-script.md
- name: Configure clients manually - name: Configure clients manually
href: update/update-compliance-v2-configuration-manual.md href: update/wufb-reports-configuration-manual.md
- name: Configure clients with Microsoft Endpoint Manager - name: Configure clients with Microsoft Endpoint Manager
href: update/update-compliance-v2-configuration-mem.md href: update/wufb-reports-configuration-intune.md
- name: Use Windows Update for Business reports - name: Use Windows Update for Business reports
items: items:
- name: Windows Update for Business reports workbook - name: Windows Update for Business reports workbook
href: update/update-compliance-v2-workbook.md href: update/wufb-reports-workbook.md
- name: Software updates in the Microsoft admin center - name: Software updates in the Microsoft admin center
href: update/update-status-admin-center.md href: update/update-status-admin-center.md
- name: Use Windows Update for Business reports data - name: Use Windows Update for Business reports data
href: update/update-compliance-v2-use.md href: update/wufb-reports-use.md
- name: Feedback, support, and troubleshooting - name: Feedback, support, and troubleshooting
href: update/update-compliance-v2-help.md href: update/wufb-reports-help.md
- name: Windows Update for Business reports schema reference - name: Windows Update for Business reports schema reference
items: items:
- name: Windows Update for Business reports schema reference - name: Windows Update for Business reports schema reference
href: update/update-compliance-v2-schema.md href: update/wufb-reports-schema.md
- name: UCClient - name: UCClient
href: update/update-compliance-v2-schema-ucclient.md href: update/wufb-reports-schema-ucclient.md
- name: UCClientReadinessStatus - name: UCClientReadinessStatus
href: update/update-compliance-v2-schema-ucclientreadinessstatus.md href: update/wufb-reports-schema-ucclientreadinessstatus.md
- name: UCClientUpdateStatus - name: UCClientUpdateStatus
href: update/update-compliance-v2-schema-ucclientupdatestatus.md href: update/wufb-reports-schema-ucclientupdatestatus.md
- name: UCDeviceAlert - name: UCDeviceAlert
href: update/update-compliance-v2-schema-ucdevicealert.md href: update/wufb-reports-schema-ucdevicealert.md
- name: UCServiceUpdateStatus - name: UCServiceUpdateStatus
href: update/update-compliance-v2-schema-ucserviceupdatestatus.md href: update/wufb-reports-schema-ucserviceupdatestatus.md
- name: UCUpdateAlert - name: UCUpdateAlert
href: update/update-compliance-v2-schema-ucupdatealert.md href: update/wufb-reports-schema-ucupdatealert.md
- name: Monitor updates with Update Compliance - name: Monitor updates with Update Compliance
href: update/update-compliance-monitor.md href: update/update-compliance-monitor.md
items: items:

4
windows/deployment/update/includes/update-compliance-admin-center-permissions.md → windows/deployment/update/includes/wufb-reports-admin-center-permissions.md
View File

@ -8,8 +8,8 @@ ms.topic: include
ms.date: 08/18/2022 ms.date: 08/18/2022
ms.localizationpriority: medium ms.localizationpriority: medium
--- ---
<!--This file is shared by updates/update-compliance-v2-enable.md and the update/update-status-admin-center.md articles. Headings may be driven by article context. --> <!--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 Update Compliance](../update-compliance-v2-enable.md) requires access to the [Microsoft admin center software updates (preview) page](../update-status-admin-center.md) as does displaying Update Compliance data in the admin center. The following permissions are needed for access to the [Microsoft 365 admin center](https://admin.microsoft.com): [Enabling Update Compliance](../wufb-reports-enable.md) requires access to the [Microsoft admin center software updates (preview) page](../update-status-admin-center.md) as does displaying Update Compliance data in the admin center. The following permissions are needed for access to the [Microsoft 365 admin center](https://admin.microsoft.com):
- To enable Update Compliance, edit Update Compliance configuration settings, and view the **Windows** tab in the **Software Updates** page: - To enable Update Compliance, edit Update Compliance configuration settings, and view the **Windows** tab in the **Software Updates** page:

2
windows/deployment/update/includes/update-compliance-endpoints.md → windows/deployment/update/includes/wufb-reports-endpoints.md
View File

@ -8,7 +8,7 @@ ms.topic: include
ms.date: 04/06/2022 ms.date: 04/06/2022
ms.localizationpriority: medium ms.localizationpriority: medium
--- ---
<!--This file is shared by updates/update-compliance-v2-prerequisites.md and the update/update-compliance-configuration-manual.md articles. Headings are driven by article context. --> <!--This file is shared by updates/wufb-reports-prerequisites.md and the update/update-compliance-configuration-manual.md articles. Headings are driven by article context. -->
Devices must be able to contact the following endpoints in order to authenticate and send diagnostic data: Devices must be able to contact the following endpoints in order to authenticate and send diagnostic data:

4
windows/deployment/update/includes/update-compliance-onboard-admin-center.md → windows/deployment/update/includes/wufb-reports-onboard-admin-center.md
View File

@ -8,11 +8,11 @@ ms.topic: include
ms.date: 08/18/2022 ms.date: 08/18/2022
ms.localizationpriority: medium ms.localizationpriority: medium
--- ---
<!--This file is shared by updates/update-compliance-v2-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/update-status-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. 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. 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. 1. In the **Software Updates** page, select the **Windows** tab.
1. When you select the **Windows** tab for the first time, you'll be asked to **Configure Settings**. This tab is populated by data from [Update Compliance](../update-compliance-v2-overview.md). Verify or supply the following information about the settings for Update Compliance: 1. When you select the **Windows** tab for the first time, you'll be asked to **Configure Settings**. This tab is populated by data from [Update Compliance](../wufb-reports-overview.md). Verify or supply the following information about the settings for Update Compliance:
- The Azure subscription - The Azure subscription
- The Log Analytics workspace - The Log Analytics workspace

2
windows/deployment/update/includes/update-compliance-script-error-codes.md → windows/deployment/update/includes/wufb-reports-script-error-codes.md
View File

@ -8,7 +8,7 @@ ms.topic: include
ms.date: 08/18/2022 ms.date: 08/18/2022
ms.localizationpriority: medium ms.localizationpriority: medium
--- ---
<!--This file is shared by updates/update-compliance-v2-configuration-script.md and the update/update-compliance-configuration-script.md articles. Headings are driven by article context. --> <!--This file is shared by updates/wufb-reports-configuration-script.md and the update/update-compliance-configuration-script.md articles. Headings are driven by article context. -->
|Error |Description | |Error |Description |
|---------|---------| |---------|---------|
| 1 | General unexpected error| | 1 | General unexpected error|

4
windows/deployment/update/includes/update-compliance-verify-device-configuration.md → windows/deployment/update/includes/wufb-reports-verify-device-configuration.md
View File

@ -8,7 +8,7 @@ ms.topic: include
ms.date: 08/10/2022 ms.date: 08/10/2022
ms.localizationpriority: medium ms.localizationpriority: medium
--- ---
<!--This file is shared by updates/update-compliance-v2-help.md and the update/update-compliance-v2-configuration-script.md articles. Headings are driven by article context. --> <!--This file is shared by updates/wufb-reports-help.md and the update/wufb-reports-configuration-script.md articles. Headings are driven by article context. -->
In some cases, you may need to manually verify the device configuration has the `AllowUpdateComplianceProcessing` policy enabled. To verify the setting, use the following steps: In some cases, you may need to manually verify the device configuration has the `AllowUpdateComplianceProcessing` policy enabled. To verify the setting, use the following steps:
@ -35,7 +35,7 @@ In some cases, you may need to manually verify the device configuration has the
1. Go to **Start**, select **Settings** > **Privacy** > **Diagnostics & feedback**. 1. Go to **Start**, select **Settings** > **Privacy** > **Diagnostics & feedback**.
1. Under **View diagnostic data**, select **Open Diagnostic Data Viewer**. 1. Under **View diagnostic data**, select **Open Diagnostic Data Viewer**.
1. When the Diagnostic Data Viewer opens, type `SoftwareUpdateClientTelemetry` in the search field. Verify the following items: 1. When the Diagnostic Data Viewer opens, type `SoftwareUpdateClientTelemetry` in the search field. Verify the following items:
- The **EnrolledTenantID** field under **m365a** should equal the `CommercialID` of your Log Analytics workspace for Update Compliance. `CommercialID` is no longer required for the [preview version of Updates Compliance](../update-compliance-v2-overview.md), but the value may still be listed in this field. - The **EnrolledTenantID** field under **m365a** should equal the `CommercialID` of your Log Analytics workspace for Update Compliance. `CommercialID` is no longer required for the [preview version of Updates Compliance](../wufb-reports-overview.md), but the value may still be listed in this field.
- The **MSP** field value under **protocol** should be either `16` or `18`. - The **MSP** field value under **protocol** should be either `16` or `18`.
- If you need to send this data to Microsoft Support, select **Export data**. - If you need to send this data to Microsoft Support, select **Export data**.

2
windows/deployment/update/update-compliance-configuration-manual.md
View File

@ -68,7 +68,7 @@ All Group policies that need to be configured for Update Compliance are under **
To enable data sharing between devices, your network, and Microsoft's Diagnostic Data Service, configure your proxy to allow devices to contact the below endpoints. To enable data sharing between devices, your network, and Microsoft's Diagnostic Data Service, configure your proxy to allow devices to contact the below endpoints.
<!--Using include for endpoint access requirements--> <!--Using include for endpoint access requirements-->
[!INCLUDE [Endpoints for Update Compliance](./includes/update-compliance-endpoints.md)] [!INCLUDE [Endpoints for Update Compliance](./includes/wufb-reports-endpoints.md)]
## Required services ## Required services

4
windows/deployment/update/update-compliance-configuration-script.md
View File

@ -50,9 +50,9 @@ Open `RunConfig.bat` and configure the following (assuming a first-run, with `ru
## Script errors ## Script errors
<!--Using include for script errors--> <!--Using include for script errors-->
[!INCLUDE [Update Compliance script error codes](./includes/update-compliance-script-error-codes.md)] [!INCLUDE [Update Compliance script error codes](./includes/wufb-reports-script-error-codes.md)]
## Verify device configuration ## Verify device configuration
<!--Using include for verifying device configuration--> <!--Using include for verifying device configuration-->
[!INCLUDE [Endpoints for Update Compliance](./includes/update-compliance-verify-device-configuration.md)]: [!INCLUDE [Endpoints for Update Compliance](./includes/wufb-reports-verify-device-configuration.md)]:

10
windows/deployment/update/update-status-admin-center.md
View File

@ -15,7 +15,7 @@ ms.technology: itpro-updates
# Microsoft admin center software updates (preview) page # Microsoft admin center software updates (preview) page
<!--37063317, 30141258, 37063041, ID2616577, ID2582518 --> <!--37063317, 30141258, 37063041, ID2616577, ID2582518 -->
***(Applies to: Windows 11 & Windows 10 using [Update Compliance](update-compliance-v2-overview.md) and the [Microsoft 365 admin center](/microsoft-365/admin/admin-overview/admin-center-overview))*** ***(Applies to: Windows 11 & Windows 10 using [Update Compliance](wufb-reports-overview.md) and the [Microsoft 365 admin center](/microsoft-365/admin/admin-overview/admin-center-overview))***
> [!Important] > [!Important]
> This information relates to a preview feature that's available for early testing and use in a production environment. This feature is fully supported but it's still in active development and may receive substantial changes until it becomes generally available. > This information relates to a preview feature that's available for early testing and use in a production environment. This feature is fully supported but it's still in active development and may receive substantial changes until it becomes generally available.
@ -32,7 +32,7 @@ The **Software updates** page has following tabs to assist you in monitoring upd
## Permissions ## Permissions
<!--Using include Microsoft 365 admin center permissions--> <!--Using include Microsoft 365 admin center permissions-->
[!INCLUDE [Update Compliance script error codes](./includes/update-compliance-admin-center-permissions.md)] [!INCLUDE [Update Compliance script error codes](./includes/wufb-reports-admin-center-permissions.md)]
## Limitations ## Limitations
@ -43,11 +43,11 @@ Update Compliance is a Windows service hosted in Azure that uses Windows diagnos
<!--Using include for onboarding Update Compliance through the Microsoft 365 admin center--> <!--Using include for onboarding Update Compliance through the Microsoft 365 admin center-->
[!INCLUDE [Onboarding Update Compliance through the Microsoft 365 admin center](./includes/update-compliance-onboard-admin-center.md)] [!INCLUDE [Onboarding Update Compliance through the Microsoft 365 admin center](./includes/wufb-reports-onboard-admin-center.md)]
## The Windows tab ## The Windows tab
The **Windows** tab in the **Software updates** page in the Microsoft admin center is populated by data from [Update Compliance](update-compliance-v2-overview.md). The tab contains a high-level overview of update compliance for Windows clients in your environment. The tab displays two charts **Windows update status** and **End of service**. The Update Compliance data that populates these charts refreshes every 24 hours. For more information, see [Update Compliance data latency](update-compliance-v2-use.md#update-compliance-data-latency). The **Windows** tab in the **Software updates** page in the Microsoft admin center is populated by data from [Update Compliance](wufb-reports-overview.md). The tab contains a high-level overview of update compliance for Windows clients in your environment. The tab displays two charts **Windows update status** and **End of service**. The Update Compliance data that populates these charts refreshes every 24 hours. For more information, see [Update Compliance data latency](wufb-reports-use.md#update-compliance-data-latency).
### Windows update status chart ### Windows update status chart
@ -69,4 +69,4 @@ The **End of service** chart list the number of devices running an operating sys
## Next steps ## Next steps
Use [Update Compliance](update-compliance-v2-overview.md) to display additional data about the status of Windows updates. Use [Update Compliance](wufb-reports-overview.md) to display additional data about the status of Windows updates.

10
windows/deployment/update/update-compliance-v2-configuration-mem.md → windows/deployment/update/wufb-reports-configuration-intune.md
View File

@ -18,14 +18,14 @@ ms.technology: itpro-updates
***(Applies to: Windows 11 & Windows 10 managed by [Microsoft Endpoint Manager](/mem/endpoint-manager-overview))*** ***(Applies to: Windows 11 & Windows 10 managed by [Microsoft Endpoint Manager](/mem/endpoint-manager-overview))***
> [!Important] > [!Important]
> - As of August 17, 2022, a new step needs to be taken to ensure access to the preview version of Update Compliance and the `CommercialID` is no longer required. For more information, see [Configure Update Compliance settings through the Microsoft 365 admin center](update-compliance-v2-enable.md#bkmk_admin-center). > - As of August 17, 2022, a new step needs to be taken to ensure access to the preview version of Update Compliance and the `CommercialID` is no longer required. For more information, see [Configure Update Compliance settings through the Microsoft 365 admin center](wufb-reports-enable.md#bkmk_admin-center).
> - This information relates to a preview feature that's available for early testing and use in a production environment. This feature is fully supported but it's still in active development and may receive substantial changes until it becomes generally available. > - This information relates to a preview feature that's available for early testing and use in a production environment. This feature is fully supported but it's still in active development and may receive substantial changes until it becomes generally available.
This article is specifically targeted at configuring devices enrolled to [Microsoft Endpoint Manager](/mem/endpoint-manager-overview) for Update Compliance, within Microsoft Endpoint Manager itself. Configuring devices for Update Compliance in Microsoft Endpoint Manager breaks down to the following steps: This article is specifically targeted at configuring devices enrolled to [Microsoft Endpoint Manager](/mem/endpoint-manager-overview) for Update Compliance, within Microsoft Endpoint Manager itself. Configuring devices for Update Compliance in Microsoft Endpoint Manager 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. [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 Update Compliance](update-compliance-v2-use.md). 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 Update Compliance](wufb-reports-use.md).
> [!TIP] > [!TIP]
> If you need to troubleshoot client enrollment, consider deploying the [configuration script](#deploy-the-configuration-script) as a Win32 app to a few devices and reviewing the logs it creates. Additional checks are performed with the script to ensure devices are correctly configured. > If you need to troubleshoot client enrollment, consider deploying the [configuration script](#deploy-the-configuration-script) as a Win32 app to a few devices and reviewing the logs it creates. Additional checks are performed with the script to ensure devices are correctly configured.
@ -69,7 +69,7 @@ Create a configuration profile that will set the required policies for Update Co
1. Select **Platform**="Windows 10 and later" and **Profile type**="Templates". 1. Select **Platform**="Windows 10 and later" and **Profile type**="Templates".
1. For **Template name**, select **Custom**, and then select **Create**. 1. For **Template name**, select **Custom**, and then select **Create**.
1. You're now on the Configuration profile creation screen. On the **Basics** tab, give a **Name** and **Description**. 1. You're now on the Configuration profile creation screen. On the **Basics** tab, give a **Name** and **Description**.
1. On the **Configuration settings** page, you'll be adding multiple OMA-URI Settings that correspond to the policies described in [Manually configuring devices for Update Compliance](update-compliance-v2-configuration-manual.md). 1. On the **Configuration settings** page, you'll be adding multiple OMA-URI Settings that correspond to the policies described in [Manually configuring devices for Update Compliance](wufb-reports-configuration-manual.md).
1. Add a setting to **Allow commercial data pipeline**; this policy is required for Update Compliance: 1. Add a setting to **Allow commercial data pipeline**; this policy is required for Update Compliance:
- **Name**: Allow commercial data pipeline - **Name**: Allow commercial data pipeline
@ -108,10 +108,10 @@ Create a configuration profile that will set the required policies for Update Co
## Deploy the configuration script ## Deploy the configuration script
The [Update Compliance Configuration Script](update-compliance-v2-configuration-script.md) is a useful tool for properly enrolling devices in Update Compliance, 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 Update Compliance](update-compliance-v2-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). The [Update Compliance Configuration Script](wufb-reports-configuration-script.md) is a useful tool for properly enrolling devices in Update Compliance, 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 Update Compliance](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 Update Compliance, 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 Update Compliance 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 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 Update Compliance, 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 Update Compliance devices.
## Next steps ## Next steps
[Use Update Compliance](update-compliance-v2-use.md) [Use Update Compliance](wufb-reports-use.md)

10
windows/deployment/update/update-compliance-v2-configuration-manual.md → windows/deployment/update/wufb-reports-configuration-manual.md
View File

@ -18,10 +18,10 @@ ms.technology: itpro-updates
***(Applies to: Windows 11 & Windows 10)*** ***(Applies to: Windows 11 & Windows 10)***
> [!Important] > [!Important]
> - As of August 17, 2022, a new step needs to be taken to ensure access to the preview version of Update Compliance and the `CommercialID` is no longer required. For more information, see [Configure Update Compliance settings through the Microsoft 365 admin center](update-compliance-v2-enable.md#bkmk_admin-center). > - As of August 17, 2022, a new step needs to be taken to ensure access to the preview version of Update Compliance and the `CommercialID` is no longer required. For more information, see [Configure Update Compliance settings through the Microsoft 365 admin center](wufb-reports-enable.md#bkmk_admin-center).
> - This information relates to a preview feature that's available for early testing and use in a production environment. This feature is fully supported but it's still in active development and may receive substantial changes until it becomes generally available. > - This information relates to a preview feature that's available for early testing and use in a production environment. This feature is fully supported but it's still in active development and may receive substantial changes until it becomes generally available.
There are a number of requirements to consider when manually configuring devices for Update Compliance. These requirements can potentially change with newer versions of Windows client. The [Update Compliance configuration script](update-compliance-v2-configuration-script.md) will be updated when any configuration requirements change so only a redeployment of the script will be required. There are a number of requirements to consider when manually configuring devices for Update Compliance. These requirements can potentially change with newer versions of Windows client. The [Update Compliance configuration script](wufb-reports-configuration-script.md) will be updated when any configuration requirements change so only a redeployment of the script will be required.
The requirements are separated into different categories: The requirements are separated into different categories:
@ -67,12 +67,12 @@ All Group policies that need to be configured for Update Compliance are under **
To enable data sharing between devices, your network, and Microsoft's Diagnostic Data Service, configure your proxy to allow devices to contact the below endpoints. To enable data sharing between devices, your network, and Microsoft's Diagnostic Data Service, configure your proxy to allow devices to contact the below endpoints.
<!--Using include for endpoint access requirements--> <!--Using include for endpoint access requirements-->
[!INCLUDE [Endpoints for Update Compliance](./includes/update-compliance-endpoints.md)] [!INCLUDE [Endpoints for Update Compliance](./includes/wufb-reports-endpoints.md)]
## Required services ## Required services
Many Windows and Microsoft services are required to ensure that not only the device can function, but Update Compliance can see device data. It's recommended that you allow all default services from the out-of-box experience to remain running. The [Update Compliance Configuration Script](update-compliance-v2-configuration-script.md) checks whether the majority of these services are running or are allowed to run automatically. Many Windows and Microsoft services are required to ensure that not only the device can function, but Update Compliance can see device data. It's recommended that you allow all default services from the out-of-box experience to remain running. The [Update Compliance Configuration Script](wufb-reports-configuration-script.md) checks whether the majority of these services are running or are allowed to run automatically.
## Next steps ## Next steps
[Use Update Compliance](update-compliance-v2-use.md) [Use Update Compliance](wufb-reports-use.md)

12
windows/deployment/update/update-compliance-v2-configuration-script.md → windows/deployment/update/wufb-reports-configuration-script.md
View File

@ -18,14 +18,14 @@ ms.technology: itpro-updates
***(Applies to: Windows 11 & Windows 10)*** ***(Applies to: Windows 11 & Windows 10)***
> [!Important] > [!Important]
> - As of August 17, 2022, a new step needs to be taken to ensure access to the preview version of Update Compliance and the `CommercialID` is no longer required. For more information, see [Configure Update Compliance settings through the Microsoft 365 admin center](update-compliance-v2-enable.md#bkmk_admin-center). > - As of August 17, 2022, a new step needs to be taken to ensure access to the preview version of Update Compliance and the `CommercialID` is no longer required. For more information, see [Configure Update Compliance settings through the Microsoft 365 admin center](wufb-reports-enable.md#bkmk_admin-center).
> - This information relates to a preview feature that's available for early testing and use in a production environment. This feature is fully supported but it's still in active development and may receive substantial changes until it becomes generally available. > - This information relates to a preview feature that's available for early testing and use in a production environment. This feature is fully supported but it's still in active development and may receive substantial changes until it becomes generally available.
The Update Compliance Configuration Script is the recommended method of configuring devices to send data to Microsoft for use with Update Compliance. The script configures the registry keys backing policies, ensures required services are running, and more. This script is a recommended complement to configuring the required policies documented in [Manually configured devices for Update Compliance](update-compliance-v2-configuration-manual.md), as it can provide feedback on whether there are any configuration issues outside of policies being configured. The Update Compliance Configuration Script is the recommended method of configuring devices to send data to Microsoft for use with Update Compliance. The script configures the registry keys backing policies, ensures required services are running, and more. This script is a recommended complement to configuring the required policies documented in [Manually configured devices for Update Compliance](wufb-reports-configuration-manual.md), as it can provide feedback on whether there are any configuration issues outside of policies being configured.
## About the script ## About the script
The configuration script configures registry keys directly. Be aware that registry keys can potentially be overwritten by policy settings like Group Policy or MDM. *Reconfiguring devices with the script doesn't reconfigure previously set policies, both in the case of Group Policy and MDM*. If there are conflicts between your Group Policy or MDM configurations and the required configurations listed in [Manually configuring devices for Update Compliance](update-compliance-v2-configuration-manual.md), device data might not appear in Update Compliance correctly. The configuration script configures registry keys directly. Be aware that registry keys can potentially be overwritten by policy settings like Group Policy or MDM. *Reconfiguring devices with the script doesn't reconfigure previously set policies, both in the case of Group Policy and MDM*. If there are conflicts between your Group Policy or MDM configurations and the required configurations listed in [Manually configuring devices for Update Compliance](wufb-reports-configuration-manual.md), device data might not appear in Update Compliance correctly.
You can download the script from the [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=101086). Keep reading to learn how to configure the script and interpret error codes that are output in logs for troubleshooting. You can download the script from the [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=101086). Keep reading to learn how to configure the script and interpret error codes that are output in logs for troubleshooting.
@ -52,14 +52,14 @@ Open `RunConfig.bat` and configure the following (assuming a first-run, with `ru
## Verify device configuration ## Verify device configuration
<!--Using include for verifying device configuration--> <!--Using include for verifying device configuration-->
[!INCLUDE [Endpoints for Update Compliance](./includes/update-compliance-verify-device-configuration.md)] [!INCLUDE [Endpoints for Update Compliance](./includes/wufb-reports-verify-device-configuration.md)]
## Script errors ## Script errors
<!--Using include for script errors--> <!--Using include for script errors-->
[!INCLUDE [Update Compliance script error codes](./includes/update-compliance-script-error-codes.md)] [!INCLUDE [Update Compliance script error codes](./includes/wufb-reports-script-error-codes.md)]
## Next steps ## Next steps
[Use Update Compliance](update-compliance-v2-use.md) [Use Update Compliance](wufb-reports-use.md)

20
windows/deployment/update/update-compliance-v2-enable.md → windows/deployment/update/wufb-reports-enable.md
View File

@ -20,7 +20,7 @@ ms.technology: itpro-updates
> - As of August 17, 2022, a new step needs to be taken to ensure access to the preview version of Update Compliance and the `CommercialID` is no longer required. For more information, see [Configure Update Compliance settings through the Microsoft 365 admin center](#bkmk_admin-center). > - As of August 17, 2022, a new step needs to be taken to ensure access to the preview version of Update Compliance and the `CommercialID` is no longer required. For more information, see [Configure Update Compliance settings through the Microsoft 365 admin center](#bkmk_admin-center).
> - This information relates to a preview feature that's available for early testing and use in a production environment. This feature is fully supported but it's still in active development and may receive substantial changes until it becomes generally available. > - This information relates to a preview feature that's available for early testing and use in a production environment. This feature is fully supported but it's still in active development and may receive substantial changes until it becomes generally available.
After verifying the [prerequisites](update-compliance-v2-prerequisites.md) are met, you can start to set up Update Compliance. The two main steps for setting up the Update Compliance solution are: After verifying the [prerequisites](wufb-reports-prerequisites.md) are met, you can start to set up Update Compliance. The two main steps for setting up the Update Compliance solution are:
1. [Add Update Compliance](#bkmk_add) to your Azure subscription. This step has the following two phases: 1. [Add Update Compliance](#bkmk_add) to your Azure subscription. This step has the following two phases:
1. [Select or create a new Log Analytics workspace](#bkmk_workspace) for use with Update Compliance. 1. [Select or create a new Log Analytics workspace](#bkmk_workspace) for use with Update Compliance.
@ -28,9 +28,9 @@ After verifying the [prerequisites](update-compliance-v2-prerequisites.md) are m
1. [Configure Update Compliance](#bkmk_admin-center) from the Microsoft 365 admin center. 1. [Configure Update Compliance](#bkmk_admin-center) from the Microsoft 365 admin center.
1. Configure the clients to send data to Update compliance. You can configure clients in the following three ways: 1. Configure the clients to send data to Update compliance. You can configure clients in the following three ways:
- Use a [script](update-compliance-v2-configuration-script.md) - Use a [script](wufb-reports-configuration-script.md)
- Use [Microsoft Endpoint Manager](update-compliance-v2-configuration-mem.md) - Use [Microsoft Endpoint Manager](wufb-reports-configuration-intune.md)
- Configure [manually](update-compliance-v2-configuration-manual.md) - Configure [manually](wufb-reports-configuration-manual.md)
> [!IMPORTANT] > [!IMPORTANT]
> Update Compliance is a Windows service hosted in Azure that uses Windows diagnostic data. You should be aware that Update Compliance doesn't meet [US Government community compliance (GCC)](/office365/servicedescriptions/office-365-platform-service-description/office-365-us-government/gcc#us-government-community-compliance) requirements. For a list of GCC offerings for Microsoft products and services, see the [Microsoft Trust Center](/compliance/regulatory/offering-home). Update Compliance is available in the Azure Commercial cloud, but not available for GCC High or United States Department of Defense customers. > Update Compliance is a Windows service hosted in Azure that uses Windows diagnostic data. You should be aware that Update Compliance doesn't meet [US Government community compliance (GCC)](/office365/servicedescriptions/office-365-platform-service-description/office-365-us-government/gcc#us-government-community-compliance) requirements. For a list of GCC offerings for Microsoft products and services, see the [Microsoft Trust Center](/compliance/regulatory/offering-home). Update Compliance is available in the Azure Commercial cloud, but not available for GCC High or United States Department of Defense customers.
@ -46,9 +46,9 @@ Update Compliance uses an [Azure Log Analytics workspaces](/azure/azure-monitor/
- Although an Azure subscription is required, you won't be charged for ingestion of Update Compliance data. - Although an Azure subscription is required, you won't be charged for ingestion of Update Compliance data.
1. In the Azure portal, type **Log Analytics** in the search bar. As you begin typing, the list filters based on your input. 1. In the Azure portal, type **Log Analytics** in the search bar. As you begin typing, the list filters based on your input.
1. Select **Log Analytics workspaces**. 1. Select **Log Analytics workspaces**.
1. If you already have a Log Analytics workspace, determine which Log Analytics workspace you'd like to use for Update Compliance. Ensure the workspace is in a **Compatible Log Analytics region** from the table listed in the [prerequisites](update-compliance-v2-prerequisites.md#log-analytics-regions). 1. If you already have a Log Analytics workspace, determine which Log Analytics workspace you'd like to use for Update Compliance. Ensure the workspace is in a **Compatible Log Analytics region** from the table listed in the [prerequisites](wufb-reports-prerequisites.md#log-analytics-regions).
- [Azure Update Management](/azure/automation/automation-intro#update-management) users should use the same workspace for Update Compliance. - [Azure Update Management](/azure/automation/automation-intro#update-management) users should use the same workspace for Update Compliance.
1. If you don't have an existing Log Analytics workspace or you don't want to use a current workspace, [create a new workspace](/azure/azure-monitor/logs/quick-create-workspace) in a [compatible region](update-compliance-v2-prerequisites.md#log-analytics-regions). 1. If you don't have an existing Log Analytics workspace or you don't want to use a current workspace, [create a new workspace](/azure/azure-monitor/logs/quick-create-workspace) in a [compatible region](wufb-reports-prerequisites.md#log-analytics-regions).
@ -76,13 +76,13 @@ Update Compliance is offered as an Azure Marketplace application that's linked t
Finish enabling Updates Compliance by configuring its settings through the Microsoft 365 admin center. Completing the Update Compliance configuration through the admin center removes needing to specify [`CommercialID`](update-compliance-get-started.md#get-your-commercialid), which was needed by the earlier version of Updates Compliance. This step is needed even if you enabled earlier previews of Update Compliance. Finish enabling Updates Compliance by configuring its settings through the Microsoft 365 admin center. Completing the Update Compliance configuration through the admin center removes needing to specify [`CommercialID`](update-compliance-get-started.md#get-your-commercialid), which was needed by the earlier version of Updates Compliance. This step is needed even if you enabled earlier previews of Update Compliance.
<!--Using include for onboarding Update Compliance through the Microsoft 365 admin center--> <!--Using include for onboarding Update Compliance through the Microsoft 365 admin center-->
[!INCLUDE [Onboarding Update Compliance through the Microsoft 365 admin center](./includes/update-compliance-onboard-admin-center.md)] [!INCLUDE [Onboarding Update Compliance through the Microsoft 365 admin center](./includes/wufb-reports-onboard-admin-center.md)]
## Next steps ## Next steps
Once you've added Update Compliance to a workspace in your Azure subscription and configured the settings through the Microsoft 365 admin center, you'll need to configure any devices you want to monitor. Enroll devices into Update Compliance using any of the following methods: Once you've added Update Compliance to a workspace in your Azure subscription and configured the settings through the Microsoft 365 admin center, you'll need to configure any devices you want to monitor. Enroll devices into Update Compliance using any of the following methods:
- [Configure clients with a script](update-compliance-v2-configuration-script.md) - [Configure clients with a script](wufb-reports-configuration-script.md)
- [Configure clients manually](update-compliance-v2-configuration-manual.md) - [Configure clients manually](wufb-reports-configuration-manual.md)
- [Configure clients with Microsoft Endpoint Manager](update-compliance-v2-configuration-mem.md) - [Configure clients with Microsoft Endpoint Manager](wufb-reports-configuration-intune.md)

10
windows/deployment/update/update-compliance-v2-help.md → windows/deployment/update/wufb-reports-help.md
View File

@ -18,7 +18,7 @@ ms.technology: itpro-updates
***(Applies to: Windows 11 & Windows 10)*** ***(Applies to: Windows 11 & Windows 10)***
> [!IMPORTANT] > [!IMPORTANT]
> - As of August 17, 2022, a new step needs to be taken to ensure access to the preview version of Update Compliance and the `CommercialID` is no longer required. For more information, see [Configure Update Compliance settings through the Microsoft 365 admin center](update-compliance-v2-enable.md#bkmk_admin-center). > - As of August 17, 2022, a new step needs to be taken to ensure access to the preview version of Update Compliance and the `CommercialID` is no longer required. For more information, see [Configure Update Compliance settings through the Microsoft 365 admin center](wufb-reports-enable.md#bkmk_admin-center).
> - This information relates to a preview feature that's available for early testing and use in a production environment. This feature is fully supported but it's still in active development and may receive substantial changes until it becomes generally available. > - This information relates to a preview feature that's available for early testing and use in a production environment. This feature is fully supported but it's still in active development and may receive substantial changes until it becomes generally available.
There are several resources that you can use to find help with Update Compliance. Whether you're just getting started or an experienced administrator, use the following resources when you need help with Update Compliance: There are several resources that you can use to find help with Update Compliance. Whether you're just getting started or an experienced administrator, use the following resources when you need help with Update Compliance:
@ -96,16 +96,16 @@ Use the troubleshooting tips below to resolve commonly encountered problems when
### Verify client configuration ### Verify client configuration
<!--Using include for verifying device configuration--> <!--Using include for verifying device configuration-->
[!INCLUDE [Endpoints for Update Compliance](./includes/update-compliance-verify-device-configuration.md)] [!INCLUDE [Endpoints for Update Compliance](./includes/wufb-reports-verify-device-configuration.md)]
### Ensuring devices are configured correctly to send data ### Ensuring devices are configured correctly to send data
The first step in troubleshooting Update Compliance is ensuring that devices are configured. Review [Manually configuring devices for Update Compliance](update-compliance-v2-configuration-manual.md) for the settings. We recommend using the [Update Compliance configuration script](update-compliance-v2-configuration-script.md) for troubleshooting and configuring devices. The first step in troubleshooting Update Compliance is ensuring that devices are configured. Review [Manually configuring devices for Update Compliance](wufb-reports-configuration-manual.md) for the settings. We recommend using the [Update Compliance configuration script](wufb-reports-configuration-script.md) for troubleshooting and configuring devices.
### Devices have been correctly configured but aren't showing up in Update Compliance ### Devices have been correctly configured but aren't showing up in Update Compliance
It takes some time for data to appear in Update Compliance for the first time or if you moved to a new Log Analytics workspace. To learn more about data latencies for Update Compliance, review [Update Compliance data latency](update-compliance-v2-use.md#update-compliance-data-latency). It takes some time for data to appear in Update Compliance for the first time or if you moved to a new Log Analytics workspace. To learn more about data latencies for Update Compliance, review [Update Compliance data latency](wufb-reports-use.md#update-compliance-data-latency).
### Devices are appearing, but without a device name ### 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 Update Compliance](update-compliance-v2-configuration-manual.md) article. 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 Update Compliance](wufb-reports-configuration-manual.md) article.

10
windows/deployment/update/update-compliance-v2-overview.md → windows/deployment/update/wufb-reports-overview.md
View File

@ -17,7 +17,7 @@ ms.technology: itpro-updates
***(Applies to: Windows 11 & Windows 10)*** ***(Applies to: Windows 11 & Windows 10)***
> [!Important] > [!Important]
> - As of August 17, 2022, a new step needs to be taken to ensure access to the preview version of Update Compliance and the `CommercialID` is no longer required. For more information, see [Configure Update Compliance settings through the Microsoft 365 admin center](update-compliance-v2-enable.md#bkmk_admin-center). > - As of August 17, 2022, a new step needs to be taken to ensure access to the preview version of Update Compliance and the `CommercialID` is no longer required. For more information, see [Configure Update Compliance settings through the Microsoft 365 admin center](wufb-reports-enable.md#bkmk_admin-center).
> - This information relates to a preview feature that's available for early testing and use in a production environment. This feature is fully supported but it's still in active development and may receive substantial changes until it becomes generally available. > - This information relates to a preview feature that's available for early testing and use in a production environment. This feature is fully supported but it's still in active development and may receive substantial changes until it becomes generally available.
Update Compliance is a cloud-based solution that provides information about the compliance of your Azure Active Directory-joined devices with Windows updates. Update Compliance 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. Update Compliance helps you: Update Compliance is a cloud-based solution that provides information about the compliance of your Azure Active Directory-joined devices with Windows updates. Update Compliance 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. Update Compliance helps you:
@ -37,9 +37,9 @@ The new version of Update Compliance is in preview. Some of the benefits of this
Currently, the preview contains the following features: Currently, the preview contains the following features:
- [Update Compliance workbook](update-compliance-v2-workbook.md) - [Update Compliance workbook](wufb-reports-workbook.md)
- Update Compliance status [charts in the Microsoft 365 admin](update-status-admin-center.md) - Update Compliance status [charts in the Microsoft 365 admin](update-status-admin-center.md)
- Access to the following new [Update Compliance tables](update-compliance-v2-schema.md): - Access to the following new [Update Compliance tables](wufb-reports-schema.md):
- UCClient - UCClient
- UCClientReadinessStatus - UCClientReadinessStatus
- UCClientUpdateStatus - UCClientUpdateStatus
@ -50,7 +50,7 @@ Currently, the preview contains the following features:
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 will be displayed along with the original Updates Compliance tables.
:::image type="content" source="media/update-compliance-v2-query-table.png" alt-text="Screenshot of using a custom Kusto (KQL) query on Update Compliance data in Log Analytics." lightbox="media/update-compliance-v2-query-table.png"::: :::image type="content" source="media/wufb-reports-query-table.png" alt-text="Screenshot of using a custom Kusto (KQL) query on Update Compliance data in Log Analytics." lightbox="media/wufb-reports-query-table.png":::
## Limitations ## Limitations
@ -82,4 +82,4 @@ Since the data from your clients is stored in a Log Analytics workspace, you can
## Next steps ## Next steps
- Review the [Update Compliance prerequisites](update-compliance-v2-prerequisites.md) - Review the [Update Compliance prerequisites](wufb-reports-prerequisites.md)

8
windows/deployment/update/update-compliance-v2-prerequisites.md → windows/deployment/update/wufb-reports-prerequisites.md
View File

@ -17,7 +17,7 @@ ms.technology: itpro-updates
***(Applies to: Windows 11 & Windows 10)*** ***(Applies to: Windows 11 & Windows 10)***
> [!Important] > [!Important]
> - As of August 17, 2022, a new step needs to be taken to ensure access to the preview version of Update Compliance and the CommercialID is no longer required. For more information, see [Configure Update Compliance settings through the Microsoft 365 admin center](update-compliance-v2-enable.md#bkmk_admin-center). > - As of August 17, 2022, a new step needs to be taken to ensure access to the preview version of Update Compliance and the CommercialID is no longer required. For more information, see [Configure Update Compliance settings through the Microsoft 365 admin center](wufb-reports-enable.md#bkmk_admin-center).
> - This information relates to a preview feature that's available for early testing and use in a production environment. This feature is fully supported but it's still in active development and may receive substantial changes until it becomes generally available. > - This information relates to a preview feature that's available for early testing and use in a production environment. This feature is fully supported but it's still in active development and may receive substantial changes until it becomes generally available.
## Update Compliance prerequisites ## Update Compliance prerequisites
@ -62,14 +62,14 @@ For more information about what's included in different diagnostic levels, see [
### Data transmission requirements ### Data transmission requirements
<!--Using include for endpoint access requirements--> <!--Using include for endpoint access requirements-->
[!INCLUDE [Endpoints for Update Compliance](./includes/update-compliance-endpoints.md)] [!INCLUDE [Endpoints for Update Compliance](./includes/wufb-reports-endpoints.md)]
> [!NOTE] > [!NOTE]
> Enrolling into Update Compliance from the [Azure CLI](/cli/azure) or enrolling programmatically another way currently isn't supported. You must manually add Update Compliance to your Azure subscription. > Enrolling into Update Compliance from the [Azure CLI](/cli/azure) or enrolling programmatically another way currently isn't supported. You must manually add Update Compliance to your Azure subscription.
## Microsoft 365 admin center permissions ## Microsoft 365 admin center permissions
<!--Using include Microsoft 365 admin center permissions--> <!--Using include Microsoft 365 admin center permissions-->
[!INCLUDE [Update Compliance script error codes](./includes/update-compliance-admin-center-permissions.md)] [!INCLUDE [Update Compliance script error codes](./includes/wufb-reports-admin-center-permissions.md)]
## Log Analytics prerequisites ## Log Analytics prerequisites
@ -115,4 +115,4 @@ Update Compliance can use a Log Analytics workspace in the following regions:
## Next steps ## Next steps
- [Enable the Update Compliance solution](update-compliance-v2-enable.md) in the Azure portal - [Enable the Update Compliance solution](wufb-reports-enable.md) in the Azure portal

0
windows/deployment/update/update-compliance-v2-schema-ucclient.md → windows/deployment/update/wufb-reports-schema-ucclient.md
View File

0
windows/deployment/update/update-compliance-v2-schema-ucclientreadinessstatus.md → windows/deployment/update/wufb-reports-schema-ucclientreadinessstatus.md
View File

0
windows/deployment/update/update-compliance-v2-schema-ucclientupdatestatus.md → windows/deployment/update/wufb-reports-schema-ucclientupdatestatus.md
View File

0
windows/deployment/update/update-compliance-v2-schema-ucdevicealert.md → windows/deployment/update/wufb-reports-schema-ucdevicealert.md
View File

0
windows/deployment/update/update-compliance-v2-schema-ucserviceupdatestatus.md → windows/deployment/update/wufb-reports-schema-ucserviceupdatestatus.md
View File

0
windows/deployment/update/update-compliance-v2-schema-ucupdatealert.md → windows/deployment/update/wufb-reports-schema-ucupdatealert.md
View File

14
windows/deployment/update/update-compliance-v2-schema.md → windows/deployment/update/wufb-reports-schema.md
View File

@ -17,7 +17,7 @@ ms.technology: itpro-updates
***(Applies to: Windows 11 & Windows 10)*** ***(Applies to: Windows 11 & Windows 10)***
> [!Important] > [!Important]
> - As of August 17, 2022, a new step needs to be taken to ensure access to the preview version of Update Compliance and the `CommercialID` is no longer required. For more information, see [Configure Update Compliance settings through the Microsoft 365 admin center](update-compliance-v2-enable.md#bkmk_admin-center). > - As of August 17, 2022, a new step needs to be taken to ensure access to the preview version of Update Compliance and the `CommercialID` is no longer required. For more information, see [Configure Update Compliance settings through the Microsoft 365 admin center](wufb-reports-enable.md#bkmk_admin-center).
> - This information relates to a preview feature that's available for early testing and use in a production environment. This feature is fully supported but it's still in active development and may receive substantial changes until it becomes generally available. > - This information relates to a preview feature that's available for early testing and use in a production environment. This feature is fully supported but it's still in active development and may receive substantial changes until it becomes generally available.
When the visualizations provided in the default experience don't fulfill your reporting needs, or if you need to troubleshoot issues with devices, it's valuable to understand the schema for Update Compliance and have a high-level understanding of the capabilities of [Azure Monitor log queries](/azure/azure-monitor/log-query/query-language) to power additional dashboards, integration with external data analysis tools, automated alerting, and more. When the visualizations provided in the default experience don't fulfill your reporting needs, or if you need to troubleshoot issues with devices, it's valuable to understand the schema for Update Compliance and have a high-level understanding of the capabilities of [Azure Monitor log queries](/azure/azure-monitor/log-query/query-language) to power additional dashboards, integration with external data analysis tools, automated alerting, and more.
@ -31,9 +31,9 @@ The table below summarizes the different tables that are part of the Update Comp
|Table |Category |Description | |Table |Category |Description |
|--|--|--| |--|--|--|
| [**UCClient**](update-compliance-v2-schema-ucclient.md) | Device record | UCClient acts as an individual device's record. It contains data such as the currently installed build, the device's name, the operating system edition, and active hours (quantitative). | | [**UCClient**](wufb-reports-schema-ucclient.md) | Device record | UCClient acts as an individual device's record. It contains data such as the currently installed build, the device's name, the operating system edition, and active hours (quantitative). |
|[**UCClientReadinessStatus**](update-compliance-v2-schema-ucclientreadinessstatus.md) | Device record | UCClientReadinessStatus is an individual device's record about its readiness for updating to Windows 11. If the device isn't capable of running Windows 11, the record includes which Windows 11 hardware requirements the device doesn't meet.| |[**UCClientReadinessStatus**](wufb-reports-schema-ucclientreadinessstatus.md) | Device record | UCClientReadinessStatus is an individual device's record about its readiness for updating to Windows 11. If the device isn't capable of running Windows 11, the record includes which Windows 11 hardware requirements the device doesn't meet.|
| [**UCClientUpdateStatus**](update-compliance-v2-schema-ucclientupdatestatus.md) | Device record | Update Event that combines the latest client-based data with the latest service-based data to create a complete picture for one device (client) and one update. | | [**UCClientUpdateStatus**](wufb-reports-schema-ucclientupdatestatus.md) | Device record | Update Event that combines the latest client-based data with the latest service-based data to create a complete picture for one device (client) and one update. |
| [**UCDeviceAlert**](update-compliance-v2-schema-ucdevicealert.md)| Service and device record | These alerts are activated as a result of an issue that is device-specific. It isn't specific to the combination of a specific update and a specific device. Like UpdateAlerts, the AlertType indicates where the Alert comes from such as a ServiceDeviceAlert or ClientDeviceAlert. | | [**UCDeviceAlert**](wufb-reports-schema-ucdevicealert.md)| Service and device record | These alerts are activated as a result of an issue that is device-specific. It isn't specific to the combination of a specific update and a specific device. Like UpdateAlerts, the AlertType indicates where the Alert comes from such as a ServiceDeviceAlert or ClientDeviceAlert. |
| [**UCServiceUpdateStatus**](update-compliance-v2-schema-ucserviceupdatestatus.md) | Service record | 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. | | [**UCServiceUpdateStatus**](wufb-reports-schema-ucserviceupdatestatus.md) | Service record | 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. |
| [**UCUpdateAlert**](update-compliance-v2-schema-ucupdatealert.md) | Service and device records | Alert for both client and service update. Contains information that needs attention, relative to one device (client), one update, and one deployment, if relevant. Certain fields may be blank depending on the UpdateAlert's AlertType field. For example, ServiceUpdateAlert won't necessarily contain client-side statuses and may be blank. | | [**UCUpdateAlert**](wufb-reports-schema-ucupdatealert.md) | Service and device records | Alert for both client and service update. Contains information that needs attention, relative to one device (client), one update, and one deployment, if relevant. Certain fields may be blank depending on the UpdateAlert's AlertType field. For example, ServiceUpdateAlert won't necessarily contain client-side statuses and may be blank. |

6
windows/deployment/update/update-compliance-v2-use.md → windows/deployment/update/wufb-reports-use.md
View File

@ -19,7 +19,7 @@ ms.technology: itpro-updates
> [!Important] > [!Important]
> This information relates to a preview feature that's available for early testing and use in a production environment. This feature is fully supported but it's still in active development and may receive substantial changes until it becomes generally available. > This information relates to a preview feature that's available for early testing and use in a production environment. This feature is fully supported but it's still in active development and may receive substantial changes until it becomes generally available.
In this article, you'll learn how to use Update Compliance to monitor Windows updates for your devices. To configure your environment for use with Update Compliance, see [Enable Update Compliance](update-compliance-v2-enable.md). In this article, you'll learn how to use Update Compliance to monitor Windows updates for your devices. To configure your environment for use with Update Compliance, see [Enable Update Compliance](wufb-reports-enable.md).
## Display Update Compliance data ## Display Update Compliance data
@ -30,14 +30,14 @@ In this article, you'll learn how to use Update Compliance to monitor Windows up
1. Select **Logs** under the **General** group in your workspace. 1. Select **Logs** under the **General** group in your workspace.
1. If the **Always show Queries** option is enabled in Log Analytics, close the query window to access the schema. 1. If the **Always show Queries** option is enabled in Log Analytics, close the query window to access the schema.
1. Under **Schemas and filter**, select **Group by: Solution** and then expand the **Update Compliance** schema. If the **Group by: Category** is selected, the **Update Compliance** schema is listed under the **Other** category. 1. Under **Schemas and filter**, select **Group by: Solution** and then expand the **Update Compliance** schema. If the **Group by: Category** is selected, the **Update Compliance** schema is listed under the **Other** category.
1. Use the [Update Compliance schema](update-compliance-v2-schema.md) for [custom Kusto (KQL) queries](/azure/data-explorer/kusto/query/), to build [custom workbooks](/azure/azure-monitor/visualize/workbooks-overview), or to build your own solution to display the Update Compliance data. For example, you might query the data to review information for different types of alerts in the past 7 days and how many times each alert occurred. 1. Use the [Update Compliance schema](wufb-reports-schema.md) for [custom Kusto (KQL) queries](/azure/data-explorer/kusto/query/), to build [custom workbooks](/azure/azure-monitor/visualize/workbooks-overview), or to build your own solution to display the Update Compliance data. For example, you might query the data to review information for different types of alerts in the past 7 days and how many times each alert occurred.
```kusto ```kusto
UCUpdateAlert UCUpdateAlert
| summarize count=count() by AlertClassification, AlertSubtype, ErrorCode, Description | summarize count=count() by AlertClassification, AlertSubtype, ErrorCode, Description
``` ```
:::image type="content" source="media/update-compliance-v2-query-table.png" alt-text="Screenshot of using a custom Kusto (KQL) query on Update Compliance data in Log Analytics." lightbox="media/update-compliance-v2-query-table.png"::: :::image type="content" source="media/wufb-reports-query-table.png" alt-text="Screenshot of using a custom Kusto (KQL) query on Update Compliance data in Log Analytics." lightbox="media/wufb-reports-query-table.png":::
## Update Compliance data latency ## Update Compliance data latency

10
windows/deployment/update/update-compliance-v2-workbook.md → windows/deployment/update/wufb-reports-workbook.md
View File

@ -17,10 +17,10 @@ ms.technology: itpro-updates
***(Applies to: Windows 11 & Windows 10)*** ***(Applies to: Windows 11 & Windows 10)***
> [!IMPORTANT] > [!IMPORTANT]
> - As of August 17, 2022, a new step needs to be taken to ensure access to the preview version of Update Compliance and the `CommercialID` is no longer required. For more information, see [Configure Update Compliance settings through the Microsoft 365 admin center](update-compliance-v2-enable.md#bkmk_admin-center). > - As of August 17, 2022, a new step needs to be taken to ensure access to the preview version of Update Compliance and the `CommercialID` is no longer required. For more information, see [Configure Update Compliance settings through the Microsoft 365 admin center](wufb-reports-enable.md#bkmk_admin-center).
> - This information relates to a preview feature that's available for early testing and use in a production environment. This feature is fully supported but it's still in active development and may receive substantial changes until it becomes generally available. > - This information relates to a preview feature that's available for early testing and use in a production environment. This feature is fully supported but it's still in active development and may receive substantial changes until it becomes generally available.
[Update Compliance](update-compliance-v2-overview.md) presents information commonly needed by updates administrators in an easy to use format. Update Compliance 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 three tab sections: [Update Compliance](wufb-reports-overview.md) presents information commonly needed by updates administrators in an easy to use format. Update Compliance 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 three tab sections:
- [Summary](#summary-tab) - [Summary](#summary-tab)
- [Quality updates](#quality-updates-tab) - [Quality updates](#quality-updates-tab)
@ -36,7 +36,7 @@ To access the Update Compliance workbook:
- You can also type **Monitor** in the search bar. As you begin typing, the list filters based on your input. - You can also type **Monitor** in the search bar. As you begin typing, the list filters based on your input.
1. When the gallery opens, select the **Update Compliance** workbook. If needed, you can filter workbooks by name in the gallery. 1. When the gallery opens, select the **Update Compliance** workbook. If needed, you can filter workbooks by name in the gallery.
1. When the workbook opens, you may need to specify which **Subscription** and **Workspace** you used when [enabling Update Compliance](update-compliance-v2-enable.md). 1. When the workbook opens, you may need to specify which **Subscription** and **Workspace** you used when [enabling Update Compliance](wufb-reports-enable.md).
## Summary tab ## Summary tab
@ -148,5 +148,5 @@ Since the Update Compliance workbook is an [Azure Workbook template](/azure/azur
## Next steps ## Next steps
- Explore the [Update Compliance (preview) schema](update-compliance-v2-schema.md) - Explore the [Update Compliance (preview) schema](wufb-reports-schema.md)
- Review [Feedback, support, and troubleshooting](update-compliance-v2-help.md) information for Update Compliance - Review [Feedback, support, and troubleshooting](wufb-reports-help.md) information for Update Compliance