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

tweaks

Browse Source
This commit is contained in:
Meghan Stewart 2022-06-02 22:59:19 -07:00
parent 509de562ec
commit 3b2aec6f32
7 changed files with 0 additions and 35 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
windows/deployment/update/update-compliance-v2-schema-ucclient.md
View File

@ -60,8 +60,3 @@ UCClient acts as an individual device's record. It contains data such as the cur
| **WUQualityDeferralDays** | [int](/azure/kusto/query/scalar-data-types/int) | `-1` | CSP: DeferQualityUpdates. The Windows Update quality update deferral configuration in days. -1 indicates not configured, 0 indicates configured but set to 0. Values greater than 0 indicate the policy setting. |
| **WUQualityGracePeriodDays** | [int](/azure/kusto/query/scalar-data-types/int) | `0` | The Windows Update grace period for quality update in days. -1 indicates not configured, 0 indicates configured and set to 0. Values greater than 0 indicate the grace period in days. |
| **WUQualityPauseState** | [string](/azure/kusto/query/scalar-data-types/string) | `NotConfigured` | Indicates pause status of device for quality updates, possible values are Paused, NotPaused, NotConfigured. |
## Next steps
- [Update Compliance overview](update-compliance-v2-overview.md)
- [Use Update Compliance](update-compliance-v2-use.md)

5
windows/deployment/update/update-compliance-v2-schema-ucclientreadinessstatus.md
View File

@ -45,8 +45,3 @@ UCClientReadinessStatus is an individual device's record about its readiness for
| **SetupReadinessTime** | [datetime](/azure/kusto/query/scalar-data-types/datetime) | `2020-05-14 09:26:03.478039` | The date and time when readiness was assessed by setup and the assessment was sent.|
| **SetupReadinessExpiryTime** | [datetime](/azure/kusto/query/scalar-data-types/datetime) | `2020-05-14 09:26:03.478039` | The date and time when the setup readiness assessment will expire.|
| **TimeGenerated** | [datetime](/azure/kusto/query/scalar-data-types/datetime) | `2020-05-14 10:26:03.478039` | The date and time when Azure Monitor Logs ingested this record for your Log Analytics workspace.|
## Next steps
- [Update Compliance overview](update-compliance-v2-overview.md)
- [Use Update Compliance](update-compliance-v2-use.md)

5
windows/deployment/update/update-compliance-v2-schema-ucclientupdatestatus.md
View File

@ -52,8 +52,3 @@ Update Event that combines the latest client-based data with the latest service-
| **UpdateInstalledTime** | [datetime](/azure/kusto/query/scalar-data-types/datetime) | `2020-05-14 09:26:03.478039` | DateTime when event transitioned to UpdateInstalled, else empty. |
| **UpdateReleaseTime** | [datetime](/azure/kusto/query/scalar-data-types/datetime) | `2020-05-14 09:26:03.478039` | The release date of the update |
| **UpdateSource** | [string](/azure/kusto/query/scalar-data-types/string) | `UUP` | The source of the update such as UUP, MUv6, Media |
## Next steps
- [Update Compliance overview](update-compliance-v2-overview.md)
- [Use Update Compliance](update-compliance-v2-use.md)

5
windows/deployment/update/update-compliance-v2-schema-ucdevicealert.md
View File

@ -51,8 +51,3 @@ These alerts are activated as a result of an issue that is device-specific. It i
| **Type** | [string](/azure/kusto/query/scalar-data-types/string) | `UpdateAlert` | The entity type. |
| **UpdateCategory** | [string](/azure/kusto/query/scalar-data-types/string) | `WindowsFeatureUpdate` | The type of content this DeviceUpdateEvent is tracking. |
| **UpdateClassification** | [string](/azure/kusto/query/scalar-data-types/string) | `Upgrade` | Whether this content is an upgrade (feature update), security (quality update), non-security (quality update) |
## Next steps
- [Update Compliance overview](update-compliance-v2-overview.md)
- [Use Update Compliance](update-compliance-v2-use.md)

5
windows/deployment/update/update-compliance-v2-schema-ucserviceupdatestatus.md
View File

@ -39,8 +39,3 @@ Update Event that comes directly from the service-side. The event has only servi
| **Type** | [string](/azure/kusto/query/scalar-data-types/string) | `ServiceUpdateEvent` | The EntityType |
| **UpdateCategory** | [string](/azure/kusto/query/scalar-data-types/string) | `WindowsFeatureUpdate` | The type of content this DeviceUpdateEvent is tracking. |
| **UpdateClassification** | [string](/azure/kusto/query/scalar-data-types/string) | `Upgrade` | Whether this update is an upgrade (feature update), security (quality update), non-security (quality update) |
## Next steps
- [Update Compliance overview](update-compliance-v2-overview.md)
- [Use Update Compliance](update-compliance-v2-use.md)

5
windows/deployment/update/update-compliance-v2-schema-ucupdatealert.md
View File

@ -54,8 +54,3 @@ Alert for both client and service updates. Contains information that needs atten
| **UpdateCategory** | [string](/azure/kusto/query/scalar-data-types/string) | `WindowsFeatureUpdate` | The type of content this DeviceUpdateEvent is tracking. |
| **UpdateClassification** | [string](/azure/kusto/query/scalar-data-types/string) | `Upgrade` | Whether this update is an upgrade (feature update), security (quality update), non-security (quality update) |
| **URL** | [string](/azure/kusto/query/scalar-data-types/string) | `aka.ms/errordetail32152` | An optional URL to get more in-depth information related to this alert. |
## Next steps
- [Update Compliance overview](update-compliance-v2-overview.md)
- [Use Update Compliance](update-compliance-v2-use.md)

5
windows/deployment/update/update-compliance-v2-schema.md
View File

@ -38,8 +38,3 @@ The table below summarizes the different tables that are part of the Update Comp
| [**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. For example, an EndOfService alert is a ClientDeviceAlert, since a build that's no longer being serviced is a client-wide state. Meanwhile, DeviceRegistrationIssues in 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. |
| [**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. |
## Next steps
- [Update Compliance overview](update-compliance-v2-overview.md)
- [Use Update Compliance](update-compliance-v2-use.md)