Delivery Optimization for packages

What Delivery Optimization does

Delivery Optimization is an HTTP downloader that can additionally fetch packages from other devices on the network or from a cache server. Peer-to-peer is optional. If neither peer nor cache has the content, it falls back to the normal HTTP source.

That matters for Intune Win32 apps: they are among the content types Delivery Optimization can use.

Peer cache at a site

Devices behind the same NAT can serve each other. In Windows client editions this local sharing is enabled by default; Group Policy or MDM can change it. The effect: a site downloads a package once and distributes it locally.

Limits at small sites

Three devices are not a swarm. If one device downloads the package and the others arrive later, the cache may already be gone. For small sites the configuration is often worth less than for offices with 30 or more devices.

Measure instead of estimating

Whether it works is not shown by package size but by distribution: how often was the same file downloaded from the internet, how often from peers? Delivery Optimization reporting provides those numbers. Without measurement, “we enabled it” is an assumption.

Interaction with Intune

Delivery Optimization replaces neither assignment nor detection. It only changes where the bytes come from. A package installed twice because of wrong detection is still downloaded twice — just faster.

---