mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 02:13:43 +00:00
incorp of feedback from Narkis
This commit is contained in:
@ -5,9 +5,9 @@ keywords: oms, operations management suite, wdav, updates, downloads, log analyt
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: greg-lindsay
|
||||
author: jaimeo
|
||||
ms.localizationpriority: medium
|
||||
ms.author: greglin
|
||||
ms.author: jaimeo
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: article
|
||||
---
|
||||
@ -59,6 +59,8 @@ In MDM, the same settings are under **.Vendor/MSFT/Policy/Config/DeliveryOptimiz
|
||||
| [Select the source of Group IDs](#select-the-source-of-group-ids) | DOGroupIDSource | 1803 |
|
||||
| [Delay background download from http (in secs)](#delay-background-download-from-http-in-secs) | DODelayBackgroundDownloadFromHttp | 1803 |
|
||||
| [Delay foreground download from http (in secs)](#delay-foreground-download-from-http-in-secs) | DODelayForegroundDownloadFromHttp | 1803 |
|
||||
| [Delay foreground download cache server fallback (in secs)](#delay-foreground-download-cache-server-fallback-in-secs) | DelayCacheServerFallbackForeground | 1903 |
|
||||
| [Delay background download cache server fallback (in secs)](#delay-background-download-cache-server-fallback-in-secs) | DelayCacheServerFallbackBackground | 1903 |
|
||||
|
||||
### More detail on Delivery Optimization settings:
|
||||
|
||||
@ -198,6 +200,12 @@ Starting in Windows 10, version 1803, this allows you to delay the use of an HTT
|
||||
### Delay foreground download from http (in secs)
|
||||
Starting in Windows 10, version 1803, allows you to delay the use of an HTTP source in a foreground (interactive) download that is allowed to use peer-to-peer.
|
||||
|
||||
### Delay Foreground Download Cache Server Fallback (in secs)
|
||||
Starting in Windows 10, version 1903, allows you to delay the fallback from cache server to the HTTP source for foreground content download by X seconds. If you set the policy to delay foreground download from http, it will apply first (to allow downloads from peers first).
|
||||
|
||||
### Delay Background Download Cache Server Fallback (in secs)
|
||||
Starting in Windows 10, version 1903, set this policy to delay the fallback from cache server to the HTTP source for a background content download by X seconds. If you set the policy to delay background download from http, it will apply first (to allow downloads from peers first).
|
||||
|
||||
### Minimum Background QoS
|
||||
|
||||
This value specifies the minimum download speed guarantee that a client attempts to achieve and will fulfill by downloading more kilobytes from Windows Update servers or WSUS. Simply put, the lower this value is, the more content will be sourced using peers on the network rather than Windows Update. The higher this value, the more content is received from Windows Update servers or WSUS, versus peers on the local network.
|
||||
@ -221,3 +229,5 @@ The device can download from peers while on battery regardless of this policy.
|
||||
|
||||
>[!IMPORTANT]
|
||||
> By default, devices **will not upload while on battery**. To enable uploads while on battery, you need to enable this policy and set the battery value under which uploads pause.
|
||||
|
||||
|
||||
|
@ -97,8 +97,11 @@ To do this with MDM, go to **.Vendor/MSFT/Policy/Config/DeliveryOptimization/**
|
||||
## Monitor Delivery Optimization
|
||||
[//]: # (How to tell if it’s working? What values are reasonable; which are not? If not, which way to adjust and how? -- check PercentPeerCaching for files > minimum >= 50%)
|
||||
|
||||
### Windows PowerShell cmdlets for analyzing usage
|
||||
**Starting in Windows 10, version 1703**, you can use two new PowerShell cmdlets to check the performance of Delivery Optimization:
|
||||
### Windows PowerShell cmdlets
|
||||
|
||||
**Starting in Windows 10, version 1703**, you can use new PowerShell cmdlets to check the performance of Delivery Optimization.
|
||||
|
||||
#### Analyze usage
|
||||
|
||||
`Get-DeliveryOptimizationStatus` returns a real-time snapshot of all current Delivery Optimization jobs.
|
||||
|
||||
@ -117,11 +120,6 @@ To do this with MDM, go to **.Vendor/MSFT/Policy/Config/DeliveryOptimization/**
|
||||
| PredefinedCallerApplication | Indicates the last caller that initiated a request for the file. |
|
||||
| ExpireOn | The target expiration date and time for the file. |
|
||||
| Pinned | A yes/no value indicating whether an item has been "pinned" in the cache (see `setDeliveryOptmizationStatus`). |
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
`Get-DeliveryOptimizationPerfSnap` returns a list of key performance data:
|
||||
|
||||
@ -136,9 +134,14 @@ To do this with MDM, go to **.Vendor/MSFT/Policy/Config/DeliveryOptimization/**
|
||||
Using the `-Verbose` option returns additional information:
|
||||
|
||||
- Bytes from peers (per type)
|
||||
- Bytes from CDN (the number of bytes received over HTTP)
|
||||
- Bytes from CDN (the number of bytes received over HTTP)
|
||||
- Average number of peer connections per download
|
||||
|
||||
Starting in Window 10, version 1903, `get-DeliveryOptimizationPerfSnap` has a new option `-CacheSummary` which provides a summary of the cache status.
|
||||
|
||||
Starting in Windows 10, version 1803, `Get-DeliveryOptimizationPerfSnapThisMonth` returns data similar to that from `Get-DeliveryOptimizationPerfSnap` but limited to the current calendar month.
|
||||
|
||||
#### Manage the Delivery Optimization cache
|
||||
|
||||
**Starting in Windows 10, version 1903:**
|
||||
|
||||
@ -158,9 +161,8 @@ You can now "pin" files to keep them persistent in the cache. You can only do th
|
||||
- `-IncludePinnedFiles` deletes all files that are pinned.
|
||||
- `-Force` deletes the cache with no prompts.
|
||||
|
||||
`get-DeliveryOptimizationPerfSnap` has a new option `-CacheSummary` which provides a summary of the cache status.
|
||||
|
||||
|
||||
#### Work with Delivery Optimization logs
|
||||
|
||||
**Starting in Windows 10, version 1803:**
|
||||
|
||||
@ -172,9 +174,7 @@ Log entries are written to the PowerShell pipeline as objects. To dump logs to a
|
||||
|
||||
[//]: # (section on what to look for in logs, list of peers, connection failures)
|
||||
|
||||
`Get-DeliveryOptimizationPerfSnapThisMonth`
|
||||
|
||||
Returns data similar to that from `Get-DeliveryOptimizationPerfSnap` but limited to the current calendar month.
|
||||
|
||||
[//]: # (possibly move to Troubleshooting)
|
||||
|
||||
|
@ -114,8 +114,8 @@ For the payloads (optional):
|
||||
|
||||
**Does Delivery Optimization use multicast?**: No. It relies on the cloud service for peer discovery, resulting in a list of peers and their IP addresses. Client devices then connect to their peers to obtain download files over TCP/IP.
|
||||
|
||||
**What data does Delivery Optimization send to its service?**
|
||||
{you've got that big table at the OSGwiki--do you want all that to be published?}
|
||||
**How does Delivery Optimization deal with congestion on the router from peer-to-peer activity on the LAN?**: Starting in Windows 10, version 1903, Delivery Optimizatio uses LEDBAT to relieve such congestion. For more details see this post on the [Networking Blog](https://techcommunity.microsoft.com/t5/Networking-Blog/Windows-Transport-converges-on-two-Congestion-Providers-Cubic/ba-p/339819).
|
||||
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
|
Reference in New Issue
Block a user