This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(92.8, 20%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EQ5%3C/text%3E%3C/svg%3E)
I'm trying to deploy an application in SCCM, but in client it failed to download it, the error message in the software center is:
The software change returned error code 0x87D00607(-2016410105)
Any idea?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(252.8, 91%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETM%3C/text%3E%3C/svg%3E)
Hi @QdPooler-5995 ,
The error code 0x87d00607 means that the content is not found by SCCM/client and the reason for that can be numerous like improper configuration of boundaries or boundary groups, pre-staged content, blockage from the firewall, etc.
To narrow down the problem, we need:
1, Make sure boundary groups are enabled in the properties of the Distribution Point and check if the IPs (make sure no IP address is typed wrongly) of the client machine are included in the boundary group.
2, Check the required port to the firewall of your client machine.
3, Check appenforce.log in the client.
Here are reference links:
https://appuals.com/sccm-installation-error-code-0x87d00607/
--please don't forget to upvote and Accept as answer if the reply is helpful--
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(259.20000000000005, 6%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
So, that pesky error code 0x87d00607, right? In my opinion, it usually means that SCCM/client is having a hard time finding the content, and trust me, there could be a bunch of reasons for it. It's kind of like a puzzle with pieces scattered all over.
To tackle this puzzle, here's what I'd suggest, just based on my experience:
First things first, make sure those boundary groups are not only turned on but also set up right in the Distribution Point properties. Oh, and double-check those client machine IP addresses – typos happen to the best of us.
Let's talk about network security. Your client machine's firewall could be causing trouble. It's like a guard at the gate. Check if it's blocking any ports that SCCM needs to do its thing.
Now, this is where the real detective work happens. Look into that appenforce.log on the client. It's like the diary of what's going on with the content. You might find some valuable clues there.
From where I stand, maintaining top-notch quality assurance is not just about fixing the immediate issue – it's about ensuring that your SCCM deployment runs like a well-oiled machine in the long run. Oh, and if you find this info helpful, don't forget to give it a thumbs-up and accept it as an answer. Quality assurance is key to smooth sailing in IT!
I hope this helps
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(220.8, 18%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESR%3C/text%3E%3C/svg%3E)
Error code 0x87D00607(-2016410105) usually indicates that the application deployment failed because the user does not have the necessary permissions to install the application. You should check the permissions of the user that is trying to install the application, and ensure that they have the necessary permissions to install and run the application. If the permissions are correct, you should also check the SCCM log files to get more information about the root cause of the error.