Cuir in eagar

Comhroinn trí

Delivery Optimization reference

Looking for Group Policy objects? See Delivery Optimization reference or the main spreadsheet available at the Download Center for Windows 11 or for Windows 10.

There are many configuration options you can set in Delivery Optimization to customize the content delivery experience specific to your environment needs. This article summarizes those configurations for your reference. If you just need an overview of Delivery Optimization, see What is Delivery Optimization. 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.

Delivery Optimization options

You can use Group Policy or an MDM solution like Intune to configure Delivery Optimization.

The Delivery Optimization settings in Group Policy are under Configuration\Policies\Administrative Templates\Windows Components\Delivery Optimization. In MDM, the same settings are under .Vendor/MSFT/Policy/Config/DeliveryOptimization/.

Summary of Delivery Optimization settings

Group Policy setting MDM setting Supported from version Notes
Download mode DODownloadMode 1511 Default is configured to LAN(1). The Group Download mode (2) combined with Group ID, enables administrators to create custom device groups that share content between devices in the group.
Group ID DOGroupID 1511 Used with Group Download mode. If not configured, check GroupIDSource. When GroupID or GroupIDSource policies aren't configured, the GroupID is defined as the AD Site (1), Authenticated domain SID (2) or Microsoft Entra tenant ID (5), in that order.
Select the source of Group IDs DOGroupIDSource 1803 If not configured, check Group ID. When the GroupID or GroupIDSource policies aren't configured, the Group is defined as the AD Site (1), Authenticated domain SID (2) or Microsoft Entra tenant ID (5), in that order.
Select a method to restrict peer selection DORestrictPeerSelectionBy 1803 Default isn't configured.
Minimum RAM (inclusive) allowed to use peer caching DOMinRAMAllowedToPeer 1703 Default value is 4 GB.
Minimum disk size allowed to use peer caching DOMinDiskSizeAllowedToPeer 1703 Default value is 32 GB.
Max cache age DOMaxCacheAge 1511 Default value is 259,200 seconds (three days).
Max cache size DOMaxCacheSize 1511 Default value is 20%.
Absolute max cache size (in GBs) DOAbsoluteMaxCacheSize 1607 Default isn't configured.
Modify cache drive DOModifyCacheDrive 1607 Default to the operating system drive through the %SYSTEMDRIVE% environment variable.
Minimum peer caching content file size DOMinFileSizeToCache 1703 Default file size is 50 MB.
Monthly upload data cap DOMonthlyUploadDataCap 1607 Default value is 20 GB.
Minimum background QoS DOMinBackgroundQoS 1607 Recommend setting this to 500 KB/s. Default value is 2500 KB/s.
Enable peer caching while the device connects via VPN DOAllowVPNPeerCaching 1709 Default is to not allow peering while on VPN.
VPN keywords DOVpnKeywords Windows 11, version 22H2 with the September 2023 or later update installed Allows you to set one or more keywords used to recognize VPN connections.
Disallow cache server downloads from VPN DODisallowCacheServerDownloadsOnVPN Windows 11, version 22H2 with the September 2023 or later update installed Disallow downloads from Microsoft Connected Cache servers when the device connects via VPN. By default, the device is allowed to download from Microsoft Connected Cache when connected via VPN.
Allow uploads while the device is on battery while under set battery level DOMinBatteryPercentageAllowedToUpload 1709 Default is to not allow peering while on battery.
Maximum foreground download bandwidth (percentage) DOPercentageMaxForegroundBandwidth 1803 Default is '0' which will dynamically adjust.
Maximum background download bandwidth (percentage) DOPercentageMaxBackgroundBandwidth 1803 Default is '0' which will dynamically adjust.
Maximum foreground download bandwidth (in KB/s) DOMaxForegroundDownloadBandwidth 2004 Default is '0' which will dynamically adjust.
Maximum background download bandwidth (in KB/s) DOMaxBackgroundDownloadBandwidth 2004 Default is '0' which will dynamically adjust.
Set hours to limit foreground download bandwidth DOSetHoursToLimitForegroundDownloadBandwidth 1803 Default isn't configured.
Set hours to limit background download bandwidth DOSetHoursToLimitBackgroundDownloadBandwidth 1803 Default isn't configured.
Delay foreground download from HTTP (in secs) DODelayForegroundDownloadFromHttp 1803 Default isn't configured. For peering, use this policy to delay the fallback to the HTTP source. Learn more about the different delay options.
Delay background download from HTTP (in secs) DODelayBackgroundDownloadFromHttp 1803 Default isn't configured. For peering, use this policy to delay the fallback to the HTTP source. Learn more about the different delay options.
Delay foreground download cache server fallback (in secs) DelayCacheServerFallbackForeground 1903 Default isn't configured. For Microsoft Connected Cache content, use this policy to delay the fallback to the HTTP source. Learn more about the different delay options.
Delay background download cache server fallback (in secs) DelayCacheServerFallbackBackground 1903 Default isn't configured. For Microsoft Connected Cache content, use this policy to delay the fallback to the HTTP source. Learn more about the different delay options.
Cache server hostname DOCacheHost 1809 No value is configured as default.
Cache server hostname source DOCacheHostSource 2004 No value is configured as default.
Maximum download bandwidth DOMaxDownloadBandwidth 1607 (deprecated in Windows 10, version 2004); use Maximum background download bandwidth (in KB/s) or Maximum foreground download bandwidth (in KB/s) instead) Default is '0' which will dynamically adjust.
Percentage of maximum download bandwidth DOPercentageMaxDownloadBandwidth 1607 (deprecated in Windows 10, version 2004); use Maximum background download bandwidth (in KB/s) or Maximum foreground download bandwidth (in KB/s) instead) Default is '0' which will dynamically adjust.
Maximum upload bandwidth DOMaxUploadBandwidth 1607 (deprecated in Windows 10, version 2004) Default is '0' (unlimited).

