Start with the client path
Map a device from boundary group to preferred distribution point before changing content. Confirm the boundary is assigned to the expected group, the DP is protected for that group, and the content is actually distributed to it. A healthy management point does not imply a healthy content path.
Validate content at the source
When a package is revised, use a new source version and redistribute intentionally. Avoid editing files underneath an existing source directory because clients can hold a different hash expectation than the administrator sees on disk.
Get-CMContentDistribution -PackageId 'ABC00123' |
Select-Object DistributionPointName, State, SourceVersion, LastUpdateDateTimeRecover without guesswork
Read DataTransferService and ContentTransferManager logs together. Compare the client’s location, requested content version, and DP state. Repair the smallest broken link first, then trigger a policy refresh and content evaluation.
Operational checklist
- Verify boundary group and preferred DP assignment.
- Check content state and source version.
- Read client transfer logs before redistributing.
- Measure recovery time for remote sites.