mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
formatting and wording tweaks
This commit is contained in:
parent
02ac07db32
commit
7b15ee888d
@ -16,17 +16,19 @@ 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 11</a>
|
||||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||||
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-delivery-optimization target=_blank>Delivery Optimization</a>
|
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-delivery-optimization target=_blank>Delivery Optimization</a>
|
||||||
ms.date: 07/01/2024
|
ms.date: 07/23/2024
|
||||||
---
|
---
|
||||||
|
|
||||||
# Configure Delivery Optimization (DO) for Windows
|
# Configure Delivery Optimization (DO) for Windows
|
||||||
|
|
||||||
|
This article describes the different configuration considerations to optimize Delivery Optimization (DO) in your environment.
|
||||||
|
|
||||||
## Delivery Optimization set up considerations
|
## Delivery Optimization set up considerations
|
||||||
|
|
||||||
Use this checklist to guide you through different aspects when modifying Delivery Optimization configurations for your environment.
|
Use this checklist to guide you through different aspects when modifying Delivery Optimization configurations for your environment.
|
||||||
|
|
||||||
1. Pre-requisites to allow Delivery Optimization communication
|
1. Prerequisites to allow Delivery Optimization communication
|
||||||
1. Evaluate Delivery Optimization policies based on the following:
|
1. Evaluate Delivery Optimization policies based on the follwoing items:
|
||||||
|
|
||||||
* Network topology
|
* Network topology
|
||||||
* Organization size
|
* Organization size
|
||||||
@ -36,7 +38,7 @@ Use this checklist to guide you through different aspects when modifying Deliver
|
|||||||
1. Using Connected Cache (MCC)
|
1. Using Connected Cache (MCC)
|
||||||
1. Choose where to set Delivery Optimization policies
|
1. Choose where to set Delivery Optimization policies
|
||||||
|
|
||||||
## 1. Pre-requisites to allow Delivery Optimization communication
|
## 1. Prerequisites to allow Delivery Optimization communication
|
||||||
|
|
||||||
:::image type="content" source="images/do-setup-allow-communication.png" alt-text="Screenshot of the considerations to allow Delivery Optimization communication." lightbox="images/do-setup-allow-communication.png":::
|
:::image type="content" source="images/do-setup-allow-communication.png" alt-text="Screenshot of the considerations to allow Delivery Optimization communication." lightbox="images/do-setup-allow-communication.png":::
|
||||||
|
|
||||||
@ -50,11 +52,11 @@ There are service endpoints that you need to permit through your Firewall to com
|
|||||||
|
|
||||||
### Proxy
|
### Proxy
|
||||||
|
|
||||||
To allow peer-to-peer (P2P) to work properly you need to allow direct calls to the Delivery Optimization service from your devices. When using a proxy, you want to bypass calls from the Delivery Optimization service (*.prod.do.dsp.mp.microsoft.com).
|
To allow peer-to-peer (P2P) to work properly, you need to allow direct calls to the Delivery Optimization service from your devices. When using a proxy, you want to bypass calls from the Delivery Optimization service (*.prod.do.dsp.mp.microsoft.com).
|
||||||
|
|
||||||
#### Local proxy
|
#### Local proxy
|
||||||
|
|
||||||
For downloads from HTTP sources, Delivery Optimization can use the automatic proxy discovery capability of WinHttp to handle communication with the proxy server. It’s important to know, Delivery Optimization uses byte range requests, so you’ll want to make sure your proxy allows this capability. [Learn more](delivery-optimization-proxy.md) about using Delivery Optimization with a proxy server.
|
For downloads from HTTP sources, Delivery Optimization can use the automatic proxy discovery capability of WinHttp to handle communication with the proxy server. It's important to know that Delivery Optimization uses byte range requests, so you'll want to make sure your proxy allows this capability. [Learn more](delivery-optimization-proxy.md) about using Delivery Optimization with a proxy server.
|
||||||
|
|
||||||
#### Cloud proxy
|
#### Cloud proxy
|
||||||
|
|
||||||
@ -78,7 +80,7 @@ There are a range of [Delivery Optimization settings](waas-delivery-optimization
|
|||||||
|
|
||||||
:::image type="content" source="images/do-setup-network-topology.png" alt-text="Screenshot of Delivery Optimization network topology considerations." lightbox="images/do-setup-network-topology.png":::
|
:::image type="content" source="images/do-setup-network-topology.png" alt-text="Screenshot of Delivery Optimization network topology considerations." lightbox="images/do-setup-network-topology.png":::
|
||||||
|
|
||||||
Peer groups can be defined in Delivery Optimization using a combination of settings such as [DODownloadMode](waas-delivery-optimization-reference.md#download-mode), [DOGroupID](waas-delivery-optimization-reference.md#group-id), [DOGroupIDSource](waas-delivery-optimization-reference.md#select-the-source-of-group-ids), and [DORestrictPeerSelection](waas-delivery-optimization-reference.md#select-a-method-to-restrict-peer-selection). *The combination of settings used will depend on your desired peer group(s) and your network topology.*
|
Peer groups can be defined in Delivery Optimization using a combination of settings such as [DODownloadMode](waas-delivery-optimization-reference.md#download-mode), [DOGroupID](waas-delivery-optimization-reference.md#group-id), [DOGroupIDSource](waas-delivery-optimization-reference.md#select-the-source-of-group-ids), and [DORestrictPeerSelection](waas-delivery-optimization-reference.md#select-a-method-to-restrict-peer-selection). *The combination of settings used depends on your desired peer group(s) and your network topology.*
|
||||||
|
|
||||||
#### Peering setup
|
#### Peering setup
|
||||||
|
|
||||||
@ -93,7 +95,7 @@ To define a peer group limited to your LAN, choose [DODownloadMode](waas-deliver
|
|||||||
|
|
||||||
###### Wide area network (WAN)
|
###### Wide area network (WAN)
|
||||||
|
|
||||||
To achieve peer groups across NATs within the same site, over the WAN, or to have more control in your local environment, use download mode ‘2’, Group-mode. Group download mode allows you to define a unique GUID Group ID or use existing logical groupings (e.g. AD Site) in your enterprise with the [DOGroupIDSource](waas-delivery-optimization-reference.md#select-the-source-of-group-ids) setting to identify a peer group.
|
To achieve peer groups across NATs within the same site, over the WAN, or to have more control in your local environment, use download mode '2', Group-mode. Group download mode allows you to define a unique GUID Group ID or use existing logical groupings (for example, AD Site) in your enterprise with the [DOGroupIDSource](waas-delivery-optimization-reference.md#select-the-source-of-group-ids) setting to identify a peer group.
|
||||||
|
|
||||||
###### GroupIDSource default behavior
|
###### GroupIDSource default behavior
|
||||||
|
|
||||||
@ -108,16 +110,16 @@ There are several options for identifying your Group ID using the [DOGroupIDSour
|
|||||||
|
|
||||||
If your environment requires a more granular approach, you can use the restrict peer discovery setting alongside the download mode to achieve more control. For example, if you have several different subnets behind the same NAT but want to limit your peer groups to a single subnet, choose [DODownloadMode](waas-delivery-optimization-reference.md#download-mode) (1) and [DORestrictPeerSelection](waas-delivery-optimization-reference.md#select-a-method-to-restrict-peer-selection) (Subnet). This setting can be used with any of the peer-related download modes (1, 2, or 3).
|
If your environment requires a more granular approach, you can use the restrict peer discovery setting alongside the download mode to achieve more control. For example, if you have several different subnets behind the same NAT but want to limit your peer groups to a single subnet, choose [DODownloadMode](waas-delivery-optimization-reference.md#download-mode) (1) and [DORestrictPeerSelection](waas-delivery-optimization-reference.md#select-a-method-to-restrict-peer-selection) (Subnet). This setting can be used with any of the peer-related download modes (1, 2, or 3).
|
||||||
|
|
||||||
#### Non-peering options
|
#### Nonpeering options
|
||||||
|
|
||||||
There are two valid download modes that don't use P2P functionality to deliver content; download modes (0) and (99). download mode (0) uses additional metadata provided by the Delivery Optimization services for a peerless, reliable, and efficient download experience. Download mode (99) will provide a reliable download experience over HTTP from the download's original source or Microsoft, with no other checks.
|
There are two valid download modes that don't use P2P functionality to deliver content; download modes (0) and (99). Download mode (0) uses additional metadata provided by the Delivery Optimization services for a peerless, reliable, and efficient download experience. Download mode (99) will provide a reliable download experience over HTTP from the download's original source or Microsoft, with no other checks.
|
||||||
|
|
||||||
#### Peering with VPN
|
#### Peering with VPN
|
||||||
|
|
||||||
By default, if Delivery Optimization detects a VPN, peering is not used. To change this behavior, use the [DOAllowVPNPeerCaching](waas-delivery-optimization-reference.md#enable-peer-caching-while-the-device-connects-via-vpn) policy. The Delivery Optimization client looks in the network adapter’s ‘Description’ and ‘FriendlyName’ strings to determine VPN usage. To allow greater flexibility for VPN identification, use the [DOVpnKeywords](waas-delivery-optimization-reference.md#vpn-keywords) to add descriptors for a particular VPN you use in your organization.
|
By default, if Delivery Optimization detects a VPN, peering isn't used. To change this behavior, use the [DOAllowVPNPeerCaching](waas-delivery-optimization-reference.md#enable-peer-caching-while-the-device-connects-via-vpn) policy. The Delivery Optimization client looks in the network adapter's 'Description' and 'FriendlyName' strings to determine VPN usage. To allow greater flexibility for VPN identification, use the [DOVpnKeywords](waas-delivery-optimization-reference.md#vpn-keywords) to add descriptors for a particular VPN you use in your organization.
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> The default keyword list is “VPN”, “Secure”, and “Virtual Private Network”. For example, “MYVPN” matches the “VPN” keyword and would be detected as a VPN connection.
|
> The default keyword list is "VPN", "Secure", and "Virtual Private Network". For example, "MYVPN" matches the "VPN" keyword and would be detected as a VPN connection.
|
||||||
|
|
||||||
### 2b. Organization size
|
### 2b. Organization size
|
||||||
|
|
||||||
@ -145,7 +147,7 @@ Alter the minimum disk size (default is 32 GB) a device must have to use peering
|
|||||||
|
|
||||||
#### Optimize cache size
|
#### Optimize cache size
|
||||||
|
|
||||||
You can also manage the amount of space the Delivery Optimization cache uses with the following settings: [DOMaxCacheSize](waas-delivery-optimization-reference.md#max-cache-size) (default is 20%) and [DOAbsoluteMaxCacheSize](waas-delivery-optimization-reference.md#absolute-max-cache-size) (default is not configured).
|
You can also manage the amount of space the Delivery Optimization cache uses with the following settings: [DOMaxCacheSize](waas-delivery-optimization-reference.md#max-cache-size) (default is 20%) and [DOAbsoluteMaxCacheSize](waas-delivery-optimization-reference.md#absolute-max-cache-size) (default isn't configured).
|
||||||
|
|
||||||
#### RAM size
|
#### RAM size
|
||||||
|
|
||||||
@ -161,8 +163,12 @@ In an environment with devices that are plugged in and have ample free disk spac
|
|||||||
|
|
||||||
Looking to improve P2P efficiency? Some of the most powerful settings you can change that could have a significant impact within your environment include:
|
Looking to improve P2P efficiency? Some of the most powerful settings you can change that could have a significant impact within your environment include:
|
||||||
|
|
||||||
* Help optimize peer connection over HTTP connections using the [DOMinBackgroundQoS](waas-delivery-optimization-reference.md#minimum-background-qos) policy. A good value for the [DOMinBackgroundQoS](waas-delivery-optimization-reference.md#minimum-background-qos) policy is something lower than the average download speed seen in your network. For example, if your average speed is 1000 KB/s, set this policy to 500 KB/s.
|
- Help optimize peer connection over HTTP connections using the [DOMinBackgroundQoS](waas-delivery-optimization-reference.md#minimum-background-qos) policy. A good value for the [DOMinBackgroundQoS](waas-delivery-optimization-reference.md#minimum-background-qos) policy is something lower than the average download speed seen in your network. For example, if your average speed is 1000 KB/s, set this policy to 500 KB/s.
|
||||||
* Improve chances of downloading from peers and/or cache server by delaying the time DO attempts to make connections before falling back to the HTTP source. The set of delay-related policies include: [DODelayBackgroundDownloadFromHttp](waas-delivery-optimization-reference.md#delay-background-download-from-http-in-secs), [DODelayForegroundDownloadFromHttp](waas-delivery-optimization-reference.md#delay-foreground-download-from-http-in-secs). To improve efficiencies from peers or a dedicated cache server, a good starting point is 60 seconds for background settings and 30 seconds for foreground settings.
|
- Improve chances of downloading from peers and/or cache server by delaying the time DO attempts to make connections before falling back to the HTTP source. The set of delay-related policies include:
|
||||||
|
- [DODelayBackgroundDownloadFromHttp](waas-delivery-optimization-reference.md#delay-background-download-from-http-in-secs)
|
||||||
|
- [DODelayForegroundDownloadFromHttp](waas-delivery-optimization-reference.md#delay-foreground-download-from-http-in-secs)
|
||||||
|
|
||||||
|
To improve efficiencies from peers or a dedicated cache server, a good starting point is 60 seconds for background settings and 30 seconds for foreground settings.
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> Not all content types are eligible for P2P. Refer to the [complete list](waas-delivery-optimization.md#types-of-download-content-supported-by-delivery-optimization) to learn more.
|
> Not all content types are eligible for P2P. Refer to the [complete list](waas-delivery-optimization.md#types-of-download-content-supported-by-delivery-optimization) to learn more.
|
||||||
@ -171,8 +177,14 @@ Looking to improve P2P efficiency? Some of the most powerful settings you can ch
|
|||||||
|
|
||||||
Regardless of P2P, consider setting the following policies to avoid network disruption.
|
Regardless of P2P, consider setting the following policies to avoid network disruption.
|
||||||
|
|
||||||
* Manage network usage as a percentage or absolute value. These policies include: [DOPercentageMaxBackgroundBandwidth](waas-delivery-optimization-reference.md#maximum-background-download-bandwidth), [DOPercentageMaxForegroundBandwidth](waas-delivery-optimization-reference.md#maximum-foreground-download-bandwidth), [DOMaxBackgroundDownloadBandwidth](waas-delivery-optimization-reference.md#maximum-background-download-bandwidth-in-kbs), and [DOMaxForegroundDownloadBandwidth](waas-delivery-optimization-reference.md#maximum-foreground-download-bandwidth-in-kbs).
|
- Manage network usage as a percentage or absolute value. These policies include:
|
||||||
* Reduce disruptions by throttling differently at different times of day, using the business hours policies, [DOSetHoursToLimitBackgroundDownloadBandwidth](waas-delivery-optimization-reference.md#set-business-hours-to-limit-background-download-bandwidth) and [DOSetHoursToLimitForegroundDownloadBandwidth](waas-delivery-optimization-reference.md#set-business-hours-to-limit-foreground-download-bandwidth).
|
- [DOPercentageMaxBackgroundBandwidth](waas-delivery-optimization-reference.md#maximum-background-download-bandwidth)
|
||||||
|
- [DOPercentageMaxForegroundBandwidth](waas-delivery-optimization-reference.md#maximum-foreground-download-bandwidth)
|
||||||
|
- [DOMaxBackgroundDownloadBandwidth](waas-delivery-optimization-reference.md#maximum-background-download-bandwidth-in-kbs)
|
||||||
|
- [DOMaxForegroundDownloadBandwidth](waas-delivery-optimization-reference.md#maximum-foreground-download-bandwidth-in-kbs)
|
||||||
|
- Reduce disruptions by throttling differently at different times of day, using the following business hours policies:
|
||||||
|
- [DOSetHoursToLimitBackgroundDownloadBandwidth](waas-delivery-optimization-reference.md#set-business-hours-to-limit-background-download-bandwidth)
|
||||||
|
- [DOSetHoursToLimitForegroundDownloadBandwidth](waas-delivery-optimization-reference.md#set-business-hours-to-limit-foreground-download-bandwidth).
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> The absolute policies are recommended in low bandwidth environments.
|
> The absolute policies are recommended in low bandwidth environments.
|
||||||
@ -181,10 +193,10 @@ Regardless of P2P, consider setting the following policies to avoid network disr
|
|||||||
|
|
||||||
:::image type="content" source="images/do-setup-connected-cache.png" alt-text="Screenshot of Delivery Optimization options when using Connected Cache." lightbox="images/do-setup-connected-cache.png":::
|
:::image type="content" source="images/do-setup-connected-cache.png" alt-text="Screenshot of Delivery Optimization options when using Connected Cache." lightbox="images/do-setup-connected-cache.png":::
|
||||||
|
|
||||||
* [DOCacheHost](waas-delivery-optimization-reference.md#cache-server-hostname) is the list of cache host server names, separated with commas. *Delivery Optimization client connects to the listed Microsoft Connected Cache servers in the order as they're listed.*
|
- [DOCacheHost](waas-delivery-optimization-reference.md#cache-server-hostname) is the list of cache host server names, separated with commas. *Delivery Optimization client connects to the listed Microsoft Connected Cache servers in the order as they're listed.*
|
||||||
* [DOCacheHostSource](waas-delivery-optimization-reference.md#cache-server-hostname-source) can be used to dynamically discover cache host servers on the network, using DHCP.
|
- [DOCacheHostSource](waas-delivery-optimization-reference.md#cache-server-hostname-source) can be used to dynamically discover cache host servers on the network, using DHCP.
|
||||||
* [DelayCacheServerFallbackBackground](waas-delivery-optimization-reference.md#delay-background-download-cache-server-fallback-in-secs) and [DelayCacheServerFallbackForeground](waas-delivery-optimization-reference.md#delay-foreground-download-cache-server-fallback-in-secs) are the delay policies to help improve chances of pulling content from the network cache host servers. (See recommended values in [Improve P2P efficiency](#2d-improve-p2p-efficiency) section above).
|
- [DelayCacheServerFallbackBackground](waas-delivery-optimization-reference.md#delay-background-download-cache-server-fallback-in-secs) and [DelayCacheServerFallbackForeground](waas-delivery-optimization-reference.md#delay-foreground-download-cache-server-fallback-in-secs) are the delay policies to help improve chances of pulling content from the network cache host servers. (See recommended values in [Improve P2P efficiency](#2d-improve-p2p-efficiency) section above).
|
||||||
* [DODisallowCacheServerDownloadsOnVPN](waas-delivery-optimization-reference.md#disallow-cache-server-downloads-on-vpn) allows control of the cache host server to supply content, when device is on a VPN connection.
|
- [DODisallowCacheServerDownloadsOnVPN](waas-delivery-optimization-reference.md#disallow-cache-server-downloads-on-vpn) allows control of the cache host server to supply content, when device is on a VPN connection.
|
||||||
|
|
||||||
## 4. Choose where to set Delivery Optimization policies
|
## 4. Choose where to set Delivery Optimization policies
|
||||||
|
|
||||||
@ -204,15 +216,15 @@ Use MDM to manage Delivery Optimization settings here,
|
|||||||
|
|
||||||
Delivery Optimization is integrated with both Microsoft Endpoint Manager and Configuration Manager.
|
Delivery Optimization is integrated with both Microsoft Endpoint Manager and Configuration Manager.
|
||||||
|
|
||||||
* [Microsoft Endpoint Manager (MEM)](/mem/intune/configuration/delivery-optimization-windows)
|
- [Microsoft Endpoint Manager (MEM)](/mem/intune/configuration/delivery-optimization-windows)
|
||||||
* [Microsoft Endpoint Configuration Manager (MECM)](/mem/configmgr/sum/deploy-use/optimize-windows-10-update-delivery)
|
- [Microsoft Endpoint Configuration Manager (MECM)](/mem/configmgr/sum/deploy-use/optimize-windows-10-update-delivery)
|
||||||
|
|
||||||
## Summary of basic configuration recommendations
|
## Summary of basic configuration recommendations
|
||||||
|
|
||||||
| Use case | Policy | Recommended value |
|
| Use case | Policy | Recommended value |
|
||||||
| ----- | ----- | ----------------- |
|
| ----- | ----- | ----------------- |
|
||||||
| Use P2P | DownloadMode | 1 or 2 |
|
| Use P2P | DownloadMode | 1 or 2 |
|
||||||
| Do not use P2P | DownloadMode | 0 |
|
| Don't use P2P | DownloadMode | 0 |
|
||||||
| Number of devices in the organization | MinFileSizeToCache | 1 MB for peer group > 100 devices |
|
| Number of devices in the organization | MinFileSizeToCache | 1 MB for peer group > 100 devices |
|
||||||
| Idle system resources | MaxCacheAge | 7 days (604800 seconds) |
|
| Idle system resources | MaxCacheAge | 7 days (604800 seconds) |
|
||||||
| Improve P2P efficiency | MinBackgroundQoS and DelayBackgroundDownloadFromHttp / DelayForegroundDownloadFromHttp | 500 KB/s and 60/30 seconds |
|
| Improve P2P efficiency | MinBackgroundQoS and DelayBackgroundDownloadFromHttp / DelayForegroundDownloadFromHttp | 500 KB/s and 60/30 seconds |
|
||||||
@ -220,11 +232,11 @@ Delivery Optimization is integrated with both Microsoft Endpoint Manager and Con
|
|||||||
|
|
||||||
## Monitor Delivery Optimization
|
## Monitor Delivery Optimization
|
||||||
|
|
||||||
Whether you opt for the default Delivery Optimization configurations or tailor them to suit your environment, you will want to track the outcomes to see how they improve your efficiency. [Learn more](waas-delivery-optimization-monitor.md) about the monitoring options for Delivery Optimization.
|
Whether you opt for the default Delivery Optimization configurations or tailor them to suit your environment, you'll want to track the outcomes to see how they improve your efficiency. [Learn more](waas-delivery-optimization-monitor.md) about the monitoring options for Delivery Optimization.
|
||||||
|
|
||||||
## Troubleshoot Delivery Optimization
|
## Troubleshoot Delivery Optimization
|
||||||
|
|
||||||
There could be many different reasons why Delivery Optimization is not working in your environment. [Learn more](delivery-optimization-troubleshoot.md) about the DO Troubleshooter and common problems and solutions to help improve the experience of using Delivery Optimization.
|
There could be many different reasons why Delivery Optimization isn't working in your environment. [Learn more](delivery-optimization-troubleshoot.md) about the DO Troubleshooter and common problems and solutions to help improve the experience of using Delivery Optimization.
|
||||||
|
|
||||||
## Test Delivery Optimization
|
## Test Delivery Optimization
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user