More detail on Delivery Optimization settings

Locally cached updates

Delivery Optimization uses locally cached updates to deliver contact via peers. The more content available in the cache, the more likely that peering can be used. In cases where devices have enough local storage and you'd like to cache more content. Likewise, if you have limited storage and would prefer to cache less, use the following settings to adjust the Delivery Optimization cache to suit your scenario:

Note

It is possible to configure preferred cache devices. For more information, see DOGroupID.

All cached files have to be above a set minimum size. This size is automatically set by the Delivery Optimization cloud services, but when local storage is sufficient and the network isn't strained or congested, administrators might choose to change it to obtain increased performance. You can set the minimum size of files to cache by adjusting DOMinFileSizeToCache.

Impact to network

More options available that control the impact Delivery Optimization has on your network include the following settings:

Policies to prioritize the use of peer-to-peer and cache server sources

When Delivery Optimization client is configured to use peers and Microsoft Connected Cache, to achieve the best possible content delivery experience, the client connects to both Connected Cache and peers in parallel. If the desired content can't be obtained from Connected Cache or peers, Delivery Optimization will automatically fall back to the HTTP source to get the requested content. There are four settings that allow you to prioritize peer-to-peer or Connected Cache sources by delaying the immediate fallback to HTTP source, which is the default behavior.

Peer-to-peer delay fallback settings
Microsoft Connected Cache delay fallback settings

If both peer-to-peer and Connected Cache are configured, the peer-to-peer delay settings will take precedence over the cache server delay settings. This setting allows Delivery Optimization to discover peers first then recognize the fallback setting for the Connected Cache cache server.

System resource usage

Administrators can further customize scenarios where Delivery Optimization is used with the following settings:

Download mode

MDM Setting: DODownloadMode

Download mode dictates which download sources clients are allowed to use when downloading Windows updates in addition to Windows Update servers. The following table shows the available download mode options and what they do. Other technical details for these policies are available in Policy CSP - Delivery Optimization.

