mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-21 17:57:22 +00:00
Merge branch 'main' of https://github.com/MicrosoftDocs/windows-docs-pr into fr-deploy-meta-usmt
This commit is contained in:
Frank Rojas
commit
67296bca16
@ -20069,6 +20069,91 @@
|
||||
"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_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-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",
|
||||
"redirect_document_id": false
|
||||
}
|
||||
]
|
||||
}
|
||||
@ -182,131 +182,131 @@
|
||||
href: update/waas-wufb-group-policy.md
|
||||
- name: 'Walkthrough: use Intune to configure Windows Update for Business'
|
||||
href: update/deploy-updates-intune.md
|
||||
- name: Monitor Windows client updates
|
||||
- name: Monitor
|
||||
items:
|
||||
- name: Windows Update for Business reports (preview)
|
||||
items:
|
||||
- name: Windows Update for Business reports overview
|
||||
href: update/wufb-reports-overview.md
|
||||
- name: Enable Windows Update for Business reports (preview)
|
||||
items:
|
||||
- name: Windows Update for Business reports prerequisites
|
||||
href: update/wufb-reports-prerequisites.md
|
||||
- name: Enable Windows Update for Business reports
|
||||
href: update/wufb-reports-enable.md
|
||||
- name: Configure clients with a script
|
||||
href: update/wufb-reports-configuration-script.md
|
||||
- name: Configure clients manually
|
||||
href: update/wufb-reports-configuration-manual.md
|
||||
- name: Configure clients with Microsoft Intune
|
||||
href: update/wufb-reports-configuration-intune.md
|
||||
- name: Use Windows Update for Business reports (preview)
|
||||
items:
|
||||
- name: Monitor with Update Compliance (preview version)
|
||||
items:
|
||||
- name: Update Compliance overview
|
||||
href: update/update-compliance-v2-overview.md
|
||||
- name: Enable Update Compliance (preview)
|
||||
items:
|
||||
- name: Update Compliance prerequisites
|
||||
href: update/update-compliance-v2-prerequisites.md
|
||||
- name: Enable the Update Compliance solution
|
||||
href: update/update-compliance-v2-enable.md
|
||||
- name: Configure clients with a script
|
||||
href: update/update-compliance-v2-configuration-script.md
|
||||
- name: Configure clients manually
|
||||
href: update/update-compliance-v2-configuration-manual.md
|
||||
- name: Configure clients with Microsoft Intune
|
||||
href: update/update-compliance-v2-configuration-mem.md
|
||||
- name: Use Update Compliance (preview)
|
||||
items:
|
||||
- name: Update Compliance workbook
|
||||
href: update/update-compliance-v2-workbook.md
|
||||
- name: Software updates in the Microsoft admin center (preview)
|
||||
href: update/update-status-admin-center.md
|
||||
- name: Use Update Compliance data
|
||||
href: update/update-compliance-v2-use.md
|
||||
- name: Feedback, support, and troubleshooting
|
||||
href: update/update-compliance-v2-help.md
|
||||
- name: Update Compliance schema reference (preview)
|
||||
items:
|
||||
- name: Update Compliance schema reference
|
||||
href: update/update-compliance-v2-schema.md
|
||||
- name: UCClient
|
||||
href: update/update-compliance-v2-schema-ucclient.md
|
||||
- name: UCClientReadinessStatus
|
||||
href: update/update-compliance-v2-schema-ucclientreadinessstatus.md
|
||||
- name: UCClientUpdateStatus
|
||||
href: update/update-compliance-v2-schema-ucclientupdatestatus.md
|
||||
- name: UCDeviceAlert
|
||||
href: update/update-compliance-v2-schema-ucdevicealert.md
|
||||
- name: UCServiceUpdateStatus
|
||||
href: update/update-compliance-v2-schema-ucserviceupdatestatus.md
|
||||
- name: UCUpdateAlert
|
||||
href: update/update-compliance-v2-schema-ucupdatealert.md
|
||||
- name: Monitor updates with Update Compliance
|
||||
href: update/update-compliance-monitor.md
|
||||
items:
|
||||
- name: Get started
|
||||
items:
|
||||
- name: Get started with Update Compliance
|
||||
href: update/update-compliance-get-started.md
|
||||
- name: Update Compliance configuration script
|
||||
href: update/update-compliance-configuration-script.md
|
||||
- name: Manually configuring devices for Update Compliance
|
||||
href: update/update-compliance-configuration-manual.md
|
||||
- name: Configuring devices for Update Compliance in Microsoft Intune
|
||||
href: update/update-compliance-configuration-mem.md
|
||||
- name: Update Compliance monitoring
|
||||
items:
|
||||
- name: Use Update Compliance
|
||||
href: update/update-compliance-using.md
|
||||
- name: Need attention report
|
||||
href: update/update-compliance-need-attention.md
|
||||
- name: Security update status report
|
||||
href: update/update-compliance-security-update-status.md
|
||||
- name: Feature update status report
|
||||
href: update/update-compliance-feature-update-status.md
|
||||
- name: Safeguard holds report
|
||||
href: update/update-compliance-safeguard-holds.md
|
||||
- name: Delivery Optimization in Update Compliance
|
||||
href: update/update-compliance-delivery-optimization.md
|
||||
- name: Data handling and privacy in Update Compliance
|
||||
href: update/update-compliance-privacy.md
|
||||
- name: Schema reference
|
||||
items:
|
||||
- name: Update Compliance schema reference
|
||||
href: update/update-compliance-schema.md
|
||||
- name: WaaSUpdateStatus
|
||||
href: update/update-compliance-schema-waasupdatestatus.md
|
||||
- name: WaaSInsiderStatus
|
||||
href: update/update-compliance-schema-waasinsiderstatus.md
|
||||
- name: WaaSDeploymentStatus
|
||||
href: update/update-compliance-schema-waasdeploymentstatus.md
|
||||
- name: WUDOStatus
|
||||
href: update/update-compliance-schema-wudostatus.md
|
||||
- name: WUDOAggregatedStatus
|
||||
href: update/update-compliance-schema-wudoaggregatedstatus.md
|
||||
- name: Troubleshooting
|
||||
- name: Windows Update for Business reports workbook
|
||||
href: update/wufb-reports-workbook.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
|
||||
href: update/wufb-reports-help.md
|
||||
- name: Windows Update for Business reports (preview) schema reference
|
||||
items:
|
||||
- name: Resolve upgrade errors
|
||||
items:
|
||||
- name: Resolve Windows client upgrade errors
|
||||
href: upgrade/resolve-windows-10-upgrade-errors.md
|
||||
- name: Quick fixes
|
||||
href: /troubleshoot/windows-client/deployment/windows-10-upgrade-quick-fixes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
- name: SetupDiag
|
||||
href: upgrade/setupdiag.md
|
||||
- name: Troubleshooting upgrade errors
|
||||
href: /troubleshoot/windows-client/deployment/windows-10-upgrade-issues-troubleshooting?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
- name: Windows error reporting
|
||||
href: upgrade/windows-error-reporting.md
|
||||
- name: Upgrade error codes
|
||||
href: /troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
- name: Log files
|
||||
href: upgrade/log-files.md
|
||||
- name: Resolution procedures
|
||||
href: /troubleshoot/windows-client/deployment/windows-10-upgrade-resolution-procedures?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
- name: Submit Windows client upgrade errors
|
||||
href: upgrade/submit-errors.md
|
||||
- name: Troubleshoot Windows Update
|
||||
items:
|
||||
- name: How to troubleshoot Windows Update
|
||||
href: /troubleshoot/windows-client/deployment/windows-update-issues-troubleshooting?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
- name: Opt out of safeguard holds
|
||||
href: update/safeguard-opt-out.md
|
||||
- name: Determine the source of Windows Updates
|
||||
href: ./update/how-windows-update-works.md
|
||||
- name: Windows Update security
|
||||
href: ./update/windows-update-security.md
|
||||
- name: Common Windows Update errors
|
||||
href: /troubleshoot/windows-client/deployment/common-windows-update-errors?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
- name: Windows Update error code reference
|
||||
href: update/windows-update-error-reference.md
|
||||
- name: Troubleshoot the Windows Update for Business deployment service
|
||||
href: update/deployment-service-troubleshoot.md
|
||||
- name: Windows Update for Business reports schema reference
|
||||
href: update/wufb-reports-schema.md
|
||||
- name: UCClient
|
||||
href: update/wufb-reports-schema-ucclient.md
|
||||
- name: UCClientReadinessStatus
|
||||
href: update/wufb-reports-schema-ucclientreadinessstatus.md
|
||||
- name: UCClientUpdateStatus
|
||||
href: update/wufb-reports-schema-ucclientupdatestatus.md
|
||||
- name: UCDeviceAlert
|
||||
href: update/wufb-reports-schema-ucdevicealert.md
|
||||
- name: UCServiceUpdateStatus
|
||||
href: update/wufb-reports-schema-ucserviceupdatestatus.md
|
||||
- name: UCUpdateAlert
|
||||
href: update/wufb-reports-schema-ucupdatealert.md
|
||||
- name: Monitor updates with Update Compliance
|
||||
href: update/update-compliance-monitor.md
|
||||
items:
|
||||
- name: Get started
|
||||
items:
|
||||
- name: Get started with Update Compliance
|
||||
href: update/update-compliance-get-started.md
|
||||
- name: Update Compliance configuration script
|
||||
href: update/update-compliance-configuration-script.md
|
||||
- name: Manually configuring devices for Update Compliance
|
||||
href: update/update-compliance-configuration-manual.md
|
||||
- name: Configuring devices for Update Compliance in Microsoft Intune
|
||||
href: update/update-compliance-configuration-mem.md
|
||||
- name: Update Compliance monitoring
|
||||
items:
|
||||
- name: Use Update Compliance
|
||||
href: update/update-compliance-using.md
|
||||
- name: Need attention report
|
||||
href: update/update-compliance-need-attention.md
|
||||
- name: Security update status report
|
||||
href: update/update-compliance-security-update-status.md
|
||||
- name: Feature update status report
|
||||
href: update/update-compliance-feature-update-status.md
|
||||
- name: Safeguard holds report
|
||||
href: update/update-compliance-safeguard-holds.md
|
||||
- name: Delivery Optimization in Update Compliance
|
||||
href: update/update-compliance-delivery-optimization.md
|
||||
- name: Data handling and privacy in Update Compliance
|
||||
href: update/update-compliance-privacy.md
|
||||
- name: Schema reference
|
||||
items:
|
||||
- name: Update Compliance schema reference
|
||||
href: update/update-compliance-schema.md
|
||||
- name: WaaSUpdateStatus
|
||||
href: update/update-compliance-schema-waasupdatestatus.md
|
||||
- name: WaaSInsiderStatus
|
||||
href: update/update-compliance-schema-waasinsiderstatus.md
|
||||
- name: WaaSDeploymentStatus
|
||||
href: update/update-compliance-schema-waasdeploymentstatus.md
|
||||
- name: WUDOStatus
|
||||
href: update/update-compliance-schema-wudostatus.md
|
||||
- name: WUDOAggregatedStatus
|
||||
href: update/update-compliance-schema-wudoaggregatedstatus.md
|
||||
- name: Troubleshooting
|
||||
items:
|
||||
- name: Resolve upgrade errors
|
||||
items:
|
||||
- name: Resolve Windows client upgrade errors
|
||||
href: upgrade/resolve-windows-10-upgrade-errors.md
|
||||
- name: Quick fixes
|
||||
href: /troubleshoot/windows-client/deployment/windows-10-upgrade-quick-fixes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
- name: SetupDiag
|
||||
href: upgrade/setupdiag.md
|
||||
- name: Troubleshooting upgrade errors
|
||||
href: /troubleshoot/windows-client/deployment/windows-10-upgrade-issues-troubleshooting?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
- name: Windows error reporting
|
||||
href: upgrade/windows-error-reporting.md
|
||||
- name: Upgrade error codes
|
||||
href: /troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
- name: Log files
|
||||
href: upgrade/log-files.md
|
||||
- name: Resolution procedures
|
||||
href: /troubleshoot/windows-client/deployment/windows-10-upgrade-resolution-procedures?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
- name: Submit Windows client upgrade errors
|
||||
href: upgrade/submit-errors.md
|
||||
- name: Troubleshoot Windows Update
|
||||
items:
|
||||
- name: How to troubleshoot Windows Update
|
||||
href: /troubleshoot/windows-client/deployment/windows-update-issues-troubleshooting?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
- name: Opt out of safeguard holds
|
||||
href: update/safeguard-opt-out.md
|
||||
- name: Determine the source of Windows Updates
|
||||
href: ./update/how-windows-update-works.md
|
||||
- name: Windows Update security
|
||||
href: ./update/windows-update-security.md
|
||||
- name: Common Windows Update errors
|
||||
href: /troubleshoot/windows-client/deployment/common-windows-update-errors?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
- name: Windows Update error code reference
|
||||
href: update/windows-update-error-reference.md
|
||||
- name: Troubleshoot the Windows Update for Business deployment service
|
||||
href: update/deployment-service-troubleshoot.md
|
||||
|
||||
- name: Reference
|
||||
items:
|
||||
|
||||
@ -1,22 +0,0 @@
|
||||
---
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: dougeby
|
||||
ms.prod: w10
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: include
|
||||
ms.date: 08/18/2022
|
||||
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. -->
|
||||
[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):
|
||||
|
||||
|
||||
- To enable Update Compliance, edit Update Compliance 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 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).
|
||||
@ -0,0 +1,21 @@
|
||||
---
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: dougeby
|
||||
ms.prod: w10
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: include
|
||||
ms.date: 08/18/2022
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
<!--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:
|
||||
|
||||
- [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)
|
||||
@ -8,13 +8,13 @@ ms.topic: include
|
||||
ms.date: 04/06/2022
|
||||
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:
|
||||
|
||||
| **Endpoint** | **Function** |
|
||||
|---------------------------------------------------------|-----------|
|
||||
| `https://v10c.events.data.microsoft.com` | Connected User Experience and Diagnostic component endpoint for Windows 10, version 1803 and later. DeviceCensus.exe must run on a regular cadence and contact this endpoint in order to receive most information for Update Compliance. |
|
||||
| `https://v10c.events.data.microsoft.com` | Connected User Experience and Diagnostic component endpoint for Windows 10, version 1803 and later. DeviceCensus.exe must run on a regular cadence and contact this endpoint in order to receive most information for Windows Update for Business reports. |
|
||||
| `https://v10.vortex-win.data.microsoft.com` | Connected User Experience and Diagnostic component endpoint for Windows 10, version 1709 or earlier. |
|
||||
| `https://settings-win.data.microsoft.com` | Required for Windows Update functionality. |
|
||||
| `https://adl.windows.com` | Required for Windows Update functionality. |
|
||||
@ -8,16 +8,16 @@ ms.topic: include
|
||||
ms.date: 08/18/2022
|
||||
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/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.
|
||||
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 [Windows Update for Business reports](../wufb-reports-overview.md). Verify or supply the following information about the settings for Windows Update for Business reports:
|
||||
|
||||
- The Azure subscription
|
||||
- The Log Analytics workspace
|
||||
1. The initial setup can take up to 24 hours. During this time, the **Windows** tab will display that it's **Waiting for Update Compliance data**.
|
||||
1. After the initial setup is complete, the **Windows** tab will display your Update Compliance data in the charts.
|
||||
1. The initial setup can take up to 24 hours. During this time, the **Windows** tab will display that it's **Waiting for Windows Update for Business reports data**.
|
||||
1. After the initial setup is complete, the **Windows** tab will display your Windows Update for Business reports data in the charts.
|
||||
|
||||
> [!Tip]
|
||||
> If you don't see an entry for **Software updates (preview)** in the menu, try going to this URL: [https://admin.microsoft.com/Adminportal/Home#/softwareupdates](https://admin.microsoft.com/Adminportal/Home#/softwareupdates).
|
||||
> If you don't see an entry for **Software updates** in the menu, try going to this URL: [https://admin.microsoft.com/Adminportal/Home#/softwareupdates](https://admin.microsoft.com/Adminportal/Home#/softwareupdates).
|
||||
14
windows/deployment/update/includes/wufb-reports-recommend.md
Normal file
14
windows/deployment/update/includes/wufb-reports-recommend.md
Normal file
@ -0,0 +1,14 @@
|
||||
---
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
ms.prod: w10
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: include
|
||||
ms.date: 11/04/2022
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
<!--This file is shared by all Update Compliance v1 articles. -->
|
||||
|
||||
> [!Important]
|
||||
> If you're using Update Compliance, it's highly recommended that you start transitioning to Windows Update for Business reports. For more information, see [Windows Update for Business reports overview](..\wufb-reports-overview.md).
|
||||
@ -8,7 +8,7 @@ ms.topic: include
|
||||
ms.date: 08/18/2022
|
||||
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 |
|
||||
|---------|---------|
|
||||
| 1 | General unexpected error|
|
||||
@ -58,5 +58,5 @@ ms.localizationpriority: medium
|
||||
| 97 | Failed to update value for EnableAllowCommercialDataPipeline |
|
||||
| 98 | Unexpected exception in EnableAllowCommercialDataPipeline |
|
||||
| 99 | Device isn't Windows 10.|
|
||||
| 100 | Device must be AADJ or hybrid AADJ to use Update Compliance |
|
||||
| 100 | Device must be AADJ or hybrid AADJ to use Windows Update for Business reports or Update Compliance |
|
||||
| 101 | Check AADJ failed with unexpected exception |
|
||||
@ -8,7 +8,7 @@ ms.topic: include
|
||||
ms.date: 08/10/2022
|
||||
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:
|
||||
|
||||
@ -35,9 +35,9 @@ In some cases, you may need to manually verify the device configuration has the
|
||||
1. Go to **Start**, select **Settings** > **Privacy** > **Diagnostics & feedback**.
|
||||
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:
|
||||
- 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 [Windows Update for Business reports](../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`.
|
||||
- If you need to send this data to Microsoft Support, select **Export data**.
|
||||
|
||||
:::image type="content" alt-text="Screenshot of the Diagnostic Data Viewer displaying the data from SoftwareUpdateClientTelemetry. The export data option and the fields for MSP and EnrolledTenantID are outlined in red." source="../media/update-compliance-diagnostic-data-viewer.png" lightbox="../media/update-compliance-diagnostic-data-viewer.png":::
|
||||
:::image type="content" alt-text="Screenshot of the Diagnostic Data Viewer displaying the data from SoftwareUpdateClientTelemetry. The export data option and the fields for MSP and EnrolledTenantID are outlined in red." source="../media/wufb-reports-diagnostic-data-viewer.png" lightbox="../media/wufb-reports-diagnostic-data-viewer.png":::
|
||||
|
||||
|
Before Width: | Height: | Size: 86 KiB After Width: | Height: | Size: 86 KiB |
|
Before Width: | Height: | Size: 372 KiB After Width: | Height: | Size: 372 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 322 KiB |
|
Before Width: | Height: | Size: 581 KiB After Width: | Height: | Size: 581 KiB |
BIN
windows/deployment/update/media/wufb-reports-query-table.png
Normal file
BIN
windows/deployment/update/media/wufb-reports-query-table.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 237 KiB |
@ -19,6 +19,10 @@ ms.technology: itpro-updates
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
|
||||
<!--Using include for recommending Windows Update for Business reports for all Update Compliance v1 docs-->
|
||||
[!INCLUDE [Recommend Windows Update for Business reports](./includes/wufb-reports-recommend.md)]
|
||||
|
||||
|
||||
There are a number of requirements to consider when manually configuring devices for Update Compliance. These can potentially change with newer versions of Windows client. The [Update Compliance Configuration Script](update-compliance-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:
|
||||
@ -68,7 +72,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.
|
||||
|
||||
<!--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
|
||||
|
||||
|
||||
@ -19,6 +19,9 @@ ms.technology: itpro-updates
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
|
||||
<!--Using include for recommending Windows Update for Business reports for all Update Compliance v1 docs-->
|
||||
[!INCLUDE [Recommend Windows Update for Business reports](./includes/wufb-reports-recommend.md)]
|
||||
|
||||
This article is specifically targeted at configuring devices enrolled to [Microsoft Intune](/mem/intune/fundamentals/what-is-intune) for Update Compliance, within Microsoft Intune itself. Configuring devices for Update Compliance in Microsoft Intune breaks down to the following steps:
|
||||
|
||||
1. [Create a configuration profile](#create-a-configuration-profile) for devices you want to enroll, that contains settings for all the MDM policies that must be configured.
|
||||
|
||||
@ -20,6 +20,8 @@ ms.technology: itpro-updates
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
|
||||
<!--Using include for recommending Windows Update for Business reports for all Update Compliance v1 docs-->
|
||||
[!INCLUDE [Recommend Windows Update for Business reports](./includes/wufb-reports-recommend.md)]
|
||||
|
||||
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-configuration-manual.md), as it can provide feedback on whether there are any configuration issues outside of policies being configured.
|
||||
|
||||
@ -50,9 +52,9 @@ Open `RunConfig.bat` and configure the following (assuming a first-run, with `ru
|
||||
## 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
|
||||
<!--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)]:
|
||||
|
||||
|
||||
@ -20,6 +20,9 @@ ms.technology: itpro-updates
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
|
||||
<!--Using include for recommending Windows Update for Business reports for all Update Compliance v1 docs-->
|
||||
[!INCLUDE [Recommend Windows Update for Business reports](./includes/wufb-reports-recommend.md)]
|
||||
|
||||
:::image type="content" alt-text="Screenshot of Delivery Optimization information in Update Compliance." source="images/UC_workspace_DO_status.png" lightbox="images/UC_workspace_DO_status.png":::
|
||||
|
||||
The Update Compliance solution provides you with information about your Delivery Optimization configuration, including the observed bandwidth savings across all devices that used peer-to-peer distribution over the past 28 days.
|
||||
|
||||
@ -19,6 +19,9 @@ ms.technology: itpro-updates
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
|
||||
<!--Using include for recommending Windows Update for Business reports for all Update Compliance v1 docs-->
|
||||
[!INCLUDE [Recommend Windows Update for Business reports](./includes/wufb-reports-recommend.md)]
|
||||
|
||||
[  ](images/UC_workspace_FU_status.png#lightbox)
|
||||
|
||||
The Feature Update Status section provides information about the status of [feature updates](waas-quick-start.md#definitions) across all devices. This section tile in the [Overview Blade](update-compliance-using.md#overview-blade) gives a percentage of devices that are on the latest applicable feature update; [Servicing Channel](waas-overview.md#servicing-channels) is considered in determining applicability. Within this section are two blades; one providing a holistic view of feature updates, the other containing three **Deployment Status** tiles, each charged with tracking the deployment for a different [Servicing Channel](waas-overview.md#servicing-channels).
|
||||
|
||||
@ -21,6 +21,9 @@ ms.technology: itpro-updates
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
|
||||
<!--Using include for recommending Windows Update for Business reports for all Update Compliance v1 docs-->
|
||||
[!INCLUDE [Recommend Windows Update for Business reports](./includes/wufb-reports-recommend.md)]
|
||||
|
||||
This article introduces the high-level steps required to enroll to the Update Compliance solution and configure devices to send data to it. The following steps cover the enrollment and device configuration workflow.
|
||||
|
||||
1. Ensure you can [meet the requirements](#update-compliance-prerequisites) to use Update Compliance.
|
||||
|
||||
@ -20,6 +20,8 @@ ms.technology: itpro-updates
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
|
||||
<!--Using include for recommending Windows Update for Business reports for all Update Compliance v1 docs-->
|
||||
[!INCLUDE [Recommend Windows Update for Business reports](./includes/wufb-reports-recommend.md)]
|
||||
## Introduction
|
||||
|
||||
Update Compliance enables organizations to:
|
||||
|
||||
@ -17,6 +17,9 @@ ms.technology: itpro-updates
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
|
||||
<!--Using include for recommending Windows Update for Business reports for all Update Compliance v1 docs-->
|
||||
[!INCLUDE [Recommend Windows Update for Business reports](./includes/wufb-reports-recommend.md)]
|
||||
|
||||
|
||||
|
||||
The **Needs attention!** section provides a breakdown of all Windows client device and update issues detected by Update Compliance. The summary tile for this section counts the number of devices that have issues, while the blades within break down the issues encountered. Finally, a [list of queries](#list-of-queries) blade in this section contains queries that provide values but do not fit within any other main section.
|
||||
|
||||
@ -19,6 +19,9 @@ ms.technology: itpro-updates
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
|
||||
<!--Using include for recommending Windows Update for Business reports for all Update Compliance v1 docs-->
|
||||
[!INCLUDE [Recommend Windows Update for Business reports](./includes/wufb-reports-recommend.md)]
|
||||
|
||||
The Safeguard Holds report provides information about devices in your population that are affected by a [safeguard hold](/windows/deployment/update/safeguard-holds).
|
||||
|
||||
Microsoft uses diagnostic data to determine whether devices that use Windows Update are ready for a feature update in order to ensure a smooth experience. When Microsoft determines a device is not ready to update due to a known issue, a *safeguard hold* is generated to delay the device's upgrade and protect the end-user experience. Safeguard holds are released over time as diagnostic data is analyzed and fixes are addressed. Details are provided on some, but not all safeguard holds on the Windows client release information pages for any given release.
|
||||
|
||||
@ -13,6 +13,9 @@ ms.technology: itpro-updates
|
||||
|
||||
# WaaSDeploymentStatus
|
||||
|
||||
<!--Using include for recommending Windows Update for Business reports for all Update Compliance v1 docs-->
|
||||
[!INCLUDE [Recommend Windows Update for Business reports](./includes/wufb-reports-recommend.md)]
|
||||
|
||||
|
||||
WaaSDeploymentStatus records track a specific update's installation progress on a specific device. Multiple WaaSDeploymentStatus records can exist simultaneously for a given device, as each record is specific to a given update and its type. For example, a device can have both a WaaSDeploymentStatus tracking a Windows Feature Update, and one tracking a Windows Quality Update, at the same time.
|
||||
|
||||
|
||||
@ -13,6 +13,9 @@ ms.technology: itpro-updates
|
||||
|
||||
# WaaSInsiderStatus
|
||||
|
||||
<!--Using include for recommending Windows Update for Business reports for all Update Compliance v1 docs-->
|
||||
[!INCLUDE [Recommend Windows Update for Business reports](./includes/wufb-reports-recommend.md)]
|
||||
|
||||
WaaSInsiderStatus records contain device-centric data and acts as the device record for devices on Windows Insider Program builds in Update Compliance. Each record provided in daily snapshots maps to a single device in a single tenant. This table has data such as the current device's installed version of Windows, whether it is on the latest available updates, and whether the device needs attention. Insider devices have fewer fields than [WaaSUpdateStatus](update-compliance-schema-waasupdatestatus.md).
|
||||
|
||||
|
||||
|
||||
@ -13,6 +13,9 @@ ms.technology: itpro-updates
|
||||
|
||||
# WaaSUpdateStatus
|
||||
|
||||
<!--Using include for recommending Windows Update for Business reports for all Update Compliance v1 docs-->
|
||||
[!INCLUDE [Recommend Windows Update for Business reports](./includes/wufb-reports-recommend.md)]
|
||||
|
||||
WaaSUpdateStatus records contain device-centric data and acts as the device record for Update Compliance. Each record provided in daily snapshots maps to a single device in a single tenant. This table has data such as the current device's installed version of Windows, whether it is on the latest available updates, and whether the device needs attention.
|
||||
|
||||
|Field |Type |Example |Description |
|
||||
|
||||
@ -13,6 +13,10 @@ ms.technology: itpro-updates
|
||||
|
||||
# WUDOAggregatedStatus
|
||||
|
||||
<!--Using include for recommending Windows Update for Business reports for all Update Compliance v1 docs-->
|
||||
[!INCLUDE [Recommend Windows Update for Business reports](./includes/wufb-reports-recommend.md)]
|
||||
|
||||
|
||||
WUDOAggregatedStatus records provide information, across all devices, on their bandwidth utilization for a specific content type in the event they use [Delivery Optimization](https://support.microsoft.com/help/4468254/windows-update-delivery-optimization-faq), over the past 28 days.
|
||||
|
||||
These fields are briefly described in this article, to learn more about Delivery Optimization in general, check out the [Delivery Optimization Reference](../do/waas-delivery-optimization-reference.md).
|
||||
|
||||
@ -13,6 +13,9 @@ ms.technology: itpro-updates
|
||||
|
||||
# WUDOStatus
|
||||
|
||||
<!--Using include for recommending Windows Update for Business reports for all Update Compliance v1 docs-->
|
||||
[!INCLUDE [Recommend Windows Update for Business reports](./includes/wufb-reports-recommend.md)]
|
||||
|
||||
> [!NOTE]
|
||||
> Currently all location-based fields are not working properly. This is a known issue.
|
||||
|
||||
|
||||
@ -13,6 +13,10 @@ ms.technology: itpro-updates
|
||||
|
||||
# Update Compliance Schema
|
||||
|
||||
<!--Using include for recommending Windows Update for Business reports for all Update Compliance v1 docs-->
|
||||
[!INCLUDE [Recommend Windows Update for Business reports](./includes/wufb-reports-recommend.md)]
|
||||
|
||||
|
||||
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.
|
||||
|
||||
The table below summarizes the different tables that are part of the Update Compliance 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).
|
||||
|
||||
@ -19,6 +19,9 @@ ms.technology: itpro-updates
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
|
||||
<!--Using include for recommending Windows Update for Business reports for all Update Compliance v1 docs-->
|
||||
[!INCLUDE [Recommend Windows Update for Business reports](./includes/wufb-reports-recommend.md)]
|
||||
|
||||
|
||||
|
||||
The Security Update Status section provides information about [security updates](waas-quick-start.md#definitions) across all devices. The section tile within the [Overview Blade](update-compliance-using.md#overview-blade) lists the percentage of devices on the latest security update available. Meanwhile, the blades within show the percentage of devices on the latest security update for each Windows client version and the deployment progress toward the latest two security updates.
|
||||
|
||||
@ -20,6 +20,9 @@ ms.technology: itpro-updates
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
|
||||
<!--Using include for recommending Windows Update for Business reports for all Update Compliance v1 docs-->
|
||||
[!INCLUDE [Recommend Windows Update for Business reports](./includes/wufb-reports-recommend.md)]
|
||||
|
||||
In this section you'll learn how to use Update Compliance to monitor your device's Windows updates and Microsoft Defender Antivirus status. To configure your environment for use with Update Compliance, refer to [Get started with Update Compliance](update-compliance-get-started.md).
|
||||
|
||||
|
||||
|
||||
@ -1,88 +0,0 @@
|
||||
---
|
||||
title: Enable the Update Compliance solution
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
description: How to enable the Update Compliance through the Azure portal
|
||||
ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
ms.date: 06/06/2022
|
||||
ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
# Enable Update Compliance
|
||||
<!--37063317, 30141258, 37063041-->
|
||||
***(Applies to: Windows 11 & Windows 10)***
|
||||
|
||||
> [!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](#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.
|
||||
|
||||
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:
|
||||
|
||||
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. [Add the Update Compliance solution](#bkmk_solution) to the Log Analytics workspace.
|
||||
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:
|
||||
- Use a [script](update-compliance-v2-configuration-script.md)
|
||||
- Use [Microsoft Intune](update-compliance-v2-configuration-mem.md)
|
||||
- Configure [manually](update-compliance-v2-configuration-manual.md)
|
||||
|
||||
> [!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.
|
||||
## <a name="bkmk_add"></a> Add Update Compliance to your Azure subscription
|
||||
|
||||
Before you configure clients to send data, you'll need to add the Update Compliance solution to your Azure subscription so the data can be received. First, you'll select or create a new Log Analytics workspace to use. Second, you'll add the Update Compliance solution to the workspace.
|
||||
|
||||
### <a name="bkmk_workspace"></a> Select or create a new Log Analytics workspace for Update Compliance
|
||||
|
||||
Update Compliance uses an [Azure Log Analytics workspaces](/azure/azure-monitor/logs/log-analytics-overview) that you own for storing the client diagnostic data. Identify an existing workspace or create a new one using the following steps:
|
||||
|
||||
1. Sign in to the Azure portal at [https://portal.azure.com](https://portal.azure.com).
|
||||
- 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. 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).
|
||||
- [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).
|
||||
|
||||
|
||||
|
||||
### <a name="bkmk_solution"></a> Add the Update Compliance solution to the Log Analytics workspace
|
||||
|
||||
Update Compliance is offered as an Azure Marketplace application that's linked to a new or existing Azure Log Analytics workspace within your Azure subscription. Follow the steps below to add the solution, to the workspace:
|
||||
|
||||
1. Go to the [Update Compliance page in the Azure Marketplace](https://azuremarketplace.microsoft.com/marketplace/apps/Microsoft.WaaSUpdateInsights?tab=Overview). You might need to sign into your Azure subscription to access this page.
|
||||
1. Select **Get it now**.
|
||||
1. Select **Continue** to agree to the [terms of use](https://azure.microsoft.com/support/legal/) and the [privacy policy](https://privacy.microsoft.com/en-us/privacystatement) to create the app in Azure.
|
||||
1. Sign into the [Azure portal](https://portal.azure.com) to finish creating the Update Compliance solution.
|
||||
1. Select the following settings:
|
||||
- **Subscription**: The Azure subscription to use.
|
||||
- **Resource group**: Select or [create a resource group](/azure/azure-resource-manager/management/manage-resource-groups-portal) for the Update Compliance solution.
|
||||
- **Azure Log Analytics Workspace**: The Log Analytics workspace you created or identified for use with Update Compliance.
|
||||
1. Select **Review + create** to review your settings.
|
||||
1. Select **Create** to add the solution. You'll receive a notification when the Updates Compliance solution has been successfully created.
|
||||
|
||||
> [!Note]
|
||||
> - You can only map one tenant to one Log Analytics workspace. Mapping one tenant to multiple workspaces isn't supported.
|
||||
> - If you change the Log Analytics workspace for Update Compliance, stale data will be displayed for about 24 hours until the new workspace is fully onboarded. You will also need to reconfigure the Update Compliance settings in the Microsoft 365 admin center.
|
||||
|
||||
### <a name="bkmk_admin-center"></a> Configure Update Compliance settings through the Microsoft 365 admin center
|
||||
|
||||
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-->
|
||||
[!INCLUDE [Onboarding Update Compliance through the Microsoft 365 admin center](./includes/update-compliance-onboard-admin-center.md)]
|
||||
|
||||
|
||||
## 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:
|
||||
|
||||
- [Configure clients with a script](update-compliance-v2-configuration-script.md)
|
||||
- [Configure clients manually](update-compliance-v2-configuration-manual.md)
|
||||
- [Configure clients with Microsoft Intune](update-compliance-v2-configuration-mem.md)
|
||||
@ -1,85 +0,0 @@
|
||||
---
|
||||
title: Update Compliance overview
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
description: Overview of Update Compliance to explain what it's used for and the cloud services it relies on.
|
||||
ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
ms.date: 08/09/2022
|
||||
ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
# Update Compliance overview
|
||||
<!--37063317, 30141258, 37063041-->
|
||||
***(Applies to: Windows 11 & Windows 10)***
|
||||
|
||||
> [!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).
|
||||
> - 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:
|
||||
|
||||
- Monitor security, quality, and feature updates for Windows 11 and Windows 10 devices
|
||||
- Report on devices with update compliance issues
|
||||
- Analyze and display your data in multiple ways
|
||||
|
||||
|
||||
## Preview information for Update Compliance
|
||||
|
||||
The new version of Update Compliance is in preview. Some of the benefits of this new version include:
|
||||
|
||||
- Integration with [Windows Update for Business deployment service](deployment-service-overview.md) to enable per deployment reporting, monitoring, and troubleshooting.
|
||||
- Compatibility with [Feature updates](/mem/intune/protect/windows-10-feature-updates) and [Expedite Windows quality updates](/mem/intune/protect/windows-10-expedite-updates) policies in Intune.
|
||||
- A new **Alerts** data type to assist you with identifying devices that encounter issues during the update process. Error code information is provided to help troubleshoot update issues.
|
||||
|
||||
Currently, the preview contains the following features:
|
||||
|
||||
- [Update Compliance workbook](update-compliance-v2-workbook.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):
|
||||
- UCClient
|
||||
- UCClientReadinessStatus
|
||||
- UCClientUpdateStatus
|
||||
- UCDeviceAlert
|
||||
- UCServiceUpdateStatus
|
||||
- UCUpdateAlert
|
||||
- Client data collection to populate the new Update 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":::
|
||||
|
||||
## Limitations
|
||||
|
||||
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.
|
||||
|
||||
|
||||
## How Update Compliance works
|
||||
|
||||
You'll set up Update Compliance by enrolling into the solution from the Azure portal. Then you'll configure your Azure AD-joined devices to send Windows client diagnostic data to the solution. Update Compliance uses [Log Analytics in Azure Monitor](/azure/azure-monitor/logs/log-analytics-overview) to store the diagnostic data the clients send. You can use this data for reporting on updates for your devices. Update Compliance collects system data such as:
|
||||
|
||||
- Update deployment progress
|
||||
- Delivery Optimization usage data
|
||||
- Windows Update for Business configuration data
|
||||
|
||||
The Azure Log Analytics ingestion and retention charges aren't incurred on your Azure subscription for Update Compliance data. You also choose an [Azure Log Analytics workspaces](/azure/azure-monitor/logs/log-analytics-overview) that you own for your client diagnostic data. The collected diagnostic data populates the Update Compliance tables so you can easily query your data.
|
||||
|
||||
## Use your Update Compliance data
|
||||
|
||||
Since the data from your clients is stored in a Log Analytics workspace, you can go beyond the standard reports to analyze and display your data in multiple ways. Some of the ways you could display your data include:
|
||||
|
||||
- Using the data in [custom workbooks](/azure/azure-monitor/visualize/workbooks-overview) that you create
|
||||
- Building [custom Kusto (KQL) queries](/azure/azure-monitor/logs/log-query-overview)
|
||||
- Developing your own custom views by integrating the [Log Analytics data](/azure/azure-monitor/visualize/tutorial-logs-dashboards) into other tools such as:
|
||||
- [Operations Management Suite](/azure/azure-monitor/agents/om-agents)
|
||||
- [Power BI](/azure/azure-monitor/logs/log-powerbi)
|
||||
- Other tools for [querying the data](/azure/azure-monitor/logs/log-query-overview)
|
||||
|
||||
|
||||
|
||||
## Next steps
|
||||
|
||||
- Review the [Update Compliance prerequisites](update-compliance-v2-prerequisites.md)
|
||||
@ -1,118 +0,0 @@
|
||||
---
|
||||
title: Update Compliance prerequisites
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
description: Prerequisites for Update Compliance
|
||||
ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
ms.date: 06/30/2022
|
||||
ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
# Update Compliance prerequisites
|
||||
<!--37063317, 30141258, 37063041-->
|
||||
***(Applies to: Windows 11 & Windows 10)***
|
||||
|
||||
> [!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).
|
||||
> - 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
|
||||
|
||||
Before you begin the process of adding Update Compliance to your Azure subscription, ensure you meet the prerequisites.
|
||||
|
||||
### Azure and Azure Active Directory
|
||||
|
||||
- An Azure subscription with [Azure Active Directory](/azure/active-directory/)
|
||||
- You must have either an Owner or Contributor [Azure role](/azure/role-based-access-control/rbac-and-directory-admin-roles#azure-roles) as a minimum in order to add the Update Compliance solution.
|
||||
- Devices must be Azure Active Directory-joined and meet the below OS, diagnostic, and endpoint access requirements.
|
||||
- Devices that are Workplace joined only (Azure AD registered) aren't supported with Update Compliance.
|
||||
|
||||
### 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
|
||||
|
||||
Update Compliance 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
|
||||
|
||||
Update Compliance supports Windows client devices on the following channels:
|
||||
|
||||
- General Availability Channel
|
||||
- Update Compliance *counts* Windows Insider Preview devices, but doesn't currently provide detailed deployment insights for them.
|
||||
|
||||
### Diagnostic data requirements
|
||||
|
||||
At minimum, Update Compliance requires devices to send diagnostic data at *Required* level (previously *Basic*). Some queries in Update Compliance require devices to send diagnostic data at the following levels:
|
||||
|
||||
- *Optional* level (previously *Full*) for Windows 11 devices
|
||||
- *Enhanced* level for Windows 10 devices
|
||||
|
||||
> [!Note]
|
||||
> Device names don't appear in Update Compliance unless you individually opt-in devices by using policy. The configuration script does this for you, but when using other client configuration methods, set one of the following to display device names:
|
||||
> - CSP: System/[AllowDeviceNameInDiagnosticData](/windows/client-management/mdm/policy-csp-system#system-allowdevicenameindiagnosticdata)
|
||||
> - Group Policy: **Allow device name to be sent in Windows diagnostic data** under **Computer Configuration\Administrative Templates\Windows Components\Data Collection and Preview Builds**
|
||||
|
||||
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
|
||||
|
||||
<!--Using include for endpoint access requirements-->
|
||||
[!INCLUDE [Endpoints for Update Compliance](./includes/update-compliance-endpoints.md)]
|
||||
|
||||
> [!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.
|
||||
|
||||
## 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)]
|
||||
|
||||
## 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
|
||||
|
||||
Update Compliance can use a Log Analytics workspace in the following regions:
|
||||
|
||||
|Compatible Log Analytics regions |
|
||||
| ------------------------------- |
|
||||
|Australia Central |
|
||||
|Australia East |
|
||||
|Australia Southeast |
|
||||
|Brazil South |
|
||||
|Canada Central |
|
||||
|Central India |
|
||||
|Central US |
|
||||
|East Asia |
|
||||
|East US |
|
||||
|East US 2 |
|
||||
|Eastus2euap(canary) |
|
||||
|France Central |
|
||||
|Japan East |
|
||||
|Korea Central |
|
||||
|North Central US |
|
||||
|North Europe |
|
||||
|South Africa North |
|
||||
|South Central US |
|
||||
|Southeast Asia |
|
||||
|Switzerland North |
|
||||
|Switzerland West |
|
||||
|UK West |
|
||||
|UK south |
|
||||
|West Central US |
|
||||
|West Europe |
|
||||
|West US |
|
||||
|West US 2 |
|
||||
|
||||
## Next steps
|
||||
|
||||
- [Enable the Update Compliance solution](update-compliance-v2-enable.md) in the Azure portal
|
||||
@ -1,39 +0,0 @@
|
||||
---
|
||||
title: Update Compliance (preview) data schema
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
description: An overview of Update Compliance (preview) data schema
|
||||
ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: reference
|
||||
ms.date: 06/06/2022
|
||||
ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
# Update Compliance version 2 schema
|
||||
<!--37063317, 30141258, 37063041-->
|
||||
***(Applies to: Windows 11 & Windows 10)***
|
||||
|
||||
> [!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).
|
||||
> - 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.
|
||||
|
||||
## Schema
|
||||
|
||||
The table below summarizes the different tables that are part of the Update Compliance 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.
|
||||
|
||||
|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). |
|
||||
|[**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.|
|
||||
| [**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. |
|
||||
| [**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. |
|
||||
| [**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. |
|
||||
| [**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. |
|
||||
@ -1,64 +0,0 @@
|
||||
---
|
||||
title: Use the Update Compliance (preview) data
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
description: How to use the Update Compliance (preview) data.
|
||||
ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
ms.date: 06/06/2022
|
||||
ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
# Use Update Compliance (preview)
|
||||
<!--37063317, 30141258, 37063041-->
|
||||
***(Applies to: Windows 11 & Windows 10)***
|
||||
|
||||
> [!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.
|
||||
|
||||
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).
|
||||
|
||||
## Display Update Compliance data
|
||||
|
||||
1. Sign into the [Azure portal](https://portal.azure.com).
|
||||
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 the workspace that you use for Updates Compliance.
|
||||
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. 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.
|
||||
|
||||
```kusto
|
||||
UCUpdateAlert
|
||||
| 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":::
|
||||
|
||||
## Update Compliance data latency
|
||||
|
||||
Update Compliance uses Windows client diagnostic data as its data source. After you add Update Compliance and appropriately configure your devices, it could take 48-72 hours before they first appear.
|
||||
|
||||
The data powering Update Compliance 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 Update Compliance.
|
||||
|
||||
| Data Type | Data upload rate from device | Data Latency |
|
||||
|--|--|--|
|
||||
| UCClient | Once per day |4 hours |
|
||||
| UCClientUpdateStatus|Every update event (Download, install, etc.)|24-36 hours |
|
||||
| UCServiceUpdateStatus| Every update event (Download, install, etc.)|24-36 hours |
|
||||
| UCUpdateAlert | Every event | 24-36 hours |
|
||||
| UCDeviceAlert | Every event | 24-36 hours |
|
||||
| UCClientReadinessStatus | After Windows 11 readiness assessment |24-36 hours |
|
||||
|
||||
## Working with Azure Monitor Logs
|
||||
|
||||
Update Compliance is built on the Azure Monitor Logs platform. All Update Compliance-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 Update Compliance.
|
||||
|
||||
See the Azure Monitor Logs articles below 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.
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Microsoft admin center software updates (preview) page
|
||||
title: Microsoft 365 admin center software updates page
|
||||
manager: dougeby
|
||||
description: Microsoft admin center populates Update Compliance data into the software updates page.
|
||||
description: Microsoft admin center populates Windows Update for Business reports data into the software updates page.
|
||||
ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
@ -13,12 +13,9 @@ ms.date: 06/20/2022
|
||||
ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
# Microsoft admin center software updates (preview) page
|
||||
# Microsoft 365 admin center software updates page
|
||||
<!--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))***
|
||||
|
||||
> [!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.
|
||||
***(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))***
|
||||
|
||||
The **Software updates** page in the [Microsoft 365 admin center](https://admin.microsoft.com) displays a high-level overview of the installation status for Microsoft 365 Apps and Windows updates in your environment. [Quality updates](quality-updates.md) that contain security fixes are typically released on the second Tuesday of each month. Ensuring these updates are installed is important because they help protect you from known vulnerabilities. The **Software updates** page allows you to easily determine the overall update compliance for your devices.
|
||||
|
||||
@ -28,26 +25,28 @@ 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 [Update Compliance script error codes](./includes/update-compliance-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
|
||||
|
||||
Update Compliance is a Windows service hosted in Azure that uses Windows diagnostic data. Update Compliance is available in the Azure Commercial cloud, but not available for GCC High or United States Department of Defense customers since it 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).
|
||||
Windows Update for Business reports is a Windows service hosted in Azure that uses Windows diagnostic data. Windows Update for Business reports is available in the Azure Commercial cloud, but not available for GCC High or United States Department of Defense customers since it 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).
|
||||
|
||||
## Get started
|
||||
|
||||
|
||||
<!--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)]
|
||||
<!--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)]
|
||||
|
||||
## 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 [Windows Update for Business reports](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 Windows Update for Business reports data that populates these charts refreshes every 24 hours. For more information, see [Windows Update for Business reports data latency](wufb-reports-use.md#data-latency).
|
||||
|
||||
### Windows update status chart
|
||||
|
||||
@ -69,4 +68,4 @@ The **End of service** chart list the number of devices running an operating sys
|
||||
|
||||
## Next steps
|
||||
|
||||
Use [Update Compliance](update-compliance-v2-overview.md) to display additional data about the status of Windows updates.
|
||||
Use [Windows Update for Business reports](wufb-reports-overview.md) to display additional data about the status of Windows updates.
|
||||
@ -1,8 +1,8 @@
|
||||
---
|
||||
title: Configuring Microsoft Intune devices for Update Compliance (preview)
|
||||
title: Configuring Microsoft Intune devices for Windows Update for Business reports
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
description: Configuring devices that are enrolled in Intune for Update Compliance (preview)
|
||||
manager: aaroncz
|
||||
description: Configuring devices that are enrolled in Microsoft Intune for Windows Update for Business reports
|
||||
ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
@ -13,28 +13,24 @@ ms.date: 08/24/2022
|
||||
ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
# Configuring Microsoft Intune devices for Update Compliance (preview)
|
||||
# Configuring Microsoft Intune devices for Windows Update for Business reports (preview)
|
||||
<!--37063317, 30141258, 37063041-->
|
||||
***(Applies to: Windows 11 & Windows 10 managed by [Microsoft Intune](/mem/intune/fundamentals/what-is-intune)***
|
||||
|
||||
> [!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).
|
||||
> - 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 Intune](/mem/intune/fundamentals/what-is-intune) for Update Compliance. Configuring devices for Update Compliance 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 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 Windows Update for Business reports](wufb-reports-use.md).
|
||||
|
||||
> [!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.
|
||||
|
||||
## Create a configuration profile
|
||||
|
||||
Create a configuration profile that will set the required policies for Update Compliance. There are two profile types that can be used to create a configuration profile for Update Compliance:
|
||||
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
|
||||
|
||||
@ -43,35 +39,31 @@ Create a configuration profile that will set the required policies for Update Co
|
||||
1. Select **Platform**="Windows 10 and later" and **Profile type**="Settings Catalog", and then select **Create**.
|
||||
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 settings from the **System** category. Using the **Settings picker**, select the **System** category, then add the following settings and values:
|
||||
1. Required settings for Update Compliance:
|
||||
1. Required settings for Windows Update for Business reports:
|
||||
- **Setting**: Allow Commercial Data Pipeline
|
||||
- **Value**: Enabled
|
||||
- **Setting**: Allow Telemetry
|
||||
- **Value**: Basic (*Basic is the minimum value, but it can be safely set to a higher value*)
|
||||
- **Setting**: Allow Update Compliance Processing
|
||||
- **Value**: Enabled
|
||||
1. (*Recommended, but not required*) Add settings for **disabling devices' Diagnostic Data opt-in settings interface**. If these settings 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 Update Compliance:
|
||||
- **Setting**: Configure Telemetry Opt In Change Notification
|
||||
- **Value**: Disable telemetry change notifications
|
||||
- **Setting**: Configure Telemetry Opt In Settings Ux
|
||||
- **Value**: Disable Telemetry opt-in Settings
|
||||
1. (*Recommended, but not required*) Allow device name to be sent in Windows Diagnostic Data. If this policy is disabled, then the device name won't be sent and won't be visible in Update Compliance:
|
||||
1. (*Recommended, but not required*) Allow device name to be sent in Windows Diagnostic Data. If this policy is disabled, the device name won't be sent and won't be visible in Windows Update for Business reports:
|
||||
- **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**.
|
||||
1. Select **Platform**="Windows 10 and later" and **Profile type**="Templates".
|
||||
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. 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 Windows Update for Business reports](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 Windows Update for Business reports:
|
||||
- **Name**: Allow commercial data pipeline
|
||||
- **Description**: Configures Microsoft to be the processor of the Windows diagnostic data collected from an Azure Active Directory-joined device.
|
||||
- **OMA-URI**: `./Vendor/MSFT/Policy/Config/System/AllowCommercialDataPipeline`
|
||||
@ -79,23 +71,23 @@ Create a configuration profile that will set the required policies for Update Co
|
||||
- **Value**: 1
|
||||
1. Add a setting configuring the **Windows Diagnostic Data level** for devices:
|
||||
- **Name**: Allow Telemetry
|
||||
- **Description**: Sets the maximum allowed diagnostic data to be sent to Microsoft, required for Update Compliance.
|
||||
- **Description**: Sets the maximum allowed diagnostic data to be sent to Microsoft, required for Windows Update for Business reports.
|
||||
- **OMA-URI**: `./Vendor/MSFT/Policy/Config/System/AllowTelemetry`
|
||||
- **Data type**: Integer
|
||||
- **Value**: 1 (*1 is the minimum value meaning basic, but it can be safely set to a higher value*).
|
||||
1. Add a setting to **Allow Update Compliance processing**; this policy is required for Update Compliance:
|
||||
1. Add a setting to **Allow Update Compliance processing**; this policy is required for Windows Update for Business reports:
|
||||
- **Name**: Allow Update Compliance Processing
|
||||
- **Description**: Opts device data into Update Compliance processing. Required to see data.
|
||||
- **OMA-URI**: `./Vendor/MSFT/Policy/Config/System/AllowUpdateComplianceProcessing`
|
||||
- **Data type**: Integer
|
||||
- **Value**: 16
|
||||
1. (*Recommended, but not required*) Add settings for **disabling devices' Diagnostic Data opt-in settings interface**. If these settings 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 Update Compliance:
|
||||
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
|
||||
1. (*Recommended, but not required*) Add a setting to **Allow device name in diagnostic data**; otherwise, the device name won't be in Update Compliance:
|
||||
1. (*Recommended, but not required*) Add a setting to **Allow device name in diagnostic data**; otherwise, the device name won't be in Windows Update for Business reports:
|
||||
- **Name**: Allow device name in Diagnostic Data
|
||||
- **Description**: Allows device name in Diagnostic Data.
|
||||
- **OMA-URI**: `./Vendor/MSFT/Policy/Config/System/AllowDeviceNameInDiagnosticData`
|
||||
@ -103,15 +95,15 @@ Create a configuration profile that will set the required policies for Update Co
|
||||
- **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 [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 [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 that 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 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
|
||||
|
||||
[Use Update Compliance](update-compliance-v2-use.md)
|
||||
[Use Windows Update for Business reports](wufb-reports-use.md)
|
||||
@ -1,8 +1,8 @@
|
||||
---
|
||||
title: Manually configuring devices for Update Compliance (preview)
|
||||
title: Manually configuring devices for Windows Update for Business reports
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
description: Manually configuring devices for Update Compliance (preview)
|
||||
description: How to manually configure devices for Windows Update for Business reports
|
||||
ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
@ -13,30 +13,26 @@ ms.date: 06/06/2022
|
||||
ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
# Manually Configuring Devices for Update Compliance (preview)
|
||||
# Manually configuring devices for Windows Update for Business reports (preview)
|
||||
<!--37063317, 30141258, 37063041-->
|
||||
***(Applies to: Windows 11 & Windows 10)***
|
||||
|
||||
> [!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).
|
||||
> - 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 Windows Update for Business reports. These requirements can potentially change with newer versions of Windows client. The [Windows Update for Business reports 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:
|
||||
|
||||
1. Ensuring the [**required policies**](#required-policies) for Update Compliance are correctly configured.
|
||||
2. Devices in every network topography must send data to the [**required endpoints**](#required-endpoints) for Update Compliance. For example, devices in both main and satellite offices, which might have different network configurations, must be able to reach the endpoints.
|
||||
1. Ensuring the [**required policies**](#required-policies) for Windows Update for Business reports are correctly configured.
|
||||
2. Devices in every network topography must send data to the [**required endpoints**](#required-endpoints) for Windows Update for Business reports. For example, devices in both main and satellite offices, which might have different network configurations, must be able to reach the endpoints.
|
||||
3. Ensure [**Required Windows services**](#required-services) are running or are scheduled to run. It's recommended all Microsoft and Windows services are set to their out-of-box defaults to ensure proper functionality.
|
||||
|
||||
|
||||
## Required policies
|
||||
|
||||
Update Compliance has a number of policies that must be appropriately configured in order for devices to be processed by Microsoft and visible in Update Compliance. Thee policies are listed below, separated by whether the policies will be configured via [Mobile Device Management](/windows/client-management/mdm/) (MDM) or Group Policy. For both tables:
|
||||
Windows Update for Business reports has a number of policies that must be appropriately configured in order for devices to be processed by Microsoft and visible in Windows Update for Business reports. Thee policies are listed below, separated by whether the policies will be configured via [Mobile Device Management](/windows/client-management/mdm/) (MDM) or Group Policy. For both tables:
|
||||
|
||||
- **Policy** corresponds to the location and name of the policy.
|
||||
- **Value** Indicates what value the policy must be set to. Update Compliance requires *at least* Basic (or Required) diagnostic data, but can function off Enhanced or Full (or Optional).
|
||||
- **Function** details why the policy is required and what function it serves for Update Compliance. It will also detail a minimum version the policy is required, if any.
|
||||
- **Value** Indicates what value the policy must be set to. Windows Update for Business reports requires *at least* Basic (or Required) diagnostic data, but can function off Enhanced or Full (or Optional).
|
||||
- **Function** details why the policy is required and what function it serves for Windows Update for Business reports. It will also detail a minimum version the policy is required, if any.
|
||||
|
||||
### Mobile Device Management policies
|
||||
|
||||
@ -46,20 +42,20 @@ 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 Update Compliance, showing `#` instead. |
|
||||
| **System/**[**AllowUpdateComplianceProcessing**](/windows/client-management/mdm/policy-csp-system#system-allowUpdateComplianceProcessing) |Integer | 16 - Allowed | Enables data flow through Update Compliance'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
|
||||
|
||||
All Group policies that need to be configured for Update Compliance are under **Computer Configuration>Administrative Templates>Windows Components\Data Collection and Preview Builds**. All of these policies must be in the *Enabled* state and set to the defined *Value* below.
|
||||
All Group policies that need to be configured for Windows Update for Business reports are under **Computer Configuration>Administrative Templates>Windows Components\Data Collection and Preview Builds**. All of these policies must be in the *Enabled* state and set to the defined *Value* below.
|
||||
|
||||
| Policy | Value | Function |
|
||||
|---------------------------|-|-----------------------------------------------------------|
|
||||
|**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 Update Compliance, showing `#` instead. |
|
||||
|**Allow Update Compliance processing** | 16 - Enabled | Enables data flow through Update Compliance's data processing system and indicates a device's explicit enrollment to the service. |
|
||||
|**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 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
|
||||
@ -67,12 +63,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.
|
||||
|
||||
<!--Using include for endpoint access requirements-->
|
||||
[!INCLUDE [Endpoints for Update Compliance](./includes/update-compliance-endpoints.md)]
|
||||
[!INCLUDE [Endpoints for Windows Update for Business reports](./includes/wufb-reports-endpoints.md)]
|
||||
|
||||
## 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 Windows Update for Business reports can see device data. It's recommended that you allow all default services from the out-of-box experience to remain running. The [Windows Update for Business reports Configuration Script](wufb-reports-configuration-script.md) checks whether the majority of these services are running or are allowed to run automatically.
|
||||
|
||||
## Next steps
|
||||
|
||||
[Use Update Compliance](update-compliance-v2-use.md)
|
||||
[Use Windows Update for Business reports](wufb-reports-use.md)
|
||||
@ -1,8 +1,8 @@
|
||||
---
|
||||
title: Update Compliance (preview) Configuration Script
|
||||
title: Windows Update for Business reports configuration script
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
description: Downloading and using the Update Compliance (preview) Configuration Script
|
||||
description: Downloading and using the Windows Update for Business reports configuration script
|
||||
ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
@ -13,19 +13,15 @@ ms.date: 06/16/2022
|
||||
ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
# Configuring devices through the Update Compliance (preview) Configuration Script
|
||||
# Configuring devices through the Windows Update for Business reports (preview) configuration script
|
||||
<!--37063317, 30141258, 37063041-->
|
||||
***(Applies to: Windows 11 & Windows 10)***
|
||||
|
||||
> [!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).
|
||||
> - 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 Windows Update for Business reports configuration script is the recommended method of configuring devices to send data to Microsoft for use with Windows Update for Business reports. 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 configure devices for Windows Update for Business reports](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
|
||||
|
||||
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 Windows Update for Business reports](wufb-reports-configuration-manual.md), device data might not appear in Windows Update for Business reports 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.
|
||||
|
||||
@ -44,7 +40,7 @@ This script's two primary files are `ConfigScript.ps1` and `RunConfig.bat`. You
|
||||
Open `RunConfig.bat` and configure the following (assuming a first-run, with `runMode=Pilot`):
|
||||
|
||||
1. Define `logPath` to where you want the logs to be saved. Ensure that `runMode=Pilot`.
|
||||
1. Don't modify the [Commercial ID](update-compliance-get-started.md#get-your-commercialid) values since they're used for the earlier version of Update Compliance. Leave `setCommercialID=false` and the `commercialIDValue=Unknown`.
|
||||
1. Don't modify the [Commercial ID](update-compliance-get-started.md#get-your-commercialid) values since they're used for the earlier version of Windows Update for Business reports (Update Compliance). Leave `setCommercialID=false` and the `commercialIDValue=Unknown`.
|
||||
1. Run the script.
|
||||
1. Examine the logs for any issues. If there are no issues, then all devices with a similar configuration and network profile are ready for the script to be deployed with `runMode=Deployment`.
|
||||
1. If there are issues, gather the logs and provide them to Microsoft Support.
|
||||
@ -52,14 +48,14 @@ Open `RunConfig.bat` and configure the following (assuming a first-run, with `ru
|
||||
## Verify device configuration
|
||||
|
||||
<!--Using include for verifying device configuration-->
|
||||
[!INCLUDE [Endpoints for Update Compliance](./includes/update-compliance-verify-device-configuration.md)]
|
||||
[!INCLUDE [Endpoints for Windows Update for Business reports](./includes/wufb-reports-verify-device-configuration.md)]
|
||||
|
||||
## Script errors
|
||||
|
||||
<!--Using include for script errors-->
|
||||
[!INCLUDE [Update Compliance script error codes](./includes/update-compliance-script-error-codes.md)]
|
||||
[!INCLUDE [Windows Update for Business reports script error codes](./includes/wufb-reports-script-error-codes.md)]
|
||||
|
||||
|
||||
## Next steps
|
||||
|
||||
[Use Update Compliance](update-compliance-v2-use.md)
|
||||
[Use Windows Update for Business reports](wufb-reports-use.md)
|
||||
83
windows/deployment/update/wufb-reports-enable.md
Normal file
83
windows/deployment/update/wufb-reports-enable.md
Normal file
@ -0,0 +1,83 @@
|
||||
---
|
||||
title: Enable Windows Update for Business reports
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
description: How to enable Windows Update for Business reports through the Azure portal
|
||||
ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
ms.date: 06/06/2022
|
||||
ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
# Enable Windows Update for Business reports (preview)
|
||||
<!--37063317, 30141258, 37063041-->
|
||||
***(Applies to: Windows 11 & Windows 10)***
|
||||
|
||||
After verifying the [prerequisites](wufb-reports-prerequisites.md) are met, you can start to set up Windows Update for Business reports. The two main steps for setting up Windows Update for Business reports are:
|
||||
|
||||
1. [Add Windows Update for Business reports](#bkmk_add) to your Azure subscription. This step has the following phases:
|
||||
1. [Select or create a new Log Analytics workspace](#bkmk_workspace) for use with Windows Update for Business reports.
|
||||
1. Enroll into Windows Update for Business reports using one of the following methods:
|
||||
- Enroll through the [Azure Workbook](#bkmk_enroll) (preferred method)
|
||||
- Enroll from the [Microsoft 365 admin center](#bkmk_admin-center).
|
||||
|
||||
1. Configure the clients to send data to Windows Update for Business reports. You can configure clients in the following three ways:
|
||||
- Use a [script](wufb-reports-configuration-script.md)
|
||||
- Use [Microsoft Intune](wufb-reports-configuration-intune.md)
|
||||
- Configure [manually](wufb-reports-configuration-manual.md)
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Windows Update for Business reports is a Windows service hosted in Azure that uses Windows diagnostic data. You should be aware that Windows Update for Business reports 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). Windows Update for Business reports is available in the Azure Commercial cloud, but not available for GCC High or United States Department of Defense customers.
|
||||
|
||||
## <a name="bkmk_add"></a> Add Windows Update for Business reports to your Azure subscription
|
||||
|
||||
Before you configure clients to send data, you'll need to add Windows Update for Business reports to your Azure subscription so the data can be received. First, you'll select or create a new Log Analytics workspace to use. Second, you'll enroll Windows Update for Business reports to the workspace.
|
||||
|
||||
## <a name="bkmk_workspace"></a> Select or create a new Log Analytics workspace for Windows Update for Business reports
|
||||
|
||||
Windows Update for Business reports uses an [Azure Log Analytics workspaces](/azure/azure-monitor/logs/log-analytics-overview) that you own for storing the client diagnostic data. Identify an existing workspace or create a new one using the following steps:
|
||||
|
||||
1. Sign in to the Azure portal at [https://portal.azure.com](https://portal.azure.com).
|
||||
- Although an Azure subscription is required, you won't be charged for ingestion of Windows Update for Business reports 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. Select **Log Analytics workspaces**.
|
||||
1. If you already have a Log Analytics workspace, determine which Log Analytics workspace you'd like to use for Windows Update for Business reports. 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 Windows Update for Business reports.
|
||||
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).
|
||||
|
||||
> [!Note]
|
||||
> - You can only map one tenant to one Log Analytics workspace. Mapping one tenant to multiple workspaces isn't supported.
|
||||
> - If you change the Log Analytics workspace for Windows Update for Business reports, stale data will be displayed for about 24 hours until the new workspace is fully onboarded. You will also need to reconfigure the Windows Update for Business reports settings to enroll again.
|
||||
|
||||
## <a name="bkmk_enroll"></a> Enroll into Windows Update for Business reports
|
||||
|
||||
Enroll into Windows Update for Business reports by configuring its settings through either the Azure Workbook or from the Microsoft 365 admin center. Completing the Windows Update for Business reports configuration removes needing to specify [`CommercialID`](update-compliance-get-started.md#get-your-commercialid), which was needed by Update Compliance, the predecessor of Windows Update for Business reports. This step is needed even if you enabled previews of Update Compliance.
|
||||
|
||||
Use one of the following methods to enroll into Windows Update for Business reports:
|
||||
|
||||
##### <a name="bkmk_enroll-workbook"></a> Enroll through the Azure Workbook (recommended method)
|
||||
|
||||
1. In the [Azure portal](https://portal.azure.com), select **Monitor** > **Workbooks** from the menu bar.
|
||||
- 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 **Windows Update for Business reports** workbook. If needed, you can filter workbooks by name in the gallery.
|
||||
1. Select the **Get started** button when prompted by the workbook to open the **Windows Update for Business reports enrollment** flyout.
|
||||
1. In the flyout, specify which **Subscription** and **Azure Log Analytics Workspace** you want to use for Windows Update for Business reports.
|
||||
- If you need to create a new Log Analytics workspace, select **Create new workspace** and follow the prompts to [create a new workspace](#bkmk_workspace).
|
||||
1. Select **Save settings** to save the settings and enroll into Windows Update for Business reports.
|
||||
1. The initial setup can take up to 24 hours. During this time, the workbook will display that it's **Waiting for Windows Update for Business reports data**.
|
||||
|
||||
##### <a name="bkmk_admin-center"></a> Enroll through the Microsoft 365 admin center
|
||||
<!--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)]
|
||||
|
||||
## Next steps
|
||||
|
||||
Once you've added Windows Update for Business reports 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 Windows Update for Business reports using any of the following methods:
|
||||
|
||||
- [Configure clients with a script](wufb-reports-configuration-script.md)
|
||||
- [Configure clients manually](wufb-reports-configuration-manual.md)
|
||||
- [Configure clients with Microsoft Intune](wufb-reports-configuration-intune.md)
|
||||
@ -1,8 +1,8 @@
|
||||
---
|
||||
title: Update Compliance (preview) feedback, support, and troubleshooting
|
||||
title: Windows Update for Business reports feedback, support, and troubleshooting
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
description: Update Compliance (preview) support information.
|
||||
description: Windows Update for Business reports support information.
|
||||
ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
@ -12,48 +12,44 @@ ms.date: 08/10/2022
|
||||
ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
# Update Compliance (preview) feedback, support, and troubleshooting
|
||||
# Windows Update for Business reports (preview) feedback, support, and troubleshooting
|
||||
|
||||
<!-- MAX6325272, OS33771278 -->
|
||||
***(Applies to: Windows 11 & Windows 10)***
|
||||
|
||||
> [!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).
|
||||
> - 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 Windows Update for Business reports. Whether you're just getting started or an experienced administrator, use the following resources when you need help with Windows Update for Business reports:
|
||||
|
||||
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:
|
||||
|
||||
- Send [product feedback about Update Compliance](#send-product-feedback)
|
||||
- Send [product feedback about Windows Update for Business reports](#send-product-feedback)
|
||||
- Open a [Microsoft support case](#open-a-microsoft-support-case)
|
||||
|
||||
- [Documentation feedback](#documentation-feedback)
|
||||
- [Troubleshooting tips](#troubleshooting-tips) for Update Compliance
|
||||
- Follow the [Windows IT Pro blog](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/bg-p/Windows10Blog) to learn about upcoming changes to Update Compliance
|
||||
- [Troubleshooting tips](#troubleshooting-tips) for Windows Update for Business reports
|
||||
- Follow the [Windows IT Pro blog](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/bg-p/Windows10Blog) to learn about upcoming changes to Windows Update for Business reports
|
||||
- Use Microsoft Q&A to [ask product questions](/answers/products/)
|
||||
|
||||
## Send product feedback
|
||||
|
||||
Use the product feedback option to offer suggestions for new features and functionality, or for suggesting changes to the current Update Compliance features. You can share feedback directly to the Update Compliance 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.
|
||||
1. In the text box, describe what you did or didn't like. When providing feedback about a problem, be sure to include enough detail in your description so it can be properly identified by the product group.
|
||||
1. Choose if you'd like to allow Microsoft to email you about your feedback.
|
||||
1. Select **Submit feedback** when you've completed the feedback form.
|
||||
:::image type="content" source="media/33771278-update-compliance-feedback.png" alt-text="Screenshot of the Azure portal showing the product feedback option flyout." lightbox="media/33771278-update-compliance-feedback.png":::
|
||||
:::image type="content" source="media/33771278-wufb-reports-feedback.png" alt-text="Screenshot of the Azure portal showing the product feedback option flyout." lightbox="media/33771278-wufb-reports-feedback.png":::
|
||||
|
||||
## Open a Microsoft support case
|
||||
|
||||
You can open support requests directly from the Azure portal. If the **Help + Support** page doesn't display, verify you have access to open support requests. For more information about role-based access controls for support requests, see [Create an Azure support request](/azure/azure-portal/supportability/how-to-create-azure-support-request). To create a new support request for Update Compliance:
|
||||
You can open support requests directly from the Azure portal. If the **Help + Support** page doesn't display, verify you have access to open support requests. For more information about role-based access controls for support requests, see [Create an Azure support request](/azure/azure-portal/supportability/how-to-create-azure-support-request). To create a new support request for Windows Update for Business reports:
|
||||
|
||||
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 Update Compliance 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 Update Compliance
|
||||
- **Subscription** - Select the subscription used for Windows Update for Business reports
|
||||
- **Service** - ***My services***
|
||||
- **Service type** - ***Log Analytics***
|
||||
- **Problem type** - ***Solutions or Insights***
|
||||
@ -83,29 +79,29 @@ Use GitHub Issues to submit the following types of feedback:
|
||||
|
||||
If you create an issue for something not related to documentation, Microsoft will close the issue and redirect you to a better feedback channel. For example:
|
||||
|
||||
- [Product feedback](#send-product-feedback) for Update Compliance
|
||||
- [Product feedback](#send-product-feedback) for Windows Update for Business reports
|
||||
- [Product questions (using Microsoft Q&A)](/answers/products/)
|
||||
- [Support requests](#open-a-microsoft-support-case) for Update Compliance
|
||||
- [Support requests](#open-a-microsoft-support-case) for Windows Update for Business reports
|
||||
|
||||
To share feedback about the Microsoft Learn platform, see [Microsoft Learn feedback](https://aka.ms/sitefeedback). The platform includes all of the wrapper components such as the header, table of contents, and right menu. Also how the articles render in the browser, such as the font, alert boxes, and page anchors.
|
||||
|
||||
## Troubleshooting tips
|
||||
|
||||
Use the troubleshooting tips below to resolve commonly encountered problems when using Update Compliance:
|
||||
Use the following troubleshooting tips to resolve the most common problems when using Windows Update for Business reports:
|
||||
|
||||
### Verify client configuration
|
||||
|
||||
<!--Using include for verifying device configuration-->
|
||||
[!INCLUDE [Endpoints for Update Compliance](./includes/update-compliance-verify-device-configuration.md)]
|
||||
[!INCLUDE [Endpoints for Windows Update for Business reports](./includes/wufb-reports-verify-device-configuration.md)]
|
||||
|
||||
### 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 Windows Update for Business reports is ensuring that devices are configured. Review [Manually configuring devices for Windows Update for Business reports](wufb-reports-configuration-manual.md) for the settings. We recommend using the [Windows Update for Business reports 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 Windows Update for Business reports
|
||||
|
||||
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 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 Update Compliance](update-compliance-v2-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.
|
||||
79
windows/deployment/update/wufb-reports-overview.md
Normal file
79
windows/deployment/update/wufb-reports-overview.md
Normal file
@ -0,0 +1,79 @@
|
||||
---
|
||||
title: Windows Update for Business reports overview
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
description: Overview of Windows Update for Business reports to explain what it's used for and the cloud services it relies on.
|
||||
ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
ms.date: 08/09/2022
|
||||
ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
# Windows Update for Business reports (preview) overview
|
||||
<!--37063317, 30141258, 37063041-->
|
||||
***(Applies to: Windows 11 & Windows 10)***
|
||||
|
||||
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
|
||||
- Analyze and display your data in multiple ways
|
||||
|
||||
|
||||
## Benefits of Windows Update for Business reports
|
||||
|
||||
Some of the benefits of Windows Update for Business reports are:
|
||||
|
||||
- Integration with [Windows Update for Business deployment service](deployment-service-overview.md) to enable per deployment reporting, monitoring, and troubleshooting.
|
||||
- Compatibility with [feature updates](/mem/intune/protect/windows-10-feature-updates) and [Expedite Windows quality updates](/mem/intune/protect/windows-10-expedite-updates) policies in Intune.
|
||||
- A new **Alerts** data type to assist you with identifying devices that encounter issues during the update process. Error code information is provided to help troubleshoot update issues.
|
||||
|
||||
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](wufb-reports-admin-center.md)
|
||||
- Access to the following [Windows Update for Business reports tables](wufb-reports-schema.md):
|
||||
- UCClient
|
||||
- UCClientReadinessStatus
|
||||
- UCClientUpdateStatus
|
||||
- UCDeviceAlert
|
||||
- UCServiceUpdateStatus
|
||||
- UCUpdateAlert
|
||||
- Client data collection to populate the Windows Update for Business reports 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":::
|
||||
|
||||
## Limitations
|
||||
|
||||
Windows Update for Business reports is a Windows service hosted in Azure that uses Windows diagnostic data. You should be aware that Windows Update for Business reports 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). Windows Update for Business reports is available in the Azure Commercial cloud, but not available for GCC High or United States Department of Defense customers.
|
||||
|
||||
|
||||
## How Windows Update for Business reports works
|
||||
|
||||
You'll set up Windows Update for Business reports by enrolling into the service from the Azure portal. Then you'll configure your Azure AD-joined devices to send Windows client diagnostic data to the service. Windows Update for Business reports uses [Log Analytics in Azure Monitor](/azure/azure-monitor/logs/log-analytics-overview) to store the diagnostic data the clients send. You can use this data for reporting on updates for your devices. Windows Update for Business reports collects system data such as:
|
||||
|
||||
- Update deployment progress
|
||||
- Delivery Optimization usage data
|
||||
- Windows Update for Business configuration data
|
||||
|
||||
The Azure Log Analytics ingestion and retention charges aren't incurred on your Azure subscription for Windows Update for Business reports data. You also choose an [Azure Log Analytics workspaces](/azure/azure-monitor/logs/log-analytics-overview) that you own for your client diagnostic data. The collected diagnostic data populates the Windows Update for Business reports tables so you can easily query your data.
|
||||
|
||||
## Use your Windows Update for Business reports data
|
||||
|
||||
Since the data from your clients is stored in a Log Analytics workspace, you can go beyond the standard reports to analyze and display your data in multiple ways. Some of the ways you could display your data include:
|
||||
|
||||
- Using the data in [custom workbooks](/azure/azure-monitor/visualize/workbooks-overview) that you create
|
||||
- Building [custom Kusto (KQL) queries](/azure/azure-monitor/logs/log-query-overview)
|
||||
- Developing your own custom views by integrating the [Log Analytics data](/azure/azure-monitor/visualize/tutorial-logs-dashboards) into other tools such as:
|
||||
- [Operations Management Suite](/azure/azure-monitor/agents/om-agents)
|
||||
- [Power BI](/azure/azure-monitor/logs/log-powerbi)
|
||||
- Other tools for [querying the data](/azure/azure-monitor/logs/log-query-overview)
|
||||
|
||||
|
||||
|
||||
## Next steps
|
||||
|
||||
- Review the [Windows Update for Business reports prerequisites](wufb-reports-prerequisites.md)
|
||||
110
windows/deployment/update/wufb-reports-prerequisites.md
Normal file
110
windows/deployment/update/wufb-reports-prerequisites.md
Normal file
@ -0,0 +1,110 @@
|
||||
---
|
||||
title: Windows Update for Business reports prerequisites
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
description: Prerequisites for Windows Update for Business reports
|
||||
ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
ms.date: 06/30/2022
|
||||
ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
# Windows Update for Business reports (preview) prerequisites
|
||||
<!--37063317, 30141258, 37063041-->
|
||||
***(Applies to: Windows 11 & Windows 10)***
|
||||
|
||||
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
|
||||
|
||||
- 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)
|
||||
|
||||
## 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 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
|
||||
|
||||
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
|
||||
|
||||
> [!Note]
|
||||
> Device names don't appear in Windows Update for Business reports unless you individually opt-in devices by using policy. The configuration script does this for you, but when using other client configuration methods, set one of the following to display device names:
|
||||
> - CSP: System/[AllowDeviceNameInDiagnosticData](/windows/client-management/mdm/policy-csp-system#system-allowdevicenameindiagnosticdata)
|
||||
> - Group Policy: **Allow device name to be sent in Windows diagnostic data** under **Computer Configuration\Administrative Templates\Windows Components\Data Collection and Preview Builds**
|
||||
|
||||
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
|
||||
|
||||
<!--Using include for endpoint access requirements-->
|
||||
[!INCLUDE [Endpoints for Windows Update for Business reports](./includes/wufb-reports-endpoints.md)]
|
||||
|
||||
> [!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.
|
||||
|
||||
## Log Analytics regions
|
||||
|
||||
Windows Update for Business reports can use a Log Analytics workspace in the following regions:
|
||||
|
||||
|Compatible Log Analytics regions |
|
||||
| ------------------------------- |
|
||||
|Australia Central |
|
||||
|Australia East |
|
||||
|Australia Southeast |
|
||||
|Brazil South |
|
||||
|Canada Central |
|
||||
|Central India |
|
||||
|Central US |
|
||||
|East Asia |
|
||||
|East US |
|
||||
|East US 2 |
|
||||
|Eastus2euap(canary) |
|
||||
|France Central |
|
||||
|Japan East |
|
||||
|Korea Central |
|
||||
|North Central US |
|
||||
|North Europe |
|
||||
|South Africa North |
|
||||
|South Central US |
|
||||
|Southeast Asia |
|
||||
|Switzerland North |
|
||||
|Switzerland West |
|
||||
|UK West |
|
||||
|UK south |
|
||||
|West Central US |
|
||||
|West Europe |
|
||||
|West US |
|
||||
|West US 2 |
|
||||
|
||||
## Next steps
|
||||
|
||||
- [Enable the Windows Update for Business reports solution](wufb-reports-enable.md) in the Azure portal
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Update Compliance Data Schema - UCClient
|
||||
title: Windows Update for Business reports Data Schema - UCClient
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
description: UCClient schema
|
||||
@ -16,9 +16,6 @@ ms.technology: itpro-updates
|
||||
<!--37063317, 30141258, 37063041-->
|
||||
***(Applies to: Windows 11 & Windows 10)***
|
||||
|
||||
> [!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.
|
||||
|
||||
UCClient acts as an individual device's record. It contains data such as the currently installed build, the device's name, the OS edition, and active hours (quantitative).
|
||||
|
||||
|Field |Type |Example |Description |
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Update Compliance Data Schema - UCClientReadinessStatus
|
||||
title: Windows Update for Business reports Data Schema - UCClientReadinessStatus
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
description: UCClientReadinessStatus schema
|
||||
@ -16,9 +16,6 @@ ms.technology: itpro-updates
|
||||
<!--37063317, 30141258, 37063041-->
|
||||
***(Applies to: Windows 10)***
|
||||
|
||||
> [!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.
|
||||
|
||||
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](/windows/whats-new/windows-11-requirements#hardware-requirements) the device doesn't meet.
|
||||
|
||||
|Field |Type |Example |Description |
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Update Compliance Data Schema - UCClientUpdateStatus
|
||||
title: Windows Update for Business reports Data Schema - UCClientUpdateStatus
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
description: UCClientUpdateStatus schema
|
||||
@ -16,9 +16,6 @@ ms.technology: itpro-updates
|
||||
<!--37063317, 30141258, 37063041-->
|
||||
***(Applies to: Windows 11 & Windows 10)***
|
||||
|
||||
> [!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.
|
||||
|
||||
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.
|
||||
|
||||
| Field | Type | Example | Description |
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Update Compliance Data Schema - UCDeviceAlert
|
||||
title: Windows Update for Business reports Data Schema - UCDeviceAlert
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
description: UCDeviceAlert schema
|
||||
@ -16,14 +16,11 @@ ms.technology: itpro-updates
|
||||
<!--37063317, 30141258, 37063041-->
|
||||
***(Applies to: Windows 11 & Windows 10)***
|
||||
|
||||
> [!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.
|
||||
|
||||
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 (ServiceDeviceAlert, ClientDeviceAlert). For example, an EndOfService alert is a ClientDeviceAlert, as a build no longer being serviced (EOS) is a client-wide state. Meanwhile, DeviceRegistrationIssues in the Windows Update for Business deployment service will be a ServiceDeviceAlert, as it's a device-wide state in the service to not be correctly registered.
|
||||
|
||||
|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 |
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Update Compliance Data Schema - UCServiceUpdateStatus
|
||||
title: Windows Update for Business reports Data Schema - UCServiceUpdateStatus
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
description: UCServiceUpdateStatus schema
|
||||
@ -16,10 +16,7 @@ ms.technology: itpro-updates
|
||||
<!--37063317, 30141258, 37063041-->
|
||||
***(Applies to: Windows 11 & Windows 10)***
|
||||
|
||||
> [!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.
|
||||
|
||||
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 |
|
||||
|---|---|---|---|
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Update Compliance Data Schema - UCUpdateAlert
|
||||
title: Windows Update for Business reports Data Schema - UCUpdateAlert
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
description: UCUpdateAlert schema
|
||||
@ -16,9 +16,6 @@ ms.technology: itpro-updates
|
||||
<!--37063317, 30141258, 37063041-->
|
||||
***(Applies to: Windows 11 & Windows 10)***
|
||||
|
||||
> [!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.
|
||||
|
||||
Alert for both client and service updates. 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.
|
||||
|
||||
|Field |Type |Example |Description |
|
||||
35
windows/deployment/update/wufb-reports-schema.md
Normal file
35
windows/deployment/update/wufb-reports-schema.md
Normal file
@ -0,0 +1,35 @@
|
||||
---
|
||||
title: Windows Update for Business reports data schema
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
description: An overview of Windows Update for Business reports data schema
|
||||
ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: reference
|
||||
ms.date: 06/06/2022
|
||||
ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
# Windows Update for Business reports (preview)schema
|
||||
<!--37063317, 30141258, 37063041-->
|
||||
***(Applies to: Windows 11 & Windows 10)***
|
||||
|
||||
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 Windows Update for Business reports 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.
|
||||
|
||||
## Schema
|
||||
|
||||
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.
|
||||
|
||||
|Table |Category |Description |
|
||||
|--|--|--|
|
||||
| [**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**](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**](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**](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**](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**](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. |
|
||||
63
windows/deployment/update/wufb-reports-use.md
Normal file
63
windows/deployment/update/wufb-reports-use.md
Normal file
@ -0,0 +1,63 @@
|
||||
---
|
||||
title: Use the Windows Update for Business reports data
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
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
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
ms.date: 06/06/2022
|
||||
ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
# Use Windows Update for Business reports (preview)
|
||||
<!--37063317, 30141258, 37063041-->
|
||||
***(Applies to: Windows 11 & Windows 10)***
|
||||
|
||||
In this article, you'll learn how to use Windows Update for Business reports to monitor Windows updates for your devices. To configure your environment for use with Windows Update for Business reports, see [Enable Windows Update for Business reports](wufb-reports-enable.md).
|
||||
|
||||
## Display Windows Update for Business reports data
|
||||
|
||||
1. Sign into the [Azure portal](https://portal.azure.com).
|
||||
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 the workspace that you use for Windows Update for Business reports.
|
||||
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. Under **Schemas and filter**, select **Group by: Solution** and then expand the **Log Management** schema. If the **Group by: Category** is selected, the schema is listed under the **Other** category.
|
||||
1. Use the [Windows Update for Business reports 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 Windows Update for Business reports 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
|
||||
UCUpdateAlert
|
||||
| summarize count=count() by AlertClassification, AlertSubtype, ErrorCode, Description
|
||||
```
|
||||
|
||||
:::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":::
|
||||
|
||||
## Data latency
|
||||
|
||||
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 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 |
|
||||
|--|--|--|
|
||||
| UCClient | Once per day |4 hours |
|
||||
| UCClientUpdateStatus|Every update event (Download, install, etc.)|24-36 hours |
|
||||
| UCServiceUpdateStatus| Every update event (Download, install, etc.)|24-36 hours |
|
||||
| UCUpdateAlert | Every event | 24-36 hours |
|
||||
| UCDeviceAlert | Every event | 24-36 hours |
|
||||
| UCClientReadinessStatus | After Windows 11 readiness assessment |24-36 hours |
|
||||
| UCDOStatus | Download Events | 24-36 hours |
|
||||
| UCDOAggregatedStatus | Download Events | 24-36 hours |
|
||||
|
||||
## Working with Azure Monitor Logs
|
||||
|
||||
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 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.
|
||||
@ -1,8 +1,8 @@
|
||||
---
|
||||
title: Use the workbook for Update Compliance (preview)
|
||||
title: Use the workbook for Windows Update for Business reports
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
description: How to use the Update Compliance (preview) workbook.
|
||||
description: How to use the Windows Update for Business reports workbook.
|
||||
ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
@ -12,45 +12,43 @@ ms.date: 10/24/2022
|
||||
ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
# Update Compliance (preview) workbook
|
||||
# Windows Update for Business reports (preview) workbook
|
||||
<!-- MAX6325272, OS33771278 -->
|
||||
***(Applies to: Windows 11 & Windows 10)***
|
||||
|
||||
> [!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).
|
||||
> - 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:
|
||||
[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)
|
||||
- [Feature updates](#feature-updates-tab)
|
||||
- [Delivery Optimization](#bkmk_do)
|
||||
|
||||
:::image type="content" source="media/33771278-update-compliance-workbook-summary.png" alt-text="Screenshot of the summary tab in the Update Compliance workbook with the three tabbed sections outlined in red." lightbox="media/33771278-update-compliance-workbook-summary.png":::
|
||||
:::image type="content" source="media/33771278-wufb-reports-workbook-summary.png" alt-text="Screenshot of the summary tab in the Windows Update for Business reports workbook with the three tabbed sections outlined in red." lightbox="media/33771278-wufb-reports-workbook-summary.png":::
|
||||
|
||||
## Open the Update Compliance workbook
|
||||
## Open the Windows Update for Business reports workbook
|
||||
|
||||
To access the Update Compliance workbook:
|
||||
To access the Windows Update for Business reports workbook:
|
||||
|
||||
1. In the [Azure portal](https://portal.azure.com), select **Monitor** > **Workbooks** from the menu bar.
|
||||
- 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 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 gallery opens, select the **Windows Update for Business reports** 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 Windows Update for Business reports](wufb-reports-enable.md).
|
||||
|
||||
## Summary tab
|
||||
|
||||
The **Summary** tab gives you a brief high-level overview of the devices that you've enrolled into Update Compliance. The **Summary** tab contains tiles above the **Overall security update status** chart.
|
||||
The **Summary** tab gives you a brief high-level overview of the devices that you've enrolled into Windows Update for Business reports. The **Summary** tab contains tiles above the **Overall security update status** chart.
|
||||
|
||||
### Summary tab tiles
|
||||
|
||||
Each of these tiles contains an option to **View details**. When **View details** is selected for a tile, a flyout appears with additional information.
|
||||
|
||||
:::image type="content" source="media/33771278-workbook-summary-tab-tiles.png" alt-text="Screenshot of the summary tab tiles in the Update Compliance workbook":::
|
||||
:::image type="content" source="media/33771278-workbook-summary-tab-tiles.png" alt-text="Screenshot of the summary tab tiles in the Windows Update for Business reports workbook":::
|
||||
|
||||
| Tile name | Description | View details description |
|
||||
|---|---|------|
|
||||
| **Enrolled devices** | Total number of devices that are enrolled into Update Compliance | Displays multiple charts about the operating systems (OS) for enrolled devices: </br> **OS Version** </br> **OS Edition** </br> **OS Servicing Channel** </br> **OS Architecture**|
|
||||
| **Enrolled devices** | Total number of devices that are enrolled into Windows Update for Business reports | Displays multiple charts about the operating systems (OS) for enrolled devices: </br> **OS Version** </br> **OS Edition** </br> **OS Servicing Channel** </br> **OS Architecture**|
|
||||
|**Active alerts** | Total number of active alerts on enrolled devices | Displays the top three active alert subtypes and the count of devices in each. </br> </br> Select the count of **Devices** to display a table of the devices. This table is limited to the first 250 rows. Select `...` to export the full list, or display the query in [Log Analytics](/azure/azure-monitor/logs/log-analytics-tutorial). </br> </br> Select an **AlertSubtype** to display a list containing: </br> - Each **Error Code** in the alert subtype </br>- A **Description** of the error code </br> - A **Recommendation** to help you remediate the error code </br> - A count of **Devices** with the specific error code |
|
||||
| **Windows 11 eligibility** | Percentage of devices that are capable of running Windows 11 | Displays the following items: </br> - **Windows 11 Readiness Status** chart </br> - **Readiness Reason(s) Breakdown** chart that displays Windows 11 requirements that aren't met. </br> - A table for **Readiness reason**. Select a reason to display a list of devices that don't meet a specific requirement for Windows 11. |
|
||||
|
||||
@ -76,7 +74,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
|
||||
|
||||
@ -132,7 +130,7 @@ The **Update status** group for feature updates contains the following items:
|
||||
|**Alerts**| Number of different error codes encountered by devices for the update. | Selecting this number lists the alert name for each error code and a count of devices with the error. Select the device count to display a list of devices that have an active alert for the error code. |
|
||||
| **Total Devices** | Count of devices for each targeted operating system version that have been offered the update, or are installing, have installed, or canceled the feature update.| Selecting the device count opens a device list table. This table is limited to the first 250 rows. Select `...` to export the full list, or display the query in [Log Analytics](/azure/azure-monitor/logs/log-analytics-tutorial). |
|
||||
|
||||
### <a name="bkmk_device-group-feature"></a>Device status group for feature updates
|
||||
### <a name="bkmk_device-group-feature"></a> Device status group for feature updates
|
||||
|
||||
The **Device status** group for feature updates contains the following items:
|
||||
|
||||
@ -141,12 +139,28 @@ The **Device status** group for feature updates contains the following items:
|
||||
- **Device compliance status**: Table containing a list of devices getting a feature update and installation information including active alerts for the devices.
|
||||
- This table is limited to the first 250 rows. Select `...` to export the full list, or display the query in [Log Analytics](/azure/azure-monitor/logs/log-analytics-tutorial).
|
||||
|
||||
## <a name="bkmk_do"></a> Delivery Optimization (preview tab)
|
||||
|
||||
The **Delivery Optimization** tab provides a summarized view of bandwidth efficiencies. This new revised report also includes Microsoft Connected Cache (MCC) information.
|
||||
|
||||
At the top of the report, tiles display the following information:
|
||||
|
||||
- Total bandwidth savings percentage
|
||||
- The percentage of the saved bandwidth broken down by peer-to-peer and MCC
|
||||
- Device counts showing percentages of bytes delivered between peer-to-peer and MCC
|
||||
- The breakdown of total downloaded GBs.
|
||||
|
||||
The Delivery Optimization tab is further divided into the following groups:
|
||||
|
||||
- **Device Configuration**: A chart differentiating the number of devices with and without peer-to-peer. And, a table of Download Mode configuration breakdown between numbers of devices. When selected, the devices within that group can be viewed, filtered in a separate table.
|
||||
- **Content Distribution**: Includes charts showing percentage volumes and GB volumes by source by content types. All content types are linked to a table for deeper filtering by **ContentType**, **AzureADTenantId**, and **GroupID**.
|
||||
- **Efficiency By Group**: This view provides filters commonly used ways of grouping devices. The provided filters include: **GroupID**, **City**, **Country**, and **ISP**.
|
||||
|
||||
## Customize the workbook
|
||||
|
||||
Since the Update Compliance workbook is an [Azure Workbook template](/azure/azure-monitor/visualize/workbooks-templates), it can be customized to suit your needs. If you open a template, make some adjustments, and save it, the template is saved as a workbook. This workbook appears in green. The original template is left untouched. For more information about workbooks, see [Get started with Azure Workbooks](/azure/azure-monitor/visualize/workbooks-getting-started).
|
||||
|
||||
Since the Windows Update for Business reports workbook is an [Azure Workbook template](/azure/azure-monitor/visualize/workbooks-templates), it can be customized to suit your needs. If you open a template, make some adjustments, and save it, the template is saved as a workbook. This workbook appears in green. The original template is left untouched. For more information about workbooks, see [Get started with Azure Workbooks](/azure/azure-monitor/visualize/workbooks-getting-started).
|
||||
|
||||
## Next steps
|
||||
|
||||
- Explore the [Update Compliance (preview) schema](update-compliance-v2-schema.md)
|
||||
- Review [Feedback, support, and troubleshooting](update-compliance-v2-help.md) information for Update Compliance
|
||||
- Explore the [Windows Update for Business reports schema](wufb-reports-schema.md)
|
||||
- Review [Feedback, support, and troubleshooting](wufb-reports-help.md) information for Windows Update for Business reports
|
||||
Loading…
x
Reference in New Issue
Block a user