Configuration Manager OSD: Showing the Distribution Point in Use

Slow SCCM OS deployments can sometimes trace back to a task sequence pulling content from the wrong distribution point — for example, falling back to a distant DP when the intended local one isn’t working correctly, without any obvious error to flag it.

Diagnosing It

Task sequences don’t show which distribution point content came from in the default UI, so this needs to be surfaced deliberately — typically by adding a custom step (a “Run PowerShell Script” or “Run Command Line” step) early in the sequence that reads the relevant task sequence environment variables and writes the resolved content source location to a log file or a custom background/status message, so you can see at a glance which DP actually served the content for that run. Community write-ups (like the one linked in this post’s resources) walk through the specific variables and scripting needed to surface this — well worth reviewing directly, since the exact variable names and approach can shift slightly between ConfigMgr versions.

Once You’ve Identified It

If you find deployments are falling back to a remote DP unexpectedly, check that DP’s boundary group configuration and the health of the “local” DP it should be preferring — a DP reporting unhealthy in content status, or a boundary group misconfiguration, are the most common root causes of this kind of silent fallback.

Still the Right Approach in 2026

The custom logging technique above remains a valid convenience wrapper, but it’s worth knowing that smsts.log has always natively recorded which distribution point served content during OSD — look for “Looking for next content source location” and the subsequent successful download entries, which show the DP’s UNC or HTTP path directly. Reading smsts.log via CMTrace or OneTrace is the standard, still-current way to confirm this without adding a custom task sequence step, if you’d rather not build the extra scripting. The sccmguru.wordpress.com post linked in the Resources below is still live as of 2026, for anyone who wants the full original walkthrough.

Resources

• OSD
• Show DP in use during Task Sequence