Download mode option Functionality when configured
HTTP Only (0) This setting disables peer-to-peer caching but still allows Delivery Optimization to download content over HTTP from the download's original source or a Microsoft Connected Cache server. This mode uses additional metadata provided by the Delivery Optimization cloud services for a peerless, reliable and efficient download experience.
LAN (1 - Default) This default operating mode for Delivery Optimization enables peer sharing on the same network. The Delivery Optimization cloud service finds other clients that connect to the Internet using the same public IP as the target client. These clients then try to connect to other peers on the same network by using their private subnet IP.
Group (2) When group mode is set, the group is automatically selected based on the device's Active Directory Domain Services (AD DS) site (Windows 10, version 1607) or the domain the device is authenticated to (Windows 10, version 1511). In group mode, peering occurs across internal subnets, between devices that belong to the same group, including devices in remote offices. You can use GroupID option to create your own custom group independently of domains and AD DS sites. Starting with Windows 10, version 1803, you can use the GroupIDSource parameter to take advantage of other method to create groups dynamically. Group download mode is the recommended option for most organizations looking to achieve the best bandwidth optimization with Delivery Optimization.
Internet (3) Enable Internet peer sources for Delivery Optimization.
Simple (99) Simple mode disables the use of Delivery Optimization cloud services completely (for offline environments). Delivery Optimization switches to this mode automatically when the Delivery Optimization cloud services are unavailable, unreachable, or when the content file size is less than 10 MB. In this mode, Delivery Optimization provides a reliable download experience over HTTP from the download's original source or a Microsoft Connected Cache server, with no peer-to-peer caching.
Bypass (100) Starting in Windows 11, this option is deprecated. Don't configure Download mode to '100' (Bypass), which can cause some content to fail to download. If you want to disable peer-to-peer functionality, configure DownloadMode to (0). If your device doesn't have internet access, configure Download Mode to (99). When you configure Bypass (100), the download bypasses Delivery Optimization and uses BITS instead. You don't need to configure this option if you're using Configuration Manager.

Note

When you use Microsoft Entra tenant, AD Site, or AD Domain as the source of group IDs, the association of devices participating in the group should not be relied on for an authentication of identity of those devices.

Group ID

MDM Setting: DOGroupID

By default, peer sharing on clients using the Group download mode (option 2) is limited to the same domain in Windows 10, version 1511, and the same domain and Active Directory Domain Services site in Windows 10, version 1607. By using the Group ID setting, you can optionally create a custom group that contains devices that should participate in Delivery Optimization but don't fall within those domain or Active Directory Domain Services site boundaries, including devices in another domain. Using Group ID, you can further restrict the default group (for example, you could create a subgroup representing an office building), or extend the group beyond the domain, allowing devices in multiple domains in your organization to be peers. This setting requires the custom group to be specified as a GUID on each device that participates in the custom group.

Note

To generate a GUID using Powershell, use [guid]::NewGuid()

This configuration is optional and not required for most implementations of Delivery Optimization.

Select the source of Group IDs

MDM Setting: DOGroupIDSource

Starting in Windows 10, version 1803, configure this policy to restrict peer selection to a specific source, when using a GroupID policy. The options are:

  • 0 = Not set
  • 1 = AD Site
  • 2 = Authenticated domain SID
  • 3 = DHCP Option ID (with this option, the client queries DHCP Option ID 234 and use the returned GUID value as the Group ID)
  • 4 = DNS Suffix
  • 5 = Starting with Windows 10, version 1903, you can use the Microsoft Entra tenant ID as a means to define groups. To do this configure the value for DOGroupIdSource to its new maximum value of 5.

When configured, the Group ID will be assigned automatically from the selected source. This policy is ignored if the GroupID policy is also configured. The default behavior, when the GroupID or GroupIDSource policies aren't configured, is to determine the Group ID using AD Site (1), Authenticated domain SID (2) or Microsoft Entra tenant ID (5), in that order. If GroupIDSource is configured to either DHCP Option ID (3) or DNS Suffix (4) and those methods fail, the default behavior is used instead. The option configured in this policy only applies to Group (2) download mode. If Group (2) isn't configured as Download mode, this policy will be ignored. If you configure the value to anything other than 0-5, the policy is ignored.

