Set Delivery Optimization

What the Delivery Optimization configuration Worklet does

This Automox Worklet™ configures Windows Update Delivery Optimization settings on Windows 10 and Windows 11 endpoints without requiring Group Policy Object distribution. The Worklet applies registry-based settings that control how endpoints download updates and Microsoft Store applications.

The Worklet supports configuration of multiple delivery optimization parameters including download mode, group identification, peer caching restrictions, cache location, and cache retention policies. This allows administrators to balance bandwidth savings with network characteristics and organizational requirements across their endpoint fleet.

Delivery Optimization enables endpoints to share downloaded updates and applications with peers on the local network or private groups, reducing consumption of internet bandwidth while maintaining a reliable distribution source for critical system updates.

Why configure delivery optimization settings

Windows Update Delivery Optimization reduces internet bandwidth consumption in environments with multiple endpoints by enabling peer-to-peer sharing of downloaded content. Without configuration, endpoints use default settings that may not align with your network capacity or organizational policies.

Organizations benefit from centralized delivery optimization settings to control costs, improve update delivery reliability in branch offices with limited connectivity, and restrict peer caching when operating over VPN connections. Consistent configuration across your endpoint fleet maintains predictable behavior and optimized performance during critical patch windows.

How delivery optimization configuration works

1. Evaluation phase: The Worklet compares current delivery optimization settings on the endpoint against the parameters you specify. It checks values in the Windows Registry at HKLM:\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization, including download mode, group ID, cache settings, and peer caching restrictions. If any setting is non-compliant, evaluation exits with code 1 to trigger remediation.

2. Remediation phase: The Worklet creates or updates registry keys in HKLM:\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization to apply your specified settings. It configures parameters such as DODownloadMode, DOGroupID, DOMaxCacheSize, DOModifyCacheDrive, and additional Windows 11 settings like DOAbsoluteMaxCacheSize and DOMinRAMAllowedToPeer. Windows then applies these policies to control delivery optimization behavior.

Delivery optimization configuration requirements

• Windows 10 Pro, Enterprise, or Education editions (or Windows 11 equivalents)

• Local administrator or system privileges to write to Windows Registry

• PowerShell execution enabled on the endpoint

• Optional: For DownloadMode 2 or 3 with peering, network connectivity and DNS resolution required

• Optional: For GroupID customization, GUID format required (example: {944fa07e-ecad-49f4-8dd1-5d4b93578b74})

Expected delivery optimization behavior after remediation

After the Worklet applies delivery optimization settings, Windows endpoints will use the configured download methods and cache policies for all update and Microsoft Store application distribution. Your specified settings persist across endpoint reboots and remain in effect until modified by another policy or Worklet. You can verify this change through the Automox Activity Log or by checking the endpoint configuration directly.

Download mode determines whether endpoints download directly from Microsoft servers (mode 0), participate in peer caching behind NAT (mode 1), peer across private groups (mode 2), or disable delivery optimization entirely (mode 100). Cache configuration controls where delivery optimization stores downloaded content, how large the cache grows, and how long cached files persist. VPN peer caching restrictions prevent bandwidth leakage when endpoints connect over VPN links, while minimum disk and RAM requirements maintain peer caching only occurs on endpoints with sufficient resources.

How to validate set delivery optimization changes

1. Run this Worklet on a pilot Windows endpoint and review evaluation output for set delivery optimization.

2. Confirm Automox activity logs show successful completion and exit code 0.

3. Verify endpoint state using checks aligned to evaluation script logic, such as Compare-DeliveryOptimization, Get-Help, Get-Command.

4. Validate remediation effects from script operations such as Set-DeliveryOptimization, Get-Help, Test-Path, then rerun evaluation for compliance.