mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
meta3upd
This commit is contained in:
parent
fd97b93d62
commit
f9563b2851
@ -9,7 +9,6 @@ author: mestew
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: article
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
|
@ -18,7 +18,7 @@ ms.date: 06/06/2022
|
||||
<!--37063317, 30141258, 37063041-->
|
||||
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.
|
||||
|
||||
# Schema for UCDeviceAlert
|
||||
## Schema for UCDeviceAlert
|
||||
|
||||
|Field |Type |Example |Description |
|
||||
|---|---|---|---|
|
||||
|
@ -20,7 +20,7 @@ ms.date: 11/17/2022
|
||||
|
||||
UCDOAggregatedStatus is an aggregation of all individual UDDOStatus records across the tenant and summarizes bandwidth savings across all devices enrolled using [Delivery Optimization and Microsoft Connected Cache](/windows/deployment/do).
|
||||
|
||||
# Schema for UCDOAggregatedStatus
|
||||
## Schema for UCDOAggregatedStatus
|
||||
|
||||
|Field |Type |Example |Description |
|
||||
|---|---|---|---|
|
||||
|
Loading…
x
Reference in New Issue
Block a user