Minimum RAM (inclusive) allowed to use peer caching

MDM Setting: DOMinRAMAllowedToPeer

This setting specifies the minimum RAM size in GB required to use Peer Caching. For example if the minimum set is 1 GB, then devices with 1 GB or higher available RAM will be allowed to use Peer caching. The recommended values are 1 to 4, and the default value is 4 GB.

Minimum disk size allowed to use peer caching

MDM Setting: DOMinDiskSizeAllowedToPeer

This setting specifies the required minimum disk size (capacity in GB) for the device to use Peer Caching. The recommended values are 64 to 256, and the default value is 32 GB.

Note

If the Modify Cache Drive policy is configured, the disk size check applies to the new working directory specified by this policy.

Max cache age

MDM Setting: DOMaxCacheAge

In environments configured for Delivery Optimization, you might want to configure an expiration on cached updates and Windows application installation files. If so, this setting defines the maximum number of seconds each file can be held in the Delivery Optimization cache on each Windows 10 client device. Alternatively, organizations might choose to configure this value to "0" which means "unlimited" to avoid peers redownloading content. When "Unlimited" value is configured, Delivery Optimization holds the files in the cache longer and cleans up the cache as needed (for example when the cache size exceeded the maximum space allowed). The default value is 259,200 seconds (three days).

Max cache size

MDM Setting: DOMaxCacheSize

This setting limits the maximum amount of space the Delivery Optimization cache can use as a percentage of the available drive space, from 1 to 100. For example, if you configure this value to 10 on a Windows client device that has 100 GB of available drive space, then Delivery Optimization uses up to 10 GB of that space. Delivery Optimization constantly assesses the available drive space and automatically clear the cache to keep the maximum cache size under the configured percentage. The default value is 20%.

Absolute max cache size

MDM Setting: DOAbsoluteMaxCacheSize

This setting specifies the maximum number of gigabytes the Delivery Optimization cache can use. This is different from the Max Cache Size setting, which is a percentage of available disk space. Also, if you configure this policy, it overrides the Max Cache Size setting. The default value is not configured.

Minimum peer caching content file size

MDM Setting: DOMinFileSizeToCache

This setting specifies the minimum content file size in MB enabled to use Peer Caching. The recommended values are from 1 to 100000. The default file size is 50 MB to participate in peering.

Maximum foreground download bandwidth

MDM Setting: DOPercentageMaxForegroundBandwidth

Starting in Windows 10, version 1803, specifies the maximum foreground download bandwidth that Delivery Optimization uses across all concurrent download activities as a percentage of available download bandwidth. The default value of "0" means that Delivery Optimization dynamically adjusts to use the available bandwidth for foreground downloads. However, downloads from LAN peers aren't throttled even when this policy is configured.

Maximum background download bandwidth

MDM Setting: DOPercentageMaxBackgroundBandwidth

Starting in Windows 10, version 1803, specifies the maximum background download bandwidth that Delivery Optimization uses across all concurrent download activities as a percentage of available download bandwidth. The default value of "0" means that Delivery Optimization dynamically adjusts to use the available bandwidth for background downloads. However, downloads from LAN peers aren't throttled even when this policy is configured.

Note

It is recommended to use the absolute value download options 'DOMaxBackgroundDownloadBandwidth' and 'DOMaxForegroundDownloadBandwidth', rather than percentage-based options, for low bandwidth environments.

Set business hours to limit foreground download bandwidth

MDM Setting: DOSetHoursToLimitForegroundDownloadBandwidth

Starting in Windows 10, version 1803, specifies the maximum foreground download bandwidth that Delivery Optimization uses during and outside business hours across all concurrent download activities as a percentage of available download bandwidth. By default, this policy isn't configured.

Set business hours to limit background download bandwidth

MDM Setting: DOSetHoursToLimitBackgroundDownloadBandwidth

Starting in Windows 10, version 1803, specifies the maximum background download bandwidth that Delivery Optimization uses during and outside business hours across all concurrent download activities as a percentage of available download bandwidth. By default, this policy isn't configured.

