When Microsoft releases monthly cumulative updates or major feature updates, branch office internet links frequently suffer severe bandwidth saturation. If hundreds of corporate laptops and workstations concurrently download a 4 GB update payload directly from Microsoft Content Delivery Networks (CDNs), external WAN bandwidth collapses. Legacy Background Intelligent Transfer Service (BITS) mechanisms mitigated this somewhat, but offered no native mechanism for workstations to share downloaded payloads with neighboring PCs on the local network.
Windows 11 addresses this bandwidth bottleneck through Delivery Optimization (DO). Functioning as a cloud-coordinated peer-to-peer (P2P) distribution engine, Delivery Optimization allows PCs on the same local subnet, Active Directory site, or private group to source Windows updates, Microsoft Store packages, and Microsoft 365 apps directly from neighboring machines. This guide provides an in-depth operational breakdown of configuring Delivery Optimization modes, enforcing peer caching boundaries, setting granular bandwidth throttles, and monitoring peer telemetry in Windows 11.
Architectural Mechanics: How Delivery Optimization Distributes Payloads
Delivery Optimization coordinates content distribution using a hybrid cloud-peer architecture:
| Component | Network Layer | Technical Functionality |
|---|---|---|
| DO Cloud Service | HTTPS (Port 443) | Discovers available peers, validates file cryptographic hashes, and issues dynamic swarming tokens to client devices. |
| Peer Transport | TCP/UDP (Port 7680) | Streams encrypted payload chunks directly between local workstations on the LAN using peer-to-peer sockets. |
| Local Cache Store | C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Microsoft\Windows\DeliveryOptimization\Cache |
Stores validated update chunks; automatically evicts old packages when drive capacity drops beneath configured safety buffers. |
| Microsoft Connected Cache (MCC) | HTTP/HTTPS Proxy | Optional dedicated enterprise cache container (hosted on Windows Server or Linux) serving as a local fallback source before querying internet CDNs. |
Delivery Optimization Download Modes (DODownloadMode)
The core behavior of Delivery Optimization is governed by its Download Mode setting:
| Mode Value | Policy Identifier | Operational Behavior | Recommended Environment |
|---|---|---|---|
0 |
HTTP Only | Disables peer caching entirely. All downloads pull directly from Microsoft CDN servers or WSUS. | High-security isolated air-gapped networks. |
1 |
LAN (Peering) | Peers strictly within the same local area network / public IP NAT boundary. | Small-to-medium branch offices without complex subnetting. |
2 |
Group | Peers strictly within a designated Active Directory Site, domain, or custom Group ID token. | Recommended Enterprise Standard. Prevents WAN link saturation across multiple corporate campuses. |
3 |
Internet | Peers with both local LAN devices and third-party peers across the public internet. | Consumer home environments; avoid in corporate enterprise networks. |
99 |
Simple Mode | Bypasses DO cloud coordination. Downloads strictly via HTTP from internal WSUS or MCC servers. | Environments where endpoints cannot access public internet endpoints. |
100 |
Bypass | Reverts fully to legacy BITS protocols. | Legacy compatibility only. |
Step 1: Configuring Delivery Optimization in Windows 11 GUI
For standalone or unmanaged devices, configure basic peer caching via the Windows Settings interface:
- Open Settings > Windows Update > Advanced options.
- Scroll down to the Additional options section and click Delivery Optimization.
- Toggle Allow downloads from other PCs to On.
- Select your preferred scope:
- Devices on my local network: Confines peering strictly to machines sharing your local NAT router.
- Devices on the internet and my local network: Permits broader peer sharing across external networks.
- Click Advanced options to set absolute or percentage download bandwidth limits for foreground (user-initiated) and background downloads.
Step 2: Enforcing Enterprise Group Policy & Intune Configurations
In enterprise corporate environments, manage Delivery Optimization centrally via Group Policy (ADMX) or Microsoft Intune:
Key Group Policy Paths:
Navigate to: Computer Configuration > Administrative Templates > Windows Components > Delivery Optimization
| Policy Name | Registry Path | Recommended Enterprise Value |
|---|---|---|
| Download Mode | DODownloadMode |
Set to 2 (Group Mode) to restrict peer discovery to defined sites. |
| Group ID | DOGroupId |
Assign a GUID or corporate token string to group specific campus devices. |
| Restrict Peer Selection By | DORestrictPeerSelectionBy |
Set to 1 (Subnet mask) to ensure peering stays on high-speed LAN switches. |
| Maximum Background Download Bandwidth | DOMaxBackgroundDownloadBandwidth |
Set percentage limit (e.g., 30%) or absolute limit in KB/s. |
| Minimum RAM required to enable Peering | DOMinRAMAllowedToPeer |
Set to 4 (GB) to prevent low-spec machines from thrashing memory. |
Step 3: Auditing Delivery Optimization Performance via PowerShell
Windows 11 includes native cmdlets to audit peer efficiency, download savings, and active socket connections:
1. Inspecting Lifetime Bandwidth Savings:
# Query Delivery Optimization performance snapshot
Get-DeliveryOptimizationPerfSnap | Select-Object FilesDownloaded, TotalBytesDownloaded, `
BytesFromPeers, BytesFromHttp, `
PercentPeerCachingThe PercentPeerCaching metric demonstrates how much external WAN bandwidth was saved by pulling packages from local peers instead of Microsoft internet CDNs.
2. Monitoring Active Peer Connections in Real Time:
While an update is actively downloading, inspect connected peers and transmission rates:
# View active download sessions and peer status
Get-DeliveryOptimizationStatus | Format-Table FileId, FileSize, PredefinedCaller, `
DownloadMode, BytesFromPeers, BytesFromHttp, `
StatusTroubleshooting Common Delivery Optimization Faults
| Observed Issue | Root Cause | Diagnostic & Remediation Step |
|---|---|---|
PercentPeerCaching remains at 0%; all traffic pulls from HTTP |
Inbound TCP/UDP port 7680 blocked on client firewalls or network classified as Public | Ensure Windows Firewall permits incoming connections on port 7680. Check connection profile with Get-NetConnectionProfile; peering is disabled on Public networks. |
| Delivery Optimization exhausts local C: drive disk space | Stale update payloads lingering in DO cache directory | Run Disk Cleanup or execute in PowerShell: Clear-DeliveryOptimizationCache. Configure policy Max Cache Size (percentage) to cap maximum disk usage. |
| Peering across Wi-Fi networks causes severe access point channel congestion | Full broadcast peering flooding wireless access points with high UDP/TCP packet churn | Set policy Enable Peer Caching while on Battery to Disabled. Configure Restrict Peer Selection By to Subnet mask to isolate peering to wired LAN backbones. |
Updates fail with error 0x80d02002 or 0x80d03805 |
Delivery Optimization service (DoSvc) corrupted or proxy blocking DO cloud endpoints | Ensure enterprise proxy allows traffic to *.prod.do.dsp.mp.microsoft.com and *.dl.delivery.mp.microsoft.com. Restart service via net stop dosvc && net start dosvc. |
Operational Governance and Best Practices
- Standardise on Group Mode (Mode 2) for Multi-Site Fleets: Deploying Mode 1 (LAN) across multi-homed corporate routers can cause cross-subnet WAN bleed. Mode 2 ensures traffic never crosses expensive inter-campus MPLS/VPN tunnels.
- Leverage Microsoft Connected Cache (MCC): For branch offices with low client density where peers are frequently powered off or mobile, deploy an MCC endpoint. Workstations pull from the persistent local MCC server before venturing out to public internet CDNs.
- Protect Cellular & Metered Connections: Verify that the policy Allow Upload while on Metered Networks is strictly set to Disabled to prevent mobile field workers from incurring substantial data overage fees while uploading updates to colleagues.