mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
ucv2-tp
This commit is contained in:
parent
7d25e3de64
commit
bd424f6600
@ -199,6 +199,10 @@
|
|||||||
href: update/update-compliance-configuration-manual.md
|
href: update/update-compliance-configuration-manual.md
|
||||||
- name: Configure clients with Microsoft Endpoint Manager
|
- name: Configure clients with Microsoft Endpoint Manager
|
||||||
href: update/update-compliance-configuration-mem.md
|
href: update/update-compliance-configuration-mem.md
|
||||||
|
- name: Use Update Compliance (preview)
|
||||||
|
items:
|
||||||
|
- name: Use Update Compliance
|
||||||
|
href: update/update-compliance-v2-use.md
|
||||||
- name: Software updates in the Microsoft admin center (preview)
|
- name: Software updates in the Microsoft admin center (preview)
|
||||||
href: update/update-status-admin-center.md
|
href: update/update-status-admin-center.md
|
||||||
- name: Schema reference (preview)
|
- name: Schema reference (preview)
|
||||||
|
@ -1,8 +1,8 @@
|
|||||||
---
|
---
|
||||||
title: Use the Update Compliance solution
|
title: Use the Update Compliance (preview) solution
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
manager: dougeby
|
manager: dougeby
|
||||||
description: How to use the Update Compliance solution.
|
description: How to use the Update Compliance (preview) solution.
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: deploy
|
ms.mktglfcycl: deploy
|
||||||
ms.pagetype: deploy
|
ms.pagetype: deploy
|
||||||
@ -14,7 +14,44 @@ ms.topic: article
|
|||||||
date: 05/07/2022
|
date: 05/07/2022
|
||||||
---
|
---
|
||||||
|
|
||||||
# Use Update Compliance
|
# Use Update Compliance (preview)
|
||||||
|
|
||||||
> [!Important]
|
> [!Important]
|
||||||
> This information relates to a preview feature that's available for early testing and use in a production environment. This feature is fully supported but it's still in active development and may receive substantial changes until it becomes generally available.
|
> This information relates to a preview feature that's available for early testing and use in a production environment. This feature is fully supported but it's still in active development and may receive substantial changes until it becomes generally available.
|
||||||
|
|
||||||
|
In this article you'll learn how to use Update Compliance to monitor Windows updates for your devices. To configure your environment for use with Update Compliance, see [Enable Update Compliance](update-compliance-v2-enable.md).
|
||||||
|
|
||||||
|
## 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 **Log** under the **General** group in your workspace.
|
||||||
|
1.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## 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 devices part of your organization 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 re-ingested 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.
|
||||||
|
|
||||||
|
| Data Type | Data upload rate from device | Data Latency |
|
||||||
|
|--|--|--|
|
||||||
|
|WaaSUpdateStatus | Once per day |4 hours |
|
||||||
|
|WaaSInsiderStatus| Once per day |4 hours |
|
||||||
|
|WaaSDeploymentStatus|Every update event (Download, install, etc.)|24-36 hours |
|
||||||
|
|WUDOAggregatedStatus|On update event, aggregated over time|24-36 hours |
|
||||||
|
|WUDOStatus|Once per day|12 hours |
|
||||||
|
|
||||||
|
This means you should generally expect to see new data device data every 24 hours, except for WaaSDeploymentStatus and WUDOAggregatedStatus, which may take 36-48 hours.
|
||||||
|
|
||||||
|
## Using Log Analytics
|
||||||
|
|
||||||
|
Update Compliance is built on the Log Analytics platform that is integrated into Operations Management Suite. All data in the workspace is the direct result of a query. Understanding the tools and features at your disposal, all integrated within Azure Portal, can deeply enhance your experience and complement Update Compliance.
|
||||||
|
|
||||||
|
See below for a few topics related to Log Analytics:
|
||||||
|
* Learn how to effectively execute custom Log Searches by referring to Microsoft Azure's excellent documentation on [querying data in Log Analytics](/azure/log-analytics/log-analytics-log-searches).
|
||||||
|
* To develop your own custom data views in Operations Management Suite or [Power BI](https://powerbi.microsoft.com/); check out documentation on [analyzing data for use in Log Analytics](/azure/log-analytics/log-analytics-dashboards).
|
||||||
|
* [Gain an overview of Log Analytics' alerts](/azure/log-analytics/log-analytics-alerts) and learn how to use it to always stay informed about the most critical issues you care about.
|
Loading…
x
Reference in New Issue
Block a user