Select a method to restrict peer selection

MDM Setting: DORestrictPeerSelectionBy

Starting in Windows 10, version 1803, configure this policy to further restrict peer selection in Download Modes LAN (1) and Group (2). In Windows 11, the 'Local Peer Discovery' option was introduced to restrict peer discovery to the local network. Currently the available options include: 0 = None, 1 = Subnet mask, and 2 = Local Peer Discovery (DNS-SD). Choosing either Subnet mask (1) or Local Peer Discovery (2) will avoid peering between subnets.

If Group mode is configured, Delivery Optimization connects to locally discovered peers that are also part of the same Group (have the same Group ID) and prevents devices that aren't using the same Group ID from participating.

In Windows 11, the Local Peer Discovery (DNS-SD) option can be configured via MDM or Group Policy. However, in Windows 10, this feature can be enabled by setting the HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization\DORestrictPeerSelectionBy value to 2.

The default behaviors differ between Windows 10 and Windows 11. In Windows 10, there is no restriction configured. In Windows 11, the default peer selection is restricted to the Subnet only in LAN Download mode (1)

Delay foreground download from HTTP (in secs)

MDM Setting: DODelayForegroundDownloadFromHttp

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. By default, this policy isn't configured.

Delay background download from HTTP (in secs)

MDM Setting: DODelayBackgroundDownloadFromHttp

Starting in Windows 10, version 1803, this allows you to delay the use of an HTTP source in a background download that is allowed to use peer-to-peer. By default, this policy isn't configured.

Delay foreground download cache server fallback (in secs)

MDM Setting: DelayCacheServerFallbackForeground

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 the 'Delay foreground download from HTTP policy is configured, it will apply first (to allow download from peers). By default, this policy isn't configured.

Delay background download cache server fallback (in secs)

MDM Setting: DelayCacheServerFallbackBackground

Starting in Windows 10, version 1903, configure this policy to delay the fallback from cache server to the HTTP source for a background content download by X seconds. If the 'Delay background download from HTTP' policy is configured, it will apply first (to allow downloads from peers) and then this policy will be applied. By default, this policy isn't configured.

Minimum background QoS

MDM Setting: DOMinBackgroundQoS

This value specifies the minimum download speed guarantee that a client attempts to achieve and will fulfill by downloading more kilobytes from HTTP sources. The lower this value is, the more content is sourced using peers on the network rather than HTTP sources. The higher this value, the more content is received from HTTP sources, versus peers on the local network. The default value is 2500 KB/s.

Modify cache drive

MDM Setting: DOModifyCacheDrive

This setting allows for an alternate Delivery Optimization cache location on the clients. By default, the cache is stored on the operating system drive through the %SYSTEMDRIVE% environment variable. You can configure the value to an environment variable (for example, %SYSTEMDRIVE%), a drive letter (for example, D:), or a folder path (for example, D:\DOCache).

Monthly upload data cap

MDM Setting: DOMonthlyUploadDataCap

This setting specifies the total amount of data in gigabytes that a Delivery Optimization client can upload to Internet peers per month. A value of "0" means that an unlimited amount of data can be uploaded. The default value for this setting is 20 GB.

Enable peer caching while the device connects via VPN

MDM Setting: DOAllowVPNPeerCaching

This setting determines whether a device will be allowed to participate in Peer Caching while connected to VPN. By default, if a VPN connection is detected, peering isn't allowed, except when the 'Local Discovery' (DNS-SD) option is chosen. Specify "true" to allow the device to participate in Peer Caching while connected via VPN to the domain network. The device can download from or upload to other domain network devices, either on VPN or on the corporate domain network.

VPN keywords

MDM Setting: DOVpnKeywords

This policy allows you to configure one or more comma-separated keywords used to recognize VPN connections. By default, this policy is not configured so if a VPN is detected, the device will not use peering. Delivery Optimization automatically detects a VPN connection by looking at the network adapter's 'Description' and 'FriendlyName' strings using the default keyword list including: "VPN", "Secure", and "Virtual Private Network" (ex: "MSFTVPN" matches the "VPN" keyword). As the number of VPNs grow it's difficult to support an ever-changing list of VPN names. To address this, we've introduced this new setting to add unique VPN names to meet the needs of individual environments.

