Reading Intune logs: where the package fails
From the Management Extension log to the installer log: which file shows which step and how to narrow down the cause.
Packaging knowledge
Versions, supersedence, logs and bandwidth: what happens after rollout and how to narrow down failures.
An update is not a new package next to the old one; it replaces it. If both are assigned at the same time, order decides, not version. Without that decision you get devices with both variants installed.
Supersedence describes which package replaces which. It needs a clear version number inside the package and a detection rule that recognises it. Without both, Intune cannot tell whether the new package has arrived.
On the client there is the Intune Management Extension log, the vendor installer log, and the package log from the PSADT run. The error is rarely where you look first: a failed download looks different from failed detection.
When a site downloads the same package repeatedly, that is a delivery problem, not an install problem. Delivery Optimization can use devices in the same network as a source. Whether it works depends on configuration, not on package size alone.
Four things: packages without a successful completion, devices with contradictory detection, versions nobody assigns anymore, and download anomalies at individual sites. Not a big report — a look at the outliers.
---
From the Management Extension log to the installer log: which file shows which step and how to narrow down the cause.
How a new version replaces the old one, why order matters and what happens when both are assigned at once.
Why 30 devices at one site should not download the same package 30 times, and which setting prevents it.