Merge pull request #879 from MicrosoftDocs/UpComDOfix

Up com d ofix
This commit is contained in:
Jaime Ondrusek
2019-08-09 15:39:03 -07:00
committed by GitHub

View File

@ -7,8 +7,9 @@ ms.prod: w10
ms.mktglfcycl: deploy ms.mktglfcycl: deploy
ms.sitesec: library ms.sitesec: library
ms.pagetype: deploy ms.pagetype: deploy
audience: itpro audience: itpro
author: greg-lindsay author: jaimeo
ms.author: jaimeo
keywords: oms, operations management suite, optimization, downloads, updates, log analytics keywords: oms, operations management suite, optimization, downloads, updates, log analytics
ms.localizationpriority: medium ms.localizationpriority: medium
ms.collection: M365-analytics ms.collection: M365-analytics
@ -21,11 +22,9 @@ The Update Compliance solution of Windows Analytics provides you with informatio
![DO status](images/UC_workspace_DO_status.png) ![DO status](images/UC_workspace_DO_status.png)
> [!IMPORTANT] > [!IMPORTANT]
> [!IMPORTANT] > There is a known issue with the way device configuration is displayed for Delivery Optimization. Some devices running Windows 10, versions 1809 or 1903 report the Delivery Optimization DownloadMode configuration value as the sequential value in the list of possible configurations rather than the actual configured value. For example, a device that is configured as HTTP + Group (2), will be shown as HTTP + Internet (3) in Update Compliance.
> There are currently two known issues affecting the Delivery Optimization status displayed in these blades:
>- Devices running Windows 10, version 1803 or older versions are not sending the correct configuration profile. As a result, the information in the Device Configuration blade might not accurately reflect the settings in your environment.
> >
> >**This issue is now fixed by installing the 2019-07 cumulative update appropriate for the device.**
## Delivery Optimization Status ## Delivery Optimization Status