sccm 0x87d00607 update content download failed

TL;DR

0x87d00607 means content location failed: the client asked for the package and no distribution point in its boundary group could serve it, or the content was never distributed. Check the client boundary and boundary group in LocationServices.log, confirm the content is distributed to that DP, and check the Allow clients to use a fallback source setting.

sccm 0x87d00607 update content download failed

Use this when

• Software Center downloads fail immediately with 0x87d00607.
• Failures affect one site or subnet while other sites install fine.
• A new deployment fails everywhere it was not explicitly distributed.

Not for this skill when

• Content downloads and then install fails. That is an install-phase code, not content location.
• The client is not assigned to any site. Fix site assignment first.

Steps

1. Read LocationServices.log on a failing client and find the boundary group and DP list returned for its subnet. Verify: the client is matched to the expected site and DP
2. In the console, check the package content status for that distribution point. Verify: content shows distributed and Success, not In Progress or Error
3. If the subnet is missing, add it to the correct boundary and boundary group. Verify: the client next policy cycle resolves the new DP
4. Enable the boundary group option to allow peer downloads or fallback to the default site boundary group if your design permits. Verify: the setting is saved on the boundary group relationship
5. Refresh machine policy on the client and retry the deployment. Verify: ContentTransferManager.log shows a download job starting from a named DP

Variant phrasings

sccm content not found on distribution point 0x87d00607

The full root-cause phrasing.

0x87d00607 boundary group no dp available

The boundary phrasing for site-specific failures.

software center download failed content location

The symptom phrasing from the user side.

Compatibility: Compatibility: Configuration Manager current branch with boundary groups; IP subnet, range, and AD site boundaries.

Why it happens

Content location is a two-sided match: the package must be on a DP, and that DP must be offered to the client based on its boundary. Either side failing produces the same client code, which is why the client log view of which DPs were offered is the fastest discriminator between a distribution gap and a boundary gap.

Edge cases / pitfalls

• VPN clients often fall into an unassigned boundary; give the VPN range its own boundary group or a fallback rule.
• A DP in provisioning or maintenance mode will not serve content even though it appears in the console.
• Cloud management gateway content needs the package enabled for the CMG, a separate distribution target.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstdjb6kwjvBujf3RynDMASg