Application Installation Error 0x87D00607

39001

Application Installation Error 0x87D00607 Application deployment in SCCM is interesting but you might encounter the errors if things are not configured properly in SCCM. If you have been working on SCCM application deployment then you might have come across the error The software change returned error code 0x87D00607 or Unable to download software 0x87D00607 error. Suppose that you have deployed an application to a device collection (A device, in Configuration Manager, is a collective term that includes any kind of computer such as a desktop, server, or a portable computer, and mobile device, such as a phone or tablet) and you see that when users try to install the application they see the error code 0x87D00607. Let’s see why this error comes up and how to troubleshoot this issue.

Application Installation Error 0x87D00607

Application Installation Error 0x87D00607

To start troubleshooting this issue you need to check the log files on the client computer. When you open the CITaskMgr.log file on the client computer you see the errors such as “CheckLocations Failed Error=0x87d00607” and “Unable to get locations, no need to continue with download”. Now you know that the application is with distribution point but the client computers are unable to find the distribution point.

Application Installation Error 0x87D00607

You might start checking this issue with boundary and boundary group configuration. In most cases the boundaries are configured correctly. You need to check if you have associated the distribution point with the boundary group. When you deploy a new DP for a site, you have the option to associate the DP during the DP installation or even later. If you don’t associate the DP with correct boundary group then you might face the deployment issues. So to fix this issue right click the boundary group and click on References tab. Under Site assignment the Use this boundary group for site assignment should be checked. Under the Site system servers click on Add and add the site server. Click on Apply and OK. Your application deployment should work fine now.

Application Installation Error 0x87D00607

7 COMMENTS

  1. Question! The softare catalog works great at my company however, people who are in a different subnet or different location cannot install software from the application catalog, it says something along the lines of ” Cannot install software ore request software”. And yes the url is added to the trusted zone sites. Any Suggestions??

      • I had Boundary group for my DP but somehow got deleted. I created a new boundary group today for the DP and then tried to push the app. Now it returned with a different error – The software change returned error code 0x87D01281 (-2016406911). As I researched about this error, I got to know that its with App-V sequencer version issue. I have App-V sequencer version 5.0.3361.0 through which I have created the application package.

  2. Hello.

    I had a similar problem where devices were unable to download the applications. The error was “Download failed for content Content under context System, error 0x80070005”.

    After I enabled the anonymous authentication on IIS -> Default Website -> SMS_DP_SMSPKG$ the problem was gone. My devices are domain joined and belong to the Boundary Group so why do we need to enable anonymous authentication?

    Thanks in advance for your help!

    Cheers,
    Pedro

    EDIT: I managed to find out why… It seems that windows 10 clients are getting tagged by SCCM as “Microsoft Windows NT Workstation 10.0 (TABLET EDITION), not sure why, which is probably making the windows 10 client falling in the “HTTP – Does not support mobile devices of mac computers” on the Distribution Point… After I enabled “Allow clients to connect anonymously” everything started working…

    Any downside for enabling this?

  3. Hi we having proper boundary group and all, Still we are facing same issue. Check Location Failed Error = 0x87d00607. No location available : CTaskConsumer(ScopeId_FFB1D20A-F8CC-4CAC-9D0C-5DE7A4B88918/DeploymentType_28aed865-a61d-4901-9b39-5a65f6054614.3.{B14E2F3C-DB8C-433F-8A38-110AEF47103D})

    Also since last 3 months all package from Primary to Secondary showing waiting for content ( in progress only) auto content replication not working from Primary to Secondary & DP which are belong to Secondary Site.

    Can you help me to short out this issue.

LEAVE A REPLY

Please enter your comment!
Please enter your name here