Create a Device Level Windows Delivery Optimization Policy

This policy centrally controls how Windows devices download updates, applications, and Microsoft content. By leveraging secure peer-to-peer (P2P) distribution and cache management, this policy reduces internet bandwidth consumption, accelerates update delivery, and minimizes disruption for end users. Standardizing these settings across your Windows fleet strengthens security posture, improves productivity, and ensures consistent behavior in remote and bandwidth-constrained environments.

Prerequisites

• Devices must be enrolled in Windows MDM (Mobile Device Management).
• Target devices must be running Windows 10 or 11 version 1607 [10.0.14393] and later. This policy is supported on the following Windows editions:
  • Windows Pro
  • Windows Enterprise
  • Windows Education
  • Windows SE
  • IoT Enterprise
  • IoT Enterprise LTSC
• Devices must have reliable network connectivity to reach the following resources:
  • Microsoft Update, content delivery services, and any configured Microsoft Connected Cache (MCC) servers
  • JumpCloud services see JumpCloud Agent Networking and Port Requirements to learn more.
• For more information on device compatibility, see Agent Compatibility, System Requirements, and Impacts.

Considerations

• This policy is applied immediately to the applicable Windows devices.

Creating the Policy

To create a Delivery Optimization policy for Windows devices, do the following:

Selecting the Policy Template

1. Log in to the JumpCloud Admin portal.

2. Go to Device Management > Policy Management. The Policy Management page is displayed.
3. On the Policy Management page, click +Add New.
4. Select Device Policy to assign the policy to devices and device groups. On the New Device Policy page:
   • Select the Windows tab.
   • Search and select the policy name and click Configure. The Details tab of the policy is displayed.
   • On the Details tab, configure the required policy configuration settings.
   • (Optional) In the Policy Name field, enter a new name for the policy or keep the default. Policy names must be unique.
   • (Optional) In the Policy Notes field, enter details such as creation date of the policy, and information on testing and deployment of the policy.

Configuring the Policy

In the Settings section, you can configure the policy settings:

• Download Mode – Enable P2P sharing and define the scope for content downloads. The supported values include:
  • HTTP only
  • HTTP blended with peering behind the same NAT
  • HTTP blended with peering across a private group
  • HTTP and peering across the internet
  • HTTP only, no peering, no use of the Delivery Optimization cloud service.
• Group ID – Specify a custom GUID that defines a private peer group. Configure this when Download Mode is set to a group-based setting to tightly control which devices can share content.
• Group ID Source – Define how each client determines its peer group (for example, based on Entra ID Tenant, domain, or a DHCP option). Select the option that best matches your identity and network design.
• Cache Server Hostname – Specify the FQDN(s) or IP addresses of Microsoft Connected Cache (MCC) servers (for example, cachehost1.contoso.com,cachehost2.contoso.com. Configure multiple hosts to provide redundancy for content downloads.
• Cache Host Source –Define how devices dynamically discover MCC servers (for example, via DHCP Option 235), simplifying configuration in large or segmented networks.
• Allow VPN Peer Caching – By default, Delivery Optimization does not use peering over VPN. Enable this option to allow devices connected via VPN to participate in peer caching, if your security policies permit.
• Delay Cache Server Fallback (Background) (seconds) – Specify how long a device waits before falling back to standard HTTP sources when an MCC server is unavailable for background downloads.
• Delay Cache Server Fallback (Foreground) (seconds) – Specify the delay before falling back to HTTP for foreground (user-initiated) downloads when the MCC server cannot be reached.
• Maximum Download Bandwidth (KB/s) – Define the maximum aggregate background download bandwidth (in Kbps) that Delivery Optimization can consume, helping to protect network performance during unattended updates. Leave this blank to let Windows manage this dynamically, or set a cap (e.g., 1000) to throttle updates during business hours.
• Maximum Upload Bandwidth (KB/s) – Controls the maximum upload bandwidth (in Kbps) used to serve content to peers, limiting the impact of peering on upstream links.
• Delay Background Download From HTTP (seconds) – Configure how long a background download waits before using HTTP, allowing time for peers to be discovered and reducing reliance on the internet.
• Delay Foreground Download From HTTP (seconds) – Configure how long a foreground download waits before using HTTP, balancing user experience with opportunities to source content from peers.
• Min Background QoS (KB/s) – Helps optimize peer connections by measuring bandwidth during background downloads. If measured speed falls below the configured threshold, the device can combine peer and HTTP sources to maintain acceptable performance.
• Monthly Upload Data Cap – Sets the maximum amount of data (in GB) a device may upload to peers each month. A value of 0 can be used to specify an unlimited upload cap.
• Min Battery Percentage Allowed to Upload – Specifies the minimum battery level (percentage) required before a device is permitted to upload content to peers, protecting mobile devices from excessive battery drain.
• Absolute Max Cache Size (GB) – Specify a hard limit (in GB) for the Delivery Optimization cache. When the cache approaches this limit, older content is automatically purged to stay within the configured capacity.
• Max Cache Age (Seconds) – Specify the maximum age (in seconds) that content can remain in the cache before it becomes eligible for deletion, ensuring stale content is automatically removed.
• Modify Cache Drive – Allows you to change the drive letter or path (for example, D:) where Delivery Optimization stores its cache, which is useful when redirecting cache to a dedicated or higher-capacity volume.

Applying the Policy

• (Optional) Select the Policy Groups tab. Select one or more policy groups where you want to add this policy. 
• Select the Device Groups tab. Select one or more device groups where you want to apply this policy to. For device groups with multiple OS member types, the policy only applies when a user logs into a supported Windows device that is enrolled in MDM.
• Or, select the Devices tab. Select one or more devices where you want to apply this policy.
• Click Create Policy. A success message is displayed indicating the completion of policy creation.

Viewing Policy Status

1. Select the Status tab.
2. To see the last Result Log for a device where this policy is applied, click view.