ConfigMgr / MECMdecimal -2016410105
Fix Intune Error 0x87D00607: The client could not find the application content on any distribution point it can reach (content not found).
Open the log below first. It is the quickest way to confirm which of the causes applies before you change anything.
CAS.log
Folder: C:\Windows\CCM\Logs\
Also check: LocationServices.log · ContentTransferManager.log · DataTransferService.log
Root causes
- The content was never distributed to a distribution point that serves the client, or the distribution failed.
- The client is outside every boundary group, or the boundary group has no content source for its site.
- The distribution point is unreachable from the client: DNS, firewall, certificate or HTTPS mode mismatch.
- The content version on the distribution point is older than the one the deployment now references.
Step-by-step remediation
- In CAS.log find the content request and the result. LocationServices.log shows which distribution points were returned.
- In the console open Monitoring > Distribution Status > Content Status for the application and confirm it is on the expected distribution points.
- Check the client IP is inside a boundary group with a content source, and that fallback is set the way you intend.
- Browse to the distribution point content URL from the client to rule out DNS, firewall and certificate issues.
- Redistribute or update the content, then run the Machine Policy Retrieval cycle and retry the deployment.
For the full diagnosis around this error, read ConfigMgr app failing: content or detection?.
Keep patching failures out of the queue
Repeat update and client failures are cheaper to prevent than to chase. Compare the options that take app packaging and upkeep off your task list, from Enterprise App Management to PSADT.
Compare Win32 packaging toolsRelated Error Codes in This Category
Other ConfigMgr / MECM errors with their own runbooks.
- 0x87D00321The install did not finish inside the "Maximum allowed run time", so Configuration Manager timed it out and failed the deployment.
- 0x8004100EA WMI namespace the client needs is missing (WBEM_E_INVALID_NAMESPACE), typically root\ccm, so the ConfigMgr client is broken.
- 0x87D00692A higher authority, normally a domain Group Policy, overrides the Windows Update settings ConfigMgr tries to apply, so software update scans fail.