Delivery Optimization settings in Intune, one by one.

DoctorDO’s reading The two defaults describe different things: what the client does with no policy, and the value the CSP reports. Get-DOConfig shows what is in force.

Group ID and its source apply in Group mode only, DOGroupId overrides DOGroupIdSource, and a source outside 0 to 5 is ignored.⁷ The full guide is Group IDs, in the demo.

While a device waits for a peer, the download appears stuck to the user.⁵ The configuration guide says the HTTP and cache-server timers both start with the download and aren’t additive;⁸ the reference says the HTTP delay applies first.⁷ Under both readings a cache delay above the HTTP delay gives the cache its time.

Autopilot is the exception: Microsoft says to set the foreground HTTP delay to 0 and the background one to 0 or a low value.¹⁰ DoctorDO’s reading A provisioning profile apart from the everyday one keeps both right; see Intune Win32 apps and Delivery Optimization.

In Intune, open the profile and select View report; per-setting status counts the devices that applied each setting, or hit a conflict or an error, and Devices > Monitor > Assignment failures lists the failures.¹

On the device, Get-DOConfig -Verbose lists each policy with its value and the provider that set it, such as Mdm Provider, or Default Provider for the platform default. Get-DODownloadMode gives the mode in use, and Get-DeliveryOptimizationStatus each download’s.¹¹

# Every Delivery Optimization policy in force, and the provider that set it
Get-DOConfig -Verbose

# The download mode the device is using now
Get-DODownloadMode

# Each current download, with its mode and where its bytes came from
Get-DeliveryOptimizationStatus |
  Select-Object FileId, DownloadMode, Priority, BytesFromPeers, BytesFromHttp

The CSP names HKLM\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization as the registry key behind each setting’s Group Policy mapping.⁶ DoctorDO’s reading Values Intune sets aren’t necessarily there, so an empty key doesn’t mean no policy. Beside that key and Get-DOConfig, DoctorDO’s collector reads HKLM\SOFTWARE\Microsoft\PolicyManager\current\device\DeliveryOptimization, where MDM values are seen but which Microsoft doesn’t document, and shows each device’s values with who set them. What is collected lists the keys.

DoctorDO is an independent community project, in preview, and changes no Delivery Optimization setting on your devices. When the settings are right and peering still fails, the troubleshooting checklist goes on from here.

See a device’s settings in the demo