Last week I stumbled upon error 0x87D00607 (-2016410105). When I googled for “The software change returned error code 0x87D00607 (-2016410105)”, I mainly got “check your boundaries” as a possible solution. However, there may be other causes for this error. With this blog post, I’m trying to sum up all causes and solutions for error 0x87D00607.
Table of Contents
Solution 1: Check your IP-Address / DHCP / DNS
Your client may have a different IP address from what your SCCM server has in mind.
On your Client, run ipconfig /all, and note the IP address.
Then on your SCCM-server, ping the client and verify the IP address is the same.
In my case, I noticed a difference and found out my DNS server wasn’t functioning correctly. To solve:
- I deleted the DNS-record of the client on my DNS server
- I ran ipconfig /flushdns on my SCCM server
- I ran ipconfig /registerdns on my client
Solution 2: Check whether your boundary covers your IP address
In SCCM, you may have configured your boundary (group) to host range 192.168.1.0/24. However, if your client has IP address 192.168.2.10, it will not be able to use the Distribution Point associated with your Boundary (group). To solve, you have multiple options:
- Change the clients’ IP address to an address within the boundary
- Extend the boundary, so that it covers the IP address of the client
- Create a new boundary and add it to the boundary group
Solution 3: Verify the distribution point is part of the boundary group
The distribution point needs to be a part of the boundary (group). If no site system is added as content location for a boundary group, no software will be deployed. To verify your DP in a boundary group, open the properties of the Boundary Group. Then go to References and note the content locations. If there’s no DP, add one.