Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | SYNCMGR_E_SYNC_FAILED (0x87D00607) | CAS.log, DataTransferService.log | -> Content location request failed |
| Affected OS build | Windows 10 / Windows 11 | ||
| Registry key involved | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\ClientSDK\BITSDownloadThrottle | Registry Editor | -> Check if throttling is enabled |
| Relevant service/endpoint URL | http(s)://<DP FQDN>/SMS_DP_SMSPKG/ | -> Ensure IIS and virtual directory are configured correctly | |
| Log line signature | Content location request failed (0x87D00607) | CAS.log, DataTransferService.log |
Log Files to Check
C:\Windows\CCM\Logs\CAS.logC:\Windows\CCM\Logs\DataTransferService.log
What This Error Actually Means
The error code 0x87D00607, also known as SYNCMGR_E_SYNC_FAILED, is raised by the Microsoft Configuration Manager (SCCM) Content Access Service (CAS). It indicates that a client was unable to download content from any of its assigned distribution points. This can be due to network issues, misconfigurations on either the client or server side, or corruption in the content itself. The error typically appears when an application installation or software update fails within Software Center and is recorded both in the SCCM client logs and in the user interface as a failed status for the specific action.Affected Versions and Scope
This issue affects clients running Windows 10 and Windows 11 operating systems. The error can occur across different builds of these OSes, but it is particularly prevalent when SCCM's Content Access Service (CAS) is involved in content delivery operations such as software updates or application installations. It does not affect older versions like Windows 7 or 8.x unless they are running a version of Configuration Manager that supports the CAS component.Where To Look First: Logs and Event IDs
To diagnose this issue, start by examining the following logs: -C:\Windows\CCM\Logs\CAS.log: This log file contains detailed information about content requests made by clients. Search for lines containing '0x87D00607' and 'Content location request failed (0x87D00607)' to identify the specific actions that have been failing.
- C:\Windows\CCM\Logs\DataTransferService.log: This file provides information about BITS download jobs. Look for entries with 'TSS Error' and '0x87D00607'.
- On the distribution point, check %ProgramFiles%\SMS_CCM\Logs\SMSDPProv.log for errors related to content distribution.
Event IDs 12345 and 12346 in the Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin log can also provide additional context regarding failed content requests. Use Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50 to retrieve recent events.
Root Causes
Distribution Point Misconfiguration or Unavailability
This issue often stems from problems with the distribution points. Verify that the IIS server on the DP is running and that the SMS_DP_SMSPKG virtual directory exists and is correctly configured. You can check this by navigating tohttp(s):///SMS_DP_SMSPKG/ .
Content Corruption or Hash Mismatch
If content on a distribution point is corrupt, the client will fail to download it due to hash mismatches. Check the SMSDPProv.log for errors related to package IDs and ensure that the content has been correctly redistributed.BITS Service Issues
The Background Intelligent Transfer Service (BITS) may be disabled or throttled by Group Policy settings. UseGet-Service BITS | Select Status, StartType to check its status and start type. If necessary, enable it with Set-Service BITS -StartupType Manual; Start-Service BITS.
Boundary Group Misconfiguration
Clients must be assigned to a boundary group that includes an accessible distribution point. Navigate to the SCCM console > Administration > Hierarchy Configuration > Boundary Groups and verify that your client's IP address or AD site is within such a boundary.Disabling BITS service on clients can cause them to lose connectivity with the management server, leading to further issues.
Fix Procedure
- Check Distribution Point Configuration: Ensure that IIS and the SMS_DP_SMSPKG virtual directory are properly set up. Use
http(s)://to test./SMS_DP_SMSPKG/ - Verify BITS Service Status: Run
Get-Service BITS | Select Status, StartType. If the service is not running or disabled, useSet-Service BITS -StartupType Manual; Start-Service BITS. - Redistribute Content to DP: In the SCCM console > Monitoring > Distribution Status > Content Status, find the failing package and redistribute it using the 'Distribute Content' option.
- Check Boundary Group Assignment: Navigate to SCCM console > Administration > Hierarchy Configuration > Boundary Groups. Ensure that your client's IP or AD site is within a boundary group containing an accessible DP.
Error Code Variants
| Error Code | Meaning |
|---|---|
| 0x87D00608 | SYNCMGR_E_INVALID_CONTENT (Invalid content or hash mismatch) |
| 0x87D00609 | SYNCMGR_E_NO_DISTRIBUTION_POINT (No distribution point available for the requested content) |
Verification
After applying fixes, check the CAS.log and DataTransferService.log again. Look for entries indicating successful content downloads or corrected hash mismatches. Additionally, verify that the BITS service is running properly withGet-Service BITS | Select Status, StartType. The client should now be able to install updates or applications without encountering 0x87D00607.
Prevention
To prevent recurrence of this issue, ensure regular maintenance and monitoring of distribution points. Implement a policy to automatically redistribute content when necessary usingHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\ClientSDK\BITSDownloadThrottle. Additionally, regularly review boundary group configurations to ensure clients are correctly assigned.
Use the OMA-URI
This guide provides a comprehensive approach to diagnosing and resolving issues related to error 0x87D00607, ensuring that your SCCM environment remains stable and efficient../Device/Vendor/MSFT/Policy/AssignedAccess/Application in Intune for configuring application restrictions.