mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 02:13:43 +00:00
more additions and cross-linking
This commit is contained in:
jaimeo
@ -23,7 +23,7 @@ ms.topic: article
|
||||
|
||||
> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
|
||||
|
||||
There are a great many details you can set in Delivery Optimization to customize it to do just what you need it to. This topic summarizes them for your reference.
|
||||
There are a great many details you can set in Delivery Optimization to customize it to do just what you need it to. This topic summarizes them for your reference. If you just need an overview of Delivery Optimization, see [Delivery Optimization for Windows 10 updates](waas-delivery-optimization.md). If you need information about setting up Delivery Optimization, including tips for the best settings in different scenarios, see [Set up Delivery Optimization for Windows 10 updates](waas-delivery-optimization-setup.md).
|
||||
|
||||
## Delivery Optimization options
|
||||
|
||||
@ -64,6 +64,10 @@ In MDM, the same settings are under **.Vendor/MSFT/Policy/Config/DeliveryOptimiz
|
||||
| [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 |
|
||||
| [Cache Server Hostname](#cache-server-hostname) | DOCacheHost | 2004 |
|
||||
| [Cache Server Hostname Source](#cache-server-hostname-source) | DOCacheHostSource | 2004 |
|
||||
| [Maximum Foreground Download Bandwidth (in KB/s)](#maximum-background-download-bandwidth-in-kbs) | DOMaxForegroundDownloadBandwidth | 2004 |
|
||||
| [Maximum Background Download Bandwidth (in KB/s)](#maximum-background-download-bandwidth-in-kbs) | DOMaxBackgroundDownloadBandwidth | 2004 |
|
||||
|
||||
### More detail on Delivery Optimization settings:
|
||||
|
||||
@ -232,4 +236,33 @@ 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.
|
||||
|
||||
### Cache Server Hostname
|
||||
|
||||
Set this policy to to designate one or more Microsoft Connected Cache servers to be used by Delivery Optimization. You can set one or more FQDNs or IP Addresses that are comma separated, for example: myhost.somerandomhost.com,myhost2.somrandomhost.com,10.10.1.7.
|
||||
|
||||
|
||||
### Cache Server Hostname Source
|
||||
|
||||
This policy allows you to specify how your client(s) can discover Delivery Optimization in Network Cache servers dynamically. There are two options:
|
||||
- 1 = DHCP Option 235.
|
||||
- 2 = DHCP Option 235 Force.
|
||||
|
||||
with either option, the client will query DHCP Option ID 235 and use the returned value as the Cache Server Hostname. Option 2 overrides the Cache Server Hostname policy, if set.
|
||||
|
||||
Set this policy to designate one or more Delivery Optimization in Network Cache servers through a custom DHCP Option. You can add one or more value either fully qualified domain names (FQDN) or IP addresses. To add multiple values, separate each FQDN or IP address by commas.
|
||||
|
||||
> [!NOTE]
|
||||
> If you format the DHCP Option ID incorrectly, the client will fall back to the Cache Server Hostname policy value if that value has been set.
|
||||
|
||||
### Maximum Foreground Download Bandwidth (in KB/s)
|
||||
|
||||
Specifies the maximum foreground download bandwidth in kilobytes/second that the device can use across all concurrent download activities using Delivery Optimization.
|
||||
|
||||
The default value of 0 (zero) means that Delivery Optimization dynamically adjusts to use the available bandwidth for downloads.
|
||||
|
||||
|
||||
### Maximum Background Download Bandwidth (in KB/s)
|
||||
|
||||
Specifies the maximum background download bandwidth in kilobytes/second that the device can use across all concurrent download activities using Delivery Optimization.
|
||||
|
||||
The default value 0 (zero) means that Delivery Optimization dynamically adjusts to use the available bandwidth for downloads.
|
||||
|
||||
@ -24,7 +24,7 @@ ms.topic: article
|
||||
|
||||
## Recommended Delivery Optimization settings
|
||||
|
||||
Delivery Optimization offers a great many settings to fine-tune its behavior (see [Delivery Optimization reference](waas-delivery-optimization-reference.md) for a comprehensive list), but for the most efficient performance, there are just a few key parameters that will have the greatest impact if particular situations exist in your deployment:
|
||||
Delivery Optimization offers a great many settings to fine-tune its behavior (see [Delivery Optimization reference](waas-delivery-optimization-reference.md) for a comprehensive list), but for the most efficient performance, there are just a few key parameters that will have the greatest impact if particular situations exist in your deployment. If you just need an overview of Delivery Optimization, see [Delivery Optimization for Windows 10 updates](waas-delivery-optimization.md).
|
||||
|
||||
- Does your topology include multiple breakouts to the internet (i.e., a "hybrid WAN") or are there only a few connections to the internet, so that all requests appear to come from a single external IP address (a "hub and spoke" topology)?
|
||||
- If you use boundary groups in your topology, how many devices are present in a given group?
|
||||
@ -129,7 +129,6 @@ To do this with MDM, go to **.Vendor/MSFT/Policy/Config/DeliveryOptimization/**
|
||||
| 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`). |
|
||||
|
||||
Starting in Windows 10, version 2004, `Get-DeliveryOptimizationStatus` has a new option `-PeerInfo` which returns a real-time list of the connected peers.
|
||||
|
||||
`Get-DeliveryOptimizationPerfSnap` returns a list of key performance data:
|
||||
|
||||
@ -147,7 +146,7 @@ Using the `-Verbose` option returns additional information:
|
||||
- Bytes from CDN (the number of bytes received over HTTP)
|
||||
- Average number of peer connections per download
|
||||
|
||||
Starting in Windows 10, version 2004, `Get-DeliveryOptimizationPerfSnap` has a new option `-PeerInfo` which returns a real-time list of the connected peers.
|
||||
**Starting in Windows 10, version 2004**, `Get-DeliveryOptimizationPerfSnap` has a new option `-PeerInfo` which returns a real-time list of the connected peers.
|
||||
|
||||
Starting in Windows 10, version 1903, `get-DeliveryOptimizationPerfSnap` has a new option `-CacheSummary` which provides a summary of the cache status.
|
||||
|
||||
@ -178,7 +177,10 @@ You can now "pin" files to keep them persistent in the cache. You can only do th
|
||||
|
||||
**Starting in Windows 10, version 2004:**
|
||||
|
||||
`Get-DeliveryOptimizationLogAnalysis [ETL Logfile path] [-ListConnections]`
|
||||
- `Enable-DeliveryOptimizationVerboseLogs`
|
||||
- `Disable-DliveryOptimizationVerboseLogs`
|
||||
|
||||
- `Get-DeliveryOptimizationLogAnalysis [ETL Logfile path] [-ListConnections]`
|
||||
|
||||
With no options, this cmdlet returns these data:
|
||||
|
||||
|
||||
@ -39,6 +39,20 @@ Delivery Optimization is a cloud-managed solution. Access to the Delivery Optimi
|
||||
|
||||
|
||||
- Activity Monitor now identifies the cache server used for as the source for Microsoft Connected Cache. For more information about using Microsoft Connected Cache with Configuration Manager, see [Microsoft Connected Cache](https://docs.microsoft.com/mem/configmgr/core/plan-design/hierarchy/fundamental-concepts-for-content-management#microsoft-connected-cache).
|
||||
- New options for [`Get-DeliveryOptimizationPerfSnap`](waas-delivery-optimization-setup.md#analyze-usage).
|
||||
- New cmdlets:
|
||||
- `Enable-DeliveryOptimizationVerboseLogs`
|
||||
- `Disable-DliveryOptimizationVerboseLogs`
|
||||
- `Get-DeliveryOptimizationLogAnalysis [ETL Logfile path] [-ListConnections]`
|
||||
- New policy settings (for details see ):
|
||||
- [DOCacheHost](waas-delivery-optimization-reference.md#cache-server-hostname)
|
||||
- [DOCacheHostSource](waas-delivery-optimization-reference.md#cache-server-hostname-source)
|
||||
- [DOMaxForegroundDownloadBandwidth](waas-delivery-optimization-reference.md#maximum-foreground-download-bandwidth-in-kbs)
|
||||
- [DOMaxBackgroundDownloadBandwidth](waas-delivery-optimization-reference.md#maximum-foreground-download-bandwidth-in-kbs)
|
||||
- Support for new types of downloads:
|
||||
- Office installations and updates
|
||||
- Xbox game pass games
|
||||
- MSIX apps (HTTP downloads only)
|
||||
|
||||
|
||||
## Requirements
|
||||
|
||||
Reference in New Issue
Block a user