SCCM Client Installation Failed With Error Code 0x87d00215

When SCCM client installation fails with error 0x87d00215 – “Failed to get DP locations as the expected version from MP”, it usually points to a boundary-related issue. In most cases, this error occurs due to missing or misconfigured SCCM site boundaries, preventing the client from locating a valid Distribution Point (DP) for content. Understanding how boundaries and boundary groups are configured is key to resolving this problem quickly and ensuring smooth client deployments.

Issue Details:

During SCCM client installation, the following error was recorded in the ccmsetup.log file

Failed to get DP locations as the expected version from MP 'http://server1.techuisitive.com'. Error 0x87d00215

The client was installed using the command line:

ccmsetup.exe /SMSSITECODE = P01

Cause:

The error indicates that the SCCM client required a new version of the installation source. However, the client was unable to locate a valid Distribution Point (DP) to download the updated source files. This typically occurs when site boundaries are missing or misconfigured, preventing the client from resolving DP locations through the Management Point (MP).

Step‑by‑Step Troubleshooting for Error 0x87d00215

1. Verify SCCM Boundary Configuration

• Open the SCCM Console → Administration → Hierarchy Configuration → Boundaries.
• Confirm that the client’s IP subnet or Active Directory (AD) site is listed as a boundary.
• If missing, create a new boundary:
  • Right‑click Boundaries → Create Boundary.
  • Select the appropriate type (IP Subnet, AD Site, IP Range).
  • Enter the client’s subnet or AD site details.
• Save and apply the configuration.

2. Check Boundary Group Association

• Navigate to Administration → Hierarchy Configuration → Boundary Groups.
• Ensure the boundary you verified/created in Step 1 is added to a boundary group.
• If not:
  • Edit the boundary group.
  • Click Add → select the boundary.
  • Save changes.
• This step ensures SCCM knows which group the client belongs to.

3. Validate Distribution Point (DP) Assignment

• Within the same boundary group, go to the References tab.
• Confirm that the boundary group is associated with at least one Distribution Point (DP).
• If missing:
  • Click Add → select the appropriate DP.
  • Save changes.
• Without a DP association, clients cannot download the installation source.

4. Trigger Client Installation Again

• On the client machine, rerun the installation command:
• Monitor C:\Windows\CCMSetup\Logs\ccmsetup.log for progress.
• If boundaries and DP associations are correct, the error should no longer appear.

5. Additional Verification (Optional)

• Use the LocationServices.log on the client to confirm DP discovery.
• Check if the client can resolve the Management Point (MP) and DP without errors.
• If issues persist, review recent Group Policy changes or network restrictions that may block communication.

Related Posts:

• SCCM Application Deployment Failed with Error 0x87d01106 | ConfigMgr
• SCCM Client Installation Failed With Error Code 0x87d00215
• PXE-E99: Unexpected network error – SCCM OSD
• Configuration Manager OSD task sequence fails with error code 0x80004005
• MECM OSD Task Sequence Failed with Error 0x80072EE7
• SCCM Client Push Installation Failed with Error 0x800706ba
• Failed to Add Update Source for WUAgent of type (2) and id ({ID). Error = 0x80004005
• SCCM OSD – Domain Join Failed with Error code 0x54b on HP Elitebook 840 G8
• ccmsetup failed with error code 0x87d00227
• Fix Application Deployment error 0x87d00213 in ConfigMgr
• CMG Connection Point Status Disconnected | SCCM | ConfigMgr
• CMG Setup – Subscription ID drop down not populating
• CMG Setup – Error when granting Contributor permission to the Azure AD app
• Failed to connect with DP – Error Code 0x8004100e | ConfigMgr | SCCM
• SCCM Client Installation Failed with error 0x87d0027e
• ConfigMgr OSD – PXE Troubleshooting
• SCCM WSUS sync error – Sync Failed – WSUS server not configured
• SCCM Software Distribution Troubleshooting