Set up Delivery Optimization for Windows 10 updates

Applies to

Looking for consumer information? See Windows Update: FAQ

Recommended Delivery Optimization settings

Delivery Optimization offers a great many settings to fine-tune its behavior (see Delivery Optimization reference 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.

• 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?
• What percentage of your devices are mobile?
• Do your devices have a lot of free space on their drives?
• Do you have a lab scenario with many devices on AC power?

These scenarios (and the recommended settings for each) are not mutually exclusive. It’s possible that your deployment might involve more than one of these scenarios, in which case you can employ the related settings in any combination as needed. In all cases, however, «download mode» is the most important one to set.

Microsoft Intune includes a profile to make it easier to set Delivery Optimization policies. For details, see Delivery Optimization settings for Intune.

Use case	Policy	Recommended value	Reason
Hub & spoke topology	Download mode	1 or 2	Automatic grouping of peers to match your topology
Sites with > 30 devices	Minimum file size to cache	10 MB (or 1 MB)	Leverage peers-to-peer capability in more downloads
Large number of mobile devices	Allow uploads on battery power	60%	Increase # of devices that can upload while limiting battery drain
Labs with AC-powered devices	Content Expiration	7 (up to 30) days	Leverage devices that can upload more for a longer period

Hybrid WAN scenario

For this scenario, grouping devices by domain allows devices to be included in peer downloads and uploads across VLANs. Set Download Mode to 2 — Group. The default group is the authenticated domain or Active Directory site. If your domain-based group is too wide, or your Active Directory sites aren’t aligned with your site network topology, then you should consider additional options for dynamically creating groups, for example by using the GroupIDSrc parameter.

To do this in Group Policy go to Configuration\Policies\Administrative Templates\Windows Components\Delivery Optimization and set Download mode to 2.

To do this with MDM, go to .Vendor/MSFT/Policy/Config/DeliveryOptimization/ and set DODownloadMode to 1 or 2.

Hub and spoke topology with boundary groups

The default download mode setting is 1; this means all devices breaking out to the internet using the same public IP will be considered as a single peer group. To prevent peer-to-peer activity across groups, you should set the download mode to 2. If you have already defined Active Directory sites per hub or branch office, then you don’t need to do anything else. If you’re not using Active Directory sites, you should set RestrictPeerSelectionBy policies to restrict the activity to the subnet or set a different source for Groups by using the GroupIDSrc parameter. See Select a method to restrict peer selection.

To do this in Group Policy go to Configuration\Policies\Administrative Templates\Windows Components\Delivery Optimization and set Download mode to 2.

To do this with MDM, go to .Vendor/MSFT/Policy/Config/DeliveryOptimization/ and set DODownloadMode to 2.

For more about using Delivery Optimization with Configuration Manager boundary groups, see Delivery Optmization.

Large number of mobile devices

If you have a mobile workforce with a great many mobile devices, set Delivery Optimization to allow uploads on battery power, while limiting the use to prevent battery drain. A setting for DOMinBatteryPercentageAllowedToUpload of 60% is a good starting point, though you might want to adjust it later.

To do this in Group Policy, go to Configuration\Policies\Administrative Templates\Windows Components\Delivery Optimization and set Allow uploads while the device is on battery while under set Battery level to 60.

To do this with MDM, go to .Vendor/MSFT/Policy/Config/DeliveryOptimization/ and set DOMinBatteryPercentageAllowedToUpload to 60.

Plentiful free space and large numbers of devices

Many devices now come with large internal drives. You can set Delivery Optimization to take better advantage of this space (especially if you have large numbers of devices) by changing the minimum file size to cache. If you have more than 30 devices in your local network or group, change it from the default 50 MB to 10 MB. If you have more than 100 devices (and are running Windows 10, version 1803 or later), set this value to 1 MB.

To do this in Group Policy, go to Configuration\Policies\Administrative Templates\Windows Components\Delivery Optimization and set Minimum Peer Caching Content File Size to 10 (if you have more than 30 devices) or 1 (if you have more than 100 devices).

To do this with MDM, go to .Vendor/MSFT/Policy/Config/DeliveryOptimization/ and set DOMinFileSizeToCache to 100 (if you have more than 30 devices) or 1 (if you have more than 100 devices).

Lab scenario

In a lab situation, you typically have a large number of devices that are plugged in and have a lot of free disk space. By increasing the content expiration interval, you can take advantage of these devices, using them as excellent upload sources in order to upload much more content over a longer period.

To do this in Group Policy, go to Configuration\Policies\Administrative Templates\Windows Components\Delivery Optimization and set Max Cache Age to 604800 (7 days) or more (up to 30 days).

To do this with MDM, go to .Vendor/MSFT/Policy/Config/DeliveryOptimization/ and set DOMaxCacheAge to 7 or more (up to 30 days).

Monitor 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.

Key	Value
File ID	A GUID that identifies the file being processed
Priority	Priority of the download; values are foreground or background
FileSize	Size of the file
TotalBytesDownloaded	The number of bytes from any source downloaded so far
PercentPeerCaching	The percentage of bytes downloaded from peers versus over HTTP
BytesFromPeers	Total bytes downloaded from peer devices (sum of bytes downloaded from LAN, Group, and Internet Peers)В
BytesfromHTTP	Total number of bytes received over HTTP
DownloadDuration	Total download time in seconds
Status	Current state of the operation. Possible values are: Downloading (download in progress); Complete (download completed, but is not uploading yet); Caching (download completed successfully and is ready to upload or uploading); Paused (download/upload paused by caller)
NumPeers	Indicates the total number of peers returned from the service.
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:

• Number of files downloadedВ
• Number of files uploadedВ
• Total bytes downloadedВ
• Total bytes uploadedВ
• Average transfer size (download); that is, the number bytes downloaded divided by the number of filesВ
• Average transfer size (upload); the number of bytes uploaded divided by the number of files
• Peer efficiency; same as PercentPeerCaching

Using the -Verbose option returns additional information:

• Bytes from peers (per type)В
• Bytes from CDN (the number of bytes received over HTTP)
• Average number of peer connections per downloadВ

Starting in Windows 10, version 2004, Get-DeliveryOptimizationStatus has a new option -PeerInfo which returns a real-time list of the connected peers.

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:

set-DeliveryOptimizationStatus -ExpireOn [date time] extends the expiration of all files in the cache. You can set the expiration immediately for all files that are in the «caching» state. For files in progress («downloading»), the expiration is applied once the download is complete. You can set the expiration up to one year from the current date and time.

set-DeliveryOptimizationStatus -ExpireOn [date time] -FileID [FileID] extends expiration for a single specific file in the cache.

You can now «pin» files to keep them persistent in the cache. You can only do this with files that are downloaded in modes 1, 2, or 3.

set-DeliveryOptimizationStatus -Pin [True] -File ID [FileID] keeps a specific file in the cache such that it won’t be deleted until the expiration date and time (which you set with set-DeliveryOptimizationStatus -ExpireOn [date time] -FileID [FileID] ). The file is also excluded from the cache quota calculation.

set-DeliveryOptimizationStatus -Pin [False] -File ID [FileID] «unpins» a file, so that it will be deleted when the expiration date and time are reached. The file is included in the cache quota calculation.

delete-DeliveryOptimizationCache lets you clear files from the cache and remove all persisted data related to them. You can use these options with this cmdlet:

• -FileID specifies a particular file to delete.
• -IncludePinnedFiles deletes all files that are pinned.
• -Force deletes the cache with no prompts.

Work with Delivery Optimization logs

Starting in Windows 10, version 2004:

Get-DeliveryOptimizationLogAnalysis [ETL Logfile path] [-ListConnections]

With no options, this cmdlet returns these data:

• total number of files
• number of foreground files
• minimum file size for it to be cached
• number of eligible files
• number of files with peers
• number of peering files [how different from the above?]
• overall efficiency
• efficiency in the peered files

Using the -ListConnections option returns these details about peers:

• destination IP address
• peer type
• status code
• bytes sent
• bytes received
• file ID

Starting in Windows 10, version 1803:

Get-DeliveryOptimizationLog [-Path ] [-Flush]

If Path is not specified, this cmdlet reads all logs from the DoSvc log directory, which requires administrator permissions. If Flush is specified, the cmdlet stops DoSvc before reading logs.

Log entries are written to the PowerShell pipeline as objects. To dump logs to a text file, run Get-DeliveryOptimizationLog | Set-Content or something similar.

Monitor with Update Compliance

Update Compliance provides you with information about your Delivery Optimization configuration, including the observed bandwidth savings across all devices that used peer-to-peer distribution over the past 28 days.

Delivery Optimization reference

Applies to

Looking for consumer information? See 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. If you just need an overview of Delivery Optimization, see Delivery Optimization for Windows 10 updates. 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.

Delivery Optimization options

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

You will find the Delivery Optimization settings in Group Policy 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
Download mode	DODownloadMode	1511
Group ID	DOGroupID	1511
Minimum RAM (inclusive) allowed to use Peer Caching	DOMinRAMAllowedToPeer	1703
Minimum disk size allowed to use Peer Caching	DOMinDiskSizeAllowedToPeer	1703
Max Cache Age	DOMaxCacheAge	1511
Max Cache Size	DOMaxCacheSize	1511
Absolute Max Cache Size	DOAbsoluteMaxCacheSize	1607
Modify Cache Drive	DOModifyCacheDrive	1607
Minimum Peer Caching Content File Size	DOMinFileSizeToCache	1703
Maximum Download Bandwidth	DOMaxDownloadBandwidth	1607 (removed in Windows 10, version 2004; use Maximum Background Download Bandwidth (in KB/s) or Maximum Foreground Download Bandwidth (in KB/s) instead)
Percentage of Maximum Download Bandwidth	DOPercentageMaxDownloadBandwidth	1607 (removed in Windows 10, version 2004; use Maximum Background Download Bandwidth (in KB/s) or Maximum Foreground Download Bandwidth (in KB/s) instead)
Max Upload Bandwidth	DOMaxUploadBandwidth	1607 (removed in Windows 10, version 2004)
Monthly Upload Data Cap	DOMonthlyUploadDataCap	1607
Minimum Background QoS	DOMinBackgroundQoS	1607
Enable Peer Caching while the device connects via VPN	DOAllowVPNPeerCaching	1709
Allow uploads while the device is on battery while under set Battery level	DOMinBatteryPercentageAllowedToUpload	1709
MaxForegroundDownloadBandwidth	DOPercentageMaxForegroundBandwidth	1803
MaxBackgroundDownloadBandwidth	DOPercentageMaxBackgroundBandwidth	1803
SetHoursToLimitBackgroundDownloadBandwidth	DOSetHoursToLimitBackgroundDownloadBandwidth	1803
SetHoursToLimitForegroundDownloadBandwidth	DOSetHoursToLimitForegroundDownloadBandwidth	1803
Select a method to restrict Peer Selection	DORestrictPeerSelectionBy	1803
Select the source of Group IDs	DOGroupIDSource	1803
Delay background download from http (in secs)	DODelayBackgroundDownloadFromHttp	1803
Delay foreground download from http (in secs)	DODelayForegroundDownloadFromHttp	1803
Delay foreground download cache server fallback (in secs)	DelayCacheServerFallbackForeground	1903
Delay background download cache server fallback (in secs)	DelayCacheServerFallbackBackground	1903
Cache Server Hostname	DOCacheHost	2004
Cache Server Hostname Source	DOCacheHostSource	2004
Maximum Foreground Download Bandwidth (in KB/s)	DOMaxForegroundDownloadBandwidth	2004
Maximum Background Download Bandwidth (in KB/s)	DOMaxBackgroundDownloadBandwidth	2004

More detail on Delivery Optimization settings:

Group ID, combined with Group Download mode, enables administrators to create custom device groups that will share content between devices in the group.

Delivery Optimization uses locally cached updates. In cases where devices have ample local storage and you would like to cache more content, or if you have limited storage and would like to cache less, use the following settings to adjust the Delivery Optimization cache to suit your scenario:

• Max Cache Size and Absolute Max Cache Size control the amount of space the Delivery Optimization cache can use.
• Max Cache Age controls the retention period for each update in the cache.
• The system drive is the default location for the Delivery Optimization cache. Modify Cache Drive allows administrators to change that location.

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

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 Minimum Peer Caching Content File Size.

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

• Maximum Download Bandwidth and Percentage of Maximum Download Bandwidth control the download bandwidth used by Delivery Optimization.
• Max Upload Bandwidth controls the Delivery Optimization upload bandwidth usage.
• Monthly Upload Data Cap controls the amount of data a client can upload to peers each month.
• Minimum Background QoS lets administrators guarantee a minimum download speed for Windows updates. This is achieved by adjusting the amount of data downloaded directly from Windows Update or WSUS servers, rather than other peers in the network.
• Maximum Foreground Download Bandwidth specifies the maximum foreground download bandwidth that Delivery Optimization uses, across all concurrent download activities, as a percentage of available download bandwidth.
• Maximum Background Download Bandwidth specifies the maximum background download bandwidth that Delivery Optimization uses, across all concurrent download activities, as a percentage of available download bandwidth.
• Set Business Hours to Limit Background Download Bandwidth 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.
• Set Business Hours to Limit Foreground Download Bandwidth 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.
• Select a method to restrict Peer Selection restricts peer selection by the options you select.
• Select the source of Group IDs restricts peer selection to a specific source.
• Delay background download from http (in secs) allows you to delay the use of an HTTP source in a background download that is allowed to use P2P.
• Delay foreground download from http (in secs) allows you to delay the use of an HTTP source in a foreground (interactive) download that is allowed to use P2P.

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

• Minimum RAM (inclusive) allowed to use Peer Caching sets the minimum RAM required for peer caching to be enabled.
• Minimum disk size allowed to use Peer Caching sets the minimum disk size required for peer caching to be enabled.
• Enable Peer Caching while the device connects via VPN allows clients connected through VPN to use peer caching.
• Allow uploads while the device is on battery while under set Battery level controls the minimum battery level required for uploads to occur. You must enable this policy to allow upload while on battery.

Download mode

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. Additional technical details for these policies are available in Policy CSP — Delivery Optimization.

Download mode option	Functionality when set
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. 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 attempts 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, with no peer-to-peer caching.
Bypass (100)	Bypass Delivery Optimization and use BITS, instead. You should only select this mode if you use WSUS and prefer to use BranchCache. You do not need to set this option if you are using Configuration Manager. If you want to disable peer-to-peer functionality, it’s best to set DownloadMode to 0 or 99.

Group mode is a best-effort optimization and should not be relied on for an authentication of identity of devices participating in the group.

Group ID

By default, peer sharing on clients using the group download mode 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 do not 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 sub-group 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.

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

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

• 0 = not set
• 1 = AD Site
• 2 = Authenticated domain SID
• 3 = DHCP Option ID (with this option, the client will query 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 Azure Active Directory (AAD) Tenant ID as a means to define groups. To do this set the value for DOGroupIdSource to its new maximum value of 5.

When set, the Group ID is assigned automatically from the selected source. If you set this policy, the GroupID policy will be ignored. The option set in this policy only applies to Group (2) download mode. If Group (2) isn’t set as Download mode, this policy will be ignored. If you set the value to anything other than 0-5, the policy is ignored.

Minimum RAM (inclusive) allowed to use Peer Caching

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 GB, and the default value is 4 GB.

Minimum disk size allowed to use Peer Caching

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 GB, and the default value is 32 GB.

If the Modify Cache Drive policy is set, the disk size check will apply to the new working directory specified by this policy.

Max Cache Age

In environments configured for Delivery Optimization, you might want to set 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. The default Max Cache Age value is 259,200 seconds (3 days). Alternatively, organizations might choose to set this value to «0» which means «unlimited» to avoid peers re-downloading content. When «Unlimited» value is set, Delivery Optimization will hold the files in the cache longer and will clean up the cache as needed (for example when the cache size exceeded the maximum space allowed).

Max Cache Size

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 set this value to 10 on a Windows 10 client device that has 100 GB of available drive space, then Delivery Optimization will use up to 10 GB of that space. Delivery Optimization will constantly assess the available drive space and automatically clear the cache to keep the maximum cache size under the set percentage. The default value for this setting is 20.

Absolute Max Cache Size

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 will override the Max Cache Size setting. The default value for this setting is 10 GB.

Minimum Peer Caching Content File Size

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

Maximum Download Bandwidth

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 will dynamically adjust and optimize the maximum bandwidth used.

Maximum Foreground Download Bandwidth

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 are not throttled even when this policy is set.

Maximum Background Download Bandwidth

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 foreground downloads. However, downloads from LAN peers are not throttled even when this policy is set.

Percentage of Maximum Download Bandwidth

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

Max Upload Bandwidth

This setting allows you to limit the amount 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 set in kilobytes per second (KB/s). The default setting is 0, or «unlimited» which means Delivery Optimization dynamically optimizes for minimal usage of upload bandwidth; however it does not cap the upload bandwidth rate at a set rate.

Set Business Hours to Limit Background Download Bandwidth

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.

Set Business Hours to Limit Foreground Download Bandwidth

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.

Select a method to restrict peer selection

Starting in Windows 10, version 1803, set this policy to restrict peer selection via selected option.
Currently the only available option is 1 = Subnet mask This option (Subnet mask) applies to both Download Modes LAN (1) and Group (2).

Delay background download from http (in secs)

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.

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.

Modify Cache Drive

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 set the value to an environment variable (e.g., %SYSTEMDRIVE%), a drive letter (e.g., D:), or a folder path (e.g., D:\DOCache).

Monthly Upload Data Cap

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

This setting determines whether a device will be allowed to participate in Peer Caching while connected to VPN. Specify «true» to allow the device to participate in Peer Caching while connected via VPN to the domain network. This means the device can download from or upload to other domain network devices, either on VPN or on the corporate domain network.

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

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 set minimum battery level. The recommended value to set if you allow uploads on battery is 40 (for 40%). The device can download from peers while on battery regardless of this policy.

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. Specify the custom DHCP option on your 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.

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.