Microsoft defines Configuration Manager error 0x87D00607 as “Content not found.” It means the client cannot find usable application content; first confirm the content is distributed to a distribution point the client can use, then check boundary-group mapping and follow the client logs to see whether it received and downloaded from a content location.
The error identifies a content-availability problem, but does not by itself identify the cause. Check deployment status and the exact code before changing the installation command or client cache.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Mastering System Center Configuration Manager | $40.83 | Buy on Amazon |
| 2 |
|
Troubleshooting System Center Configuration Manager | $50.99 | Buy on Amazon |
1. Confirm the deployment status and exact error
In the Configuration Manager console, go to Monitoring → Deployments and inspect the affected deployment. An Unknown status can mean the client has not received policy; In Progress can indicate that content is still downloading. Confirm the client reports the exact error and review the log entries around the failure.
Microsoft distinguishes 0x87D00607, “Content not found,” from 0x87D01107, which indicates that locations were obtained but could not be accessed, and from cache or disk-capacity errors 0x87D01201 and 0x87D01202. Use the code and logs to identify which stage failed.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errors#1 Best Overall
2. Confirm the application content is distributed
- In the console, go to Monitoring → Distribution Status → Content Status.
- Find the application deployment type’s content and review its distribution status on the relevant distribution points.
- Confirm that at least one distribution point the client can use has the content successfully distributed.
- If distribution failed or is incomplete, investigate and correct the distribution problem before troubleshooting the client cache.
For site-side distribution-point problems, Microsoft identifies DistMgr.log and SMSdpmon.log as useful logs.
3. Check the client’s boundary and boundary-group path
- Confirm the client’s current network location is covered by the intended configured boundary.
- Confirm that boundary belongs to the expected boundary group.
- Confirm that a distribution point containing the application content is associated with a boundary group the client can use.
- Review the boundary group’s neighbor or default site boundary-group relationships and fallback delays if the client is expected to use those sources.
Do not assume that every distribution point is automatically available to every client. Microsoft recommends checking boundary and boundary-group configuration when application content cannot be downloaded.
If the deployment is intended to allow a client to use a distribution point from a neighbor or default site boundary group, review the deployment type’s Content tab. Where appropriate for your environment, set the deployment option to Download content from distribution point and run locally. Check the intended behavior before changing this setting.
4. Trace the content request in client logs
Use the content’s unique ID to correlate entries. The download flow checks the client cache, requests distribution-point locations when needed, creates a transfer job after a location is returned, and then transfers the content.
| Log | What to check |
|---|---|
| CAS.log | Cache checks, content requests, and transfer initiation. |
| LocationServices.log | Distribution-point location requests and responses. |
| ContentTransferManager.log | Persisted content locations and transfer-job activity. |
| DataTransferService.log | Download activity and transfer progress. |
If ContentTransferManager.log reports Received empty location update, the client may have received no usable distribution-point location and remain at 0% download. Investigate content availability and boundary-group configuration. If a location is returned, follow the transfer through ContentTransferManager.log and DataTransferService.log to determine whether the client could reach the source and complete the download.
5. Distinguish missing content from access and cache problems
| Evidence | What it suggests | Next check |
|---|---|---|
| No usable location returned | Content availability or boundary-group mapping problem | Distribution status, boundary membership, group associations, and configured fallback |
| A location is returned but cannot be reached | Access or transfer problem; Microsoft associates 0x87D01107 with inaccessible locations | Distribution-point access and the transfer entries in ContentTransferManager.log and DataTransferService.log |
| 0x87D01201 or 0x87D01202 | Available disk space or client-cache capacity problem | Client storage and cache settings |
These adjacent errors are not the same as 0x87D00607. Use the exact reported code rather than treating every download failure as a cache problem.
6. Refresh policy if the client has not received the deployment
If deployment status is Unknown or the client has not received the deployment policy, manually refresh client policy and verify that the device receives the deployment. After correcting content distribution or boundary configuration, monitor the client logs again as it requests the content.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.FAQ
What does SCCM error 0x87D00607 mean?
Microsoft defines it as “Content not found.” The client cannot find usable application content, so check distribution status, boundary-group mapping, and the client’s content-location logs.
What should I check first?
Confirm the exact error and deployment status, then verify that the content is successfully distributed to a distribution point the client can use.
Why does ContentTransferManager.log show “Received empty location update”?
The client may have received no usable distribution-point location. Check whether the content is available and whether the client’s boundary and boundary-group configuration provide an appropriate source.
How is 0x87D00607 different from 0x87D01107?
Microsoft labels 0x87D00607 “Content not found.” Error 0x87D01107 indicates that locations were obtained but could not be accessed, so check the selected source and transfer logs.
Can a cache problem cause this error?
Microsoft lists 0x87D01201 and 0x87D01202 for disk-space or client-cache capacity problems. Those are distinct from 0x87D00607; confirm the exact code before changing cache settings.
Quick Recap
Sources
- Microsoft: Configuration Manager application installation error reference
- Microsoft: Troubleshooting tips for application deployments
- Microsoft: Application download in Configuration Manager
- Microsoft: Boundary groups and distribution points
- Microsoft: Manage distribution points
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