Disallow cache server downloads on VPN

MDM Setting: DODisallowCacheServerDownloadsOnVPN

This policy disallows downloads from Connected Cache servers when the device connects via VPN. By default, the device is allowed to download from Connected Cache when connected via VPN. Configure this policy if you prefer devices to download directly from the Internet when connected remotely (via VPN) instead of pulling from a Microsoft Connected Cache server deployed on your corporate network.

Allow uploads while the device is on battery while under set battery level

MDM Setting: DOMinBatteryPercentageAllowedToUpload

This setting specifies battery levels at which a device will be allowed to upload data. Specify any value between 1 and 100 (in percentage) to allow the device to upload data to LAN and Group peers while on DC power (Battery). Uploads will automatically pause when the battery level drops below the configured minimum battery level. The recommended value to configure, if you allow uploads on battery, is 40 (for 40%). 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 configure the battery value under which uploads pause.

Cache server hostname

MDM Setting: DOCacheHost

Configure this policy 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.somerandomhost.com,10.10.1.7. By default, this policy has no value. Delivery Optimization client will connect to the listed Microsoft Connected Cache servers in the order as they are listed. When multiple FQDNs or IP Addresses are listed, fallback to the CDN occurs immediately after the first failure in downloading from a cache server, unless the DelayCacheServerFallbackBackground or DelayCacheServerFallbackForeground policies are configured. When these delay policies are configured, the fallback occurs only after the configured delay time and the client continues to attempt connecting to the cache servers in round robin order before the delay time expires.

Important

Any value will signify that the policy is configured. For example, an empty string ("") isn't considered empty.

Cache server hostname source

MDM Setting: DOCacheHostSource

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 queries DHCP Option ID 235 and use the returned value as the Cache Server Hostname. Option 2 overrides the Cache Server Hostname policy, if configured. By default, this policy has no value.

Configure this policy to designate Delivery Optimization in Network Cache servers through a custom DHCP Option. Specify the custom DHCP option on your DHCP server as text type. You can add one or more values as either fully qualified domain names (FQDN) or IP addresses. To add multiple values, separate each FQDN or IP address with 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 configured.

Maximum foreground download bandwidth (in KB/s)

MDM Setting: DOMaxForegroundDownloadBandwidth

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" means that Delivery Optimization dynamically adjusts to use the available bandwidth for downloads.

Maximum background download bandwidth (in KB/s)

MDM Setting: DOMaxBackgroundDownloadBandwidth

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" means that Delivery Optimization dynamically adjusts to use the available bandwidth for downloads.

Deprecated policies

Maximum download bandwidth

MDM Setting: DOMaxDownloadBandwidth

Deprecated in Windows 10, version 2004. This setting specifies the maximum download bandwidth that can be used across all concurrent Delivery Optimization downloads in kilobytes per second (KB/s). A default value of "0" means that Delivery Optimization dynamically adjusts and optimizes the maximum bandwidth used.

Percentage of maximum download bandwidth

MDM Setting: DOPercentageMaxDownloadBandwidth

Deprecated in Windows 10, version 2004. This setting specifies the maximum download bandwidth that Delivery Optimization can use across all concurrent download activities as a percentage of available download bandwidth. The default value of "0" means that Delivery Optimization dynamically adjusts to use the available bandwidth for downloads.

Max upload bandwidth

MDM Setting: DOMaxUploadBandwidth

Deprecated in Windows 10, version 2004. This setting allows you to limit the number of upload bandwidth individual clients can use for Delivery Optimization. Consider this setting when clients are providing content to requesting peers on the network. This option is configured in kilobytes per second (KB/s). The default value is "0" or "unlimited" which means Delivery Optimization dynamically optimizes for minimal usage of upload bandwidth; however it doesn't cap the upload bandwidth rate at a set rate.