Packaging knowledge

Packages in production: versions and logs

Versions, supersedence, logs and bandwidth: what happens after rollout and how to narrow down failures.

Replacing instead of overwriting

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.

Versions and supersedence

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.

Logs on three levels

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.

Bandwidth and Delivery Optimization

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.

What to check monthly

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.

---

02

Supersedence and versioning

How a new version replaces the old one, why order matters and what happens when both are assigned at once.