The software change returned error code 0x87d00607 2016410105

Hi,

I’m trying to deploy some applications through SCCM’s software catalog but I stumble upon the error «The software change returned error code 0x87D00607(-2016410105).»

Checking some logs, I found these:

CAS.log

The number of discovered DPs(including Branch DP and Multicast) is 0    ContentAccess    11/23/2016 8:02:13 PM    10072 (0x2758)
Requesting locations synchronously for content Content_ba085e91-bf14-4845-9fb1-3b99281efde1.1 with priority Foreground    ContentAccess    11/24/2016 7:55:04 AM    4856 (0x12F8)
sRelatedContentIDs is <RelatedContentIDs><RelatedContentID ID=»Content_f43014ea-0cbf-4408-99c2-0bb104be61ce.1″/></RelatedContentIDs>. Length = 110.    ContentAccess    11/24/2016 7:55:05 AM  
 4856 (0x12F8)
The number of discovered DPs(including Branch DP and Multicast) is 0    ContentAccess    11/24/2016 7:55:05 AM    4856 (0x12F8)
Requesting locations synchronously for content Content_ba085e91-bf14-4845-9fb1-3b99281efde1.1 with priority Foreground    ContentAccess    11/24/2016 7:55:05 AM    4856 (0x12F8)
sRelatedContentIDs is <RelatedContentIDs><RelatedContentID ID=»Content_f43014ea-0cbf-4408-99c2-0bb104be61ce.1″/></RelatedContentIDs>. Length = 110.    ContentAccess    11/24/2016 7:55:05 AM  
 4856 (0x12F8)
The number of discovered DPs(including Branch DP and Multicast) is 0    ContentAccess    11/24/2016 7:55:05 AM    4856 (0x12F8)
Location update from CTM for content CM10003D.1 and request {BB7A500D-595C-4BA8-993D-E58C280536DD}    ContentAccess    11/24/2016 7:56:43 AM    740 (0x02E4)
   Download request only, ignoring location update    ContentAccess    11/24/2016 7:56:43 AM    740 (0x02E4)
Location update from CTM for content CM10003D.1 and request {BB7A500D-595C-4BA8-993D-E58C280536DD}    ContentAccess    11/24/2016 7:58:16 AM    740 (0x02E4)
   Download request only, ignoring location update    ContentAccess    11/24/2016 7:58:16 AM    740 (0x02E4)

LocationServices.log

Current AD site of machine is SMHO    LocationServices    11/24/2016 7:55:04 AM    4856 (0x12F8)
Current AD site of machine is SMHO    LocationServices    11/24/2016 7:55:05 AM    4856 (0x12F8)
Current AD site of machine is SMHO    LocationServices    11/24/2016 7:55:05 AM    4856 (0x12F8)
Current AD site of machine is SMHO    LocationServices    11/24/2016 7:55:05 AM    4856 (0x12F8)
Current AD site of machine is SMHO    LocationServices    11/24/2016 7:56:42 AM    8868 (0x22A4)
Attempting to retrieve lookup MP(s) from AD    LocationServices    11/24/2016 7:56:42 AM    8868 (0x22A4)
The MP name retrieved is ‘SMPHHOSCCM01.smprime.sm.ph’ with version ‘8239’ and capabilities ‘<Capabilities SchemaVersion=»1.0″><Property Name=»SSLState» Value=»0″/></Capabilities>’    LocationServices  
 11/24/2016 7:56:42 AM    8868 (0x22A4)
MP ‘SMPHHOSCCM01.smprime.sm.ph’ is compatible    LocationServices    11/24/2016 7:56:42 AM    8868 (0x22A4)
Lookup Management Points from AD:    LocationServices    11/24/2016 7:56:42 AM    8868 (0x22A4)
Name: ‘SMPHHOSCCM01.smprime.sm.ph’ HTTPS: ‘N’ ForestTrust: ‘N’    LocationServices    11/24/2016 7:56:42 AM    8868 (0x22A4)
Retrieved lookup MP(s) from AD    LocationServices    11/24/2016 7:56:42 AM    8868 (0x22A4)
Default Management Points from AD:    LocationServices    11/24/2016 7:56:42 AM    8868 (0x22A4)
Name: ‘SMPHHOSCCM01.smprime.sm.ph’ HTTPS: ‘N’ ForestTrust: ‘N’    LocationServices    11/24/2016 7:56:42 AM    8868 (0x22A4)
Persisting the default management points in WMI    LocationServices    11/24/2016 7:56:42 AM    8868 (0x22A4)
Current AD site of machine is SMHO    LocationServices    11/24/2016 7:56:42 AM    8868 (0x22A4)
LSUpdateInternetManagementPoints    LocationServices    11/24/2016 7:56:42 AM    8868 (0x22A4)
Current AD site of machine is SMHO    LocationServices    11/24/2016 7:56:42 AM    8868 (0x22A4)
LSUpdateInternetManagementPoints: No internet MPs were retrieved from MP SMPHHOSCCM01.smprime.sm.ph, clearing previous list.    LocationServices    11/24/2016 7:56:42 AM    8868 (0x22A4)
Default Management Points from MP:    LocationServices    11/24/2016 7:56:42 AM    8868 (0x22A4)
Name: ‘SMPHHOSCCM01.smprime.sm.ph’ HTTPS: ‘N’ ForestTrust: ‘N’    LocationServices    11/24/2016 7:56:42 AM    8868 (0x22A4)
Persisted Default Management Point Locations locally    LocationServices    11/24/2016 7:56:42 AM    8868 (0x22A4)
Current AD site of machine is SMHO    LocationServices    11/24/2016 7:56:42 AM    8868 (0x22A4)
Attempting to retrieve local MPs from the assigned MP    LocationServices    11/24/2016 7:56:42 AM    8868 (0x22A4)
Current AD site of machine is SMHO    LocationServices    11/24/2016 7:56:42 AM    8868 (0x22A4)
Current AD site of machine is SMHO    LocationServices    11/24/2016 7:56:42 AM    8868 (0x22A4)
Current AD site of machine is SMHO    LocationServices    11/24/2016 7:56:42 AM    8868 (0x22A4)
Current AD site of machine is SMHO    LocationServices    11/24/2016 7:56:42 AM    8868 (0x22A4)
Retrieved management point encryption info from AD.    LocationServices    11/24/2016 7:56:42 AM    9800 (0x2648)
Raising event:
instance of CCM_CcmHttp_Status
{
    ClientID = «GUID:B2F9D111-B2A3-4773-8D95-298F7CE2589B»;
    DateTime = «20161123235643.107000+000»;
    HostName = «SMPHHOSCCM01.smprime.sm.ph»;
    HRESULT = «0x00000000»;
    ProcessID = 9188;
    StatusCode = 0;
    ThreadID = 9800;
};
    LocationServices    11/24/2016 7:56:43 AM    9800 (0x2648)
Updating portal information.    LocationServices    11/24/2016 7:56:43 AM    8540 (0x215C)
Current AD site of machine is SMHO    LocationServices    11/24/2016 7:56:43 AM    7964 (0x1F1C)
Received reply of type PortalCertificateReply    LocationServices    11/24/2016 7:56:43 AM    740 (0x02E4)
The reply from location manager contains 1 certificates    LocationServices    11/24/2016 7:56:43 AM    740 (0x02E4)
Updating portal certificates    LocationServices    11/24/2016 7:56:43 AM    740 (0x02E4)
Successfully created context from the raw certificate.    LocationServices    11/24/2016 7:56:43 AM    740 (0x02E4)
Calling back with empty distribution points list    LocationServices    11/24/2016 7:56:43 AM    7964 (0x1F1C)
Executing Task LSRefreshLocationsTask    LocationServices    11/24/2016 7:58:16 AM    8868 (0x22A4)
Current AD site of machine is SMHO    LocationServices    11/24/2016 7:58:16 AM    8868 (0x22A4)
Current AD site of machine is SMHO    LocationServices    11/24/2016 7:58:16 AM    8868 (0x22A4)
Calling back with empty distribution points list    LocationServices    11/24/2016 7:58:16 AM    8868 (0x22A4)
Current AD site of machine is SMHO    LocationServices    11/24/2016 8:01:42 AM    7768 (0x1E58)

It seems that client can’t see any DP for them to download the application. Searching the internet, I found similar issues that are all pointing to boundaries. I have checked my boundaries and they all seems ok and configured properly. Actually, I was to
able deploy software updates a few days ago and there was no recent change done on the sccm server especially with the boundaries.

What else can be done for this?

Thanks!

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.

The issue arises when a user tries to deploy a package or application through SCCM but encounters the following message:

The software change returned error code 0x87D00607(-2016410105)

You can fix the error code 0x87d00607 by trying the solutions below but before diving into more technical solutions, check if rebooting your primary SCCM server sorts out the issue. Moreover, make sure the date and time are correct on the server and client machines. Furthermore, make sure all updates or hotfixes for SCCM are applied to your machine. Additionally, check if all the affected users are present in the SourceContentLib directory. If not, add the users to the mentioned library and check if the issue is resolved.

If the package or application, you are trying to install (or uninstall), has an official installer/uninstaller (like Adobe CC Uninstaller), check if using that official installer/uninstaller solves the problem. Also, do not forget to check if the package or application has any dependencies, if so, then make sure those dependencies are included in the source files of the package or application. If you are trying to install an updated version of an application (e.g., MS Office) that is already installed on the client machine, then check if uninstalling the older version of the application lets you install the newer version without any issue.

1. Change the Default Browser of the Client Machine

The application or package might show the error code 0x87d00607 if the default browser of your client machine is not set to Edge or Internet Explorer (due to different OS dependencies in a corporate networking environment). In this case, setting the default browser of the client machine (or machines) to Internet Explorer or Edge may solve the problem. Before proceeding, check if you are using a metered connection (e.g., a notebook with a SIM card), then allowing the same in the Default Client Settings of SCCM may solve the problem.

1. Click Windows, type: Default Apps, and then open Default Apps.
2. Now click the option under Web Browser (e.g., Google Chrome) and choose Internet Explorer.
3. Then reboot your client machine and upon reboot, check if it is clear of the error code 0x87d00607.

If at step 2, the default browser is already set to Internet Explorer, set it as Microsoft Edge and reboot your machine to check if the error 0x87d00607 is cleared out.

2. Add the SMS_DP Path in the IIS Settings

SMS_DP hosts the log files of DP, files to validate content, pre-stage content (if enabled), and is the temporary storage hub of the package/application before its inclusion in the Content Library. You may encounter the error 0x87d00607 if the SMP_DP path is not properly configured in the IIS Settings of DP. In this scenario, adding the path to SMS_DP in the IIS Settings may solve the problem. But before proceeding, make sure to remove NAP (Network Access Protection), as it has been deprecated by Microsoft in Windows Server 2012 R2, and if you are still using it, then uninstalling it may solve the problem.

1. Log on to the DP server and navigate to its IIS settings.
2. Now select the server and open ISAPI and CGI Restrictions.
3. Then check if an entry for SMS_DP is present there. If not, then add a new entry with the following path:

   C:Windowssystem32inetsrvsmsfileisapi.dll

4. Now apply your changes and check if the error 0x87d00607 is cleared.

3. Use HTTP to the Client Connections

The error code can be caused by the improper configuration of the client connections protocol; the clients are required to connect to the server by using HTTPS protocol. In this scenario, setting the client connections to use HTTP protocol may solve the problem.

1. Open the SCCM and in the left pane, expand Site Configuration.
2. Now select Servers and Site System Rules and in the right pane, open Management Point (in the Site System Roles section).
3. Then select HTTP and apply your changes.
4. Wait for at least 5 minutes and check if the error 0x87d00607 is resolved.

If that did not do the trick, check if the DNS server of your organization is functioning properly.

4. Unblock the Source Files of the Package/Application

You may encounter the error code 0X87d00607 2016410105 if the OS of your device does not trust some of the source files and blocks their execution. In this context, unblocking the source files might solve the problem.

1. Navigate to the directory of the source files of your package/application, right-click on any of the files, and select Properties.
2. Then check if an unblock option is available (either checkbox or button), if so, then click on it to Unblock the file.
3. Now repeat the same to unblock all the source files and check if the system is clear of the error code 0X87d00607 2016410105.

This method might work for some files, but for a large number of files, you may use the SysInternels Streams to unblock all files. If that did not work, then check if removing the package/application from the SCCM server, creating a new directory on the SCCM server, and copying the package/application source files to that directory solves the issue.

5. Change the Deployment Options of the Package/Application

You may encounter the error code 0x87d00607 if the Deployment Options of the package/application are not configured to run locally. In this case, setting the Deployment Options to download content and run locally may solve the problem.

1. Open the Properties of your package/application in SCCM and head to the Content tab.
2. Now expand the dropdown of the Deployment Options and select Download Content from Distribution Point and Run Locally.
3. Then apply your changes and check (at least after 5 minutes) that the software change returned error is cleared.

6. Disable the Pre-staged Content of the Distribution Point

You may encounter the error code 0X87d00607 in SCCM if you have configured the distribution point to only use the pre-staged content (which will only accept content manually copied to it). In this scenario, disabling the pre-staged content for the distribution point may solve the problem.

1. Open SCCM and open the Properties of the Distribution Point.
2. Now remove the checkmark of Enable This Distribution Point for Prestaged Content and apply your changes.
3. Then wait for 5 minutes and check if the error code 0x87d00607 is cleared.

7. Enable Fallback Location for Content

If the client machine cannot access a preferred distribution point, then enabling the fallback location for the content may enable the machine to fetch the same from another source and thus solve the error at hand.

1. Open the Properties of your package/application and head to its Content tab.
2. Now, checkmark the option of Allow Clients to Use a Fallback Source Location for Content and make sure the Deployment Options dropdown is set to Download Content from the Distribution Point and Run Locally.
3. Then apply your changes and check (at least after 5 minutes) if the error code 0X87d00607 2016410105 is cleared.

8. Allow the Users’ Machines to Use Distribution Points

If your organization is using SCCM’s Distribution Points to distribute the packages/applications, then allowing the clients’ machines to use the distribution points from the default site boundary group may clear the 0x87d00607 error. But before proceeding, check if setting the maintenance window of the deployed software to collection solves the issue.

1. Steer to your package/application in the SCCM and open package/application’s Properties.
2. Now head to the Content tab and checkmark the option of Allow Clients to Use Distribution Points from the Default Site Boundary Group.
3. Then apply your changes and check if SCCM’s error 0X87d00607 is cleared.

If that did not do the trick, check if allowing the client machines to download from a cloud source/distribution point solves the problem. If that did not work, you may check if the DP server is not corrupt or is missing from the group of DP servers.

9. Edit Boundaries and Boundary Group in SCCM

The error code 0x87d00607 in SCCM may emerge if the boundaries and boundary group are not properly configured or the IP of the client’s machine is not added to them. In this context, editing the boundaries and boundary groups may solve the problem.

1. Launch the SCCM and navigate to the following path:

   Administration>>Overview>>Hierarchy Configuration>>Boundary Groups

2. Now head to the Reference tab of the Boundary Group and checkmark Use This Boundary Group for Site Assignment (under Site Assignment).
3. Then add the server to the boundary group and apply your changes to check if the SCCM issue is resolved.
4. If not, 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.
5. Keep in mind that adding IPs like 10.22.8.0 to 10.22.9.10 will not add 10.22.9.0 in the boundary group (although, it works in the networking world), so, add the IPs accordingly.
6. Also, check if using the IPv6 IP range of the client machines in the boundary groups sorts the issue.

10. Allow the SCCM Required Ports in the Firewall of the Client Machine

The SCCM might show the error code 0x87d00607 if the SCCM’s required ports are blocked by the firewall on the client machine. In this case, allowing the SCCM’s required ports on the client machine may solve the problem. You may check the SCCM’s required ports as per the protocol from the official Microsoft source and add the required port to the firewall of your client machine. For illustration, we will discuss the process for opening the port of Global catalog LDAP to the Windows Defender Firewall. But before proceeding, check if the ports of the webserver of SCCM are not in conflict with another service (especially, port 80).

Warning: Advance with utmost care and at your own risk as editing the firewall settings is a skillful task and if not done properly, you may cause unintended and everlasting damage to your data/system.

1. Click Windows, type: Windows Defender Firewall, and open it.
2. Now, in the left pane, select Outbound Rules, and in the Action pane, click on New Rule.
3. Then select Port as the Rule Type and select the radio button of TCP.
4. Now enter 3268 in the Specific Remote Ports box.
5. Then click on Next and select the radio button of Allow the Connection.
6. Now select all the three types of networks (i.e., Domain, Private, and Public) and click on Next.
7. Then name the rule as per your requirement and click Finish.
8. Now try again to check if SCCM is clear of the error 0x87d00607.

If that issue persists, check if the firewall of your VPN or router is not causing the issue. If the issue is still there, check if re-adding the client machine to the domain solves the problem. If that did not do the trick, then you may use ContentLibraryCleanup.exe in the delete mode against your SCCM server and check if that solves the issue at hand. If the issue persists, then you may reinstall IIS (with BITS and ASP.Net) or SCCM (with IIS). If none of the solutions did the trick for you, then you may share the package/application with users (till the problem is reported to be solved).

All solutions to error 0x87D00607: The software change returned error code 0x87D00607 (-2016410105)

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.

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:

1. I deleted the DNS-record of the client on my DNS server
2. I ran ipconfig /flushdns on my SCCM server
3. 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.

Источник

The software change returned error code 0x87d00607 2016410105

I’m trying to deploy some applications through SCCM’s software catalog but I stumble upon the error «The software change returned error code 0x87D00607(-2016410105).»

Checking some logs, I found these:

The number of discovered DPs(including Branch DP and Multicast) is 0 ContentAccess 11/23/2016 8:02:13 PM 10072 (0x2758)
Requesting locations synchronously for content Content_ba085e91-bf14-4845-9fb1-3b99281efde1.1 with priority Foreground ContentAccess 11/24/2016 7:55:04 AM 4856 (0x12F8)
sRelatedContentIDs is . Length = 110. ContentAccess 11/24/2016 7:55:05 AM 4856 (0x12F8)
The number of discovered DPs(including Branch DP and Multicast) is 0 ContentAccess 11/24/2016 7:55:05 AM 4856 (0x12F8)
Requesting locations synchronously for content Content_ba085e91-bf14-4845-9fb1-3b99281efde1.1 with priority Foreground ContentAccess 11/24/2016 7:55:05 AM 4856 (0x12F8)
sRelatedContentIDs is . Length = 110. ContentAccess 11/24/2016 7:55:05 AM 4856 (0x12F8)
The number of discovered DPs(including Branch DP and Multicast) is 0 ContentAccess 11/24/2016 7:55:05 AM 4856 (0x12F8)
Location update from CTM for content CM10003D.1 and request ContentAccess 11/24/2016 7:56:43 AM 740 (0x02E4)
Download request only, ignoring location update ContentAccess 11/24/2016 7:56:43 AM 740 (0x02E4)
Location update from CTM for content CM10003D.1 and request ContentAccess 11/24/2016 7:58:16 AM 740 (0x02E4)
Download request only, ignoring location update ContentAccess 11/24/2016 7:58:16 AM 740 (0x02E4)

Current AD site of machine is SMHO LocationServices 11/24/2016 7:55:04 AM 4856 (0x12F8)
Current AD site of machine is SMHO LocationServices 11/24/2016 7:55:05 AM 4856 (0x12F8)
Current AD site of machine is SMHO LocationServices 11/24/2016 7:55:05 AM 4856 (0x12F8)
Current AD site of machine is SMHO LocationServices 11/24/2016 7:55:05 AM 4856 (0x12F8)
Current AD site of machine is SMHO LocationServices 11/24/2016 7:56:42 AM 8868 (0x22A4)
Attempting to retrieve lookup MP(s) from AD LocationServices 11/24/2016 7:56:42 AM 8868 (0x22A4)
The MP name retrieved is ‘SMPHHOSCCM01.smprime.sm.ph’ with version ‘8239’ and capabilities ‘

‘ LocationServices 11/24/2016 7:56:42 AM 8868 (0x22A4)
MP ‘SMPHHOSCCM01.smprime.sm.ph’ is compatible LocationServices 11/24/2016 7:56:42 AM 8868 (0x22A4)
Lookup Management Points from AD: LocationServices 11/24/2016 7:56:42 AM 8868 (0x22A4)
Name: ‘SMPHHOSCCM01.smprime.sm.ph’ HTTPS: ‘N’ ForestTrust: ‘N’ LocationServices 11/24/2016 7:56:42 AM 8868 (0x22A4)
Retrieved lookup MP(s) from AD LocationServices 11/24/2016 7:56:42 AM 8868 (0x22A4)
Default Management Points from AD: LocationServices 11/24/2016 7:56:42 AM 8868 (0x22A4)
Name: ‘SMPHHOSCCM01.smprime.sm.ph’ HTTPS: ‘N’ ForestTrust: ‘N’ LocationServices 11/24/2016 7:56:42 AM 8868 (0x22A4)
Persisting the default management points in WMI LocationServices 11/24/2016 7:56:42 AM 8868 (0x22A4)
Current AD site of machine is SMHO LocationServices 11/24/2016 7:56:42 AM 8868 (0x22A4)
LSUpdateInternetManagementPoints LocationServices 11/24/2016 7:56:42 AM 8868 (0x22A4)
Current AD site of machine is SMHO LocationServices 11/24/2016 7:56:42 AM 8868 (0x22A4)
LSUpdateInternetManagementPoints: No internet MPs were retrieved from MP SMPHHOSCCM01.smprime.sm.ph, clearing previous list. LocationServices 11/24/2016 7:56:42 AM 8868 (0x22A4)
Default Management Points from MP: LocationServices 11/24/2016 7:56:42 AM 8868 (0x22A4)
Name: ‘SMPHHOSCCM01.smprime.sm.ph’ HTTPS: ‘N’ ForestTrust: ‘N’ LocationServices 11/24/2016 7:56:42 AM 8868 (0x22A4)
Persisted Default Management Point Locations locally LocationServices 11/24/2016 7:56:42 AM 8868 (0x22A4)
Current AD site of machine is SMHO LocationServices 11/24/2016 7:56:42 AM 8868 (0x22A4)
Attempting to retrieve local MPs from the assigned MP LocationServices 11/24/2016 7:56:42 AM 8868 (0x22A4)
Current AD site of machine is SMHO LocationServices 11/24/2016 7:56:42 AM 8868 (0x22A4)
Current AD site of machine is SMHO LocationServices 11/24/2016 7:56:42 AM 8868 (0x22A4)
Current AD site of machine is SMHO LocationServices 11/24/2016 7:56:42 AM 8868 (0x22A4)
Current AD site of machine is SMHO LocationServices 11/24/2016 7:56:42 AM 8868 (0x22A4)
Retrieved management point encryption info from AD. LocationServices 11/24/2016 7:56:42 AM 9800 (0x2648)
Raising event:
instance of CCM_CcmHttp_Status
<
ClientID = «GUID:B2F9D111-B2A3-4773-8D95-298F7CE2589B»;
DateTime = «20161123235643.107000+000»;
HostName = «SMPHHOSCCM01.smprime.sm.ph»;
HRESULT = «0x00000000»;
ProcessID = 9188;
StatusCode = 0;
ThreadID = 9800;
>;
LocationServices 11/24/2016 7:56:43 AM 9800 (0x2648)
Updating portal information. LocationServices 11/24/2016 7:56:43 AM 8540 (0x215C)
Current AD site of machine is SMHO LocationServices 11/24/2016 7:56:43 AM 7964 (0x1F1C)
Received reply of type PortalCertificateReply LocationServices 11/24/2016 7:56:43 AM 740 (0x02E4)
The reply from location manager contains 1 certificates LocationServices 11/24/2016 7:56:43 AM 740 (0x02E4)
Updating portal certificates LocationServices 11/24/2016 7:56:43 AM 740 (0x02E4)
Successfully created context from the raw certificate. LocationServices 11/24/2016 7:56:43 AM 740 (0x02E4)
Calling back with empty distribution points list LocationServices 11/24/2016 7:56:43 AM 7964 (0x1F1C)
Executing Task LSRefreshLocationsTask LocationServices 11/24/2016 7:58:16 AM 8868 (0x22A4)
Current AD site of machine is SMHO LocationServices 11/24/2016 7:58:16 AM 8868 (0x22A4)
Current AD site of machine is SMHO LocationServices 11/24/2016 7:58:16 AM 8868 (0x22A4)
Calling back with empty distribution points list LocationServices 11/24/2016 7:58:16 AM 8868 (0x22A4)
Current AD site of machine is SMHO LocationServices 11/24/2016 8:01:42 AM 7768 (0x1E58)

It seems that client can’t see any DP for them to download the application. Searching the internet, I found similar issues that are all pointing to boundaries. I have checked my boundaries and they all seems ok and configured properly. Actually, I was to able deploy software updates a few days ago and there was no recent change done on the sccm server especially with the boundaries.

Источник

The software change returned error code 0x87d00607 2016410105

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

Question

Hi to everyone. I am learning SCCM 2012 R2 using book Mastering SCCM 2012 R2 in addition to various video trainings and online resources. Currently I am focused on application deployment. I created Foxit Reader application — msi deployment type, distributed it to DP and deployed it to device collection containing only one test computer (Win 7 Pro SP1 x64). Having done all these steps I went to client’s Software Center and Application Catalog. Foxit Reader app is visible but as soon as I click on Install button I receive an error:

The software change returned error code 0x87D00607(-2016410105).

I deployed Office 2013 a few days ago (although I am struggling to uninstall it silently) without problems. Meanwhile I did not change anything related to boundaries, boundary groups and DPs. I have only one SCCM 2012 R2 server (Primary stand-alone site). I hate these situations when I follow along some official learning material such as this book, doing everything the same as it is done there and it does not work at all.

Unfortunately I can not afford official MS training, my company does not invest in their system engineers so we are on our own. It is nice to learn something by yourself but situations like this take too much time — probably on official training it would be solved immediately.

Источник

Fix: SCCM Installation Error Code 0X87D00607 (-2016410105)

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.

The issue arises when a user tries to deploy a package or application through SCCM but encounters the following message:

The software change returned error code 0x87D00607(-2016410105)

The Software Change Returned Error Code 0X87d00607 2016410105

You can fix the error code 0x87d00607 by trying the solutions below but before diving into more technical solutions, check if rebooting your primary SCCM server sorts out the issue. Moreover, make sure the date and time are correct on the server and client machines. Furthermore, make sure all updates or hotfixes for SCCM are applied to your machine. Additionally, check if all the affected users are present in the SourceContentLib directory. If not, add the users to the mentioned library and check if the issue is resolved.

If the package or application, you are trying to install (or uninstall), has an official installer/uninstaller (like Adobe CC Uninstaller), check if using that official installer/uninstaller solves the problem. Also, do not forget to check if the package or application has any dependencies, if so, then make sure those dependencies are included in the source files of the package or application. If you are trying to install an updated version of an application (e.g., MS Office) that is already installed on the client machine, then check if uninstalling the older version of the application lets you install the newer version without any issue.

1. Change the Default Browser of the Client Machine

The application or package might show the error code 0x87d00607 if the default browser of your client machine is not set to Edge or Internet Explorer (due to different OS dependencies in a corporate networking environment). In this case, setting the default browser of the client machine (or machines) to Internet Explorer or Edge may solve the problem. Before proceeding, check if you are using a metered connection (e.g., a notebook with a SIM card), then allowing the same in the Default Client Settings of SCCM may solve the problem.

1. Click Windows, type: Default Apps, and then open Default Apps. Open Default Apps
2. Now click the option under Web Browser (e.g., Google Chrome) and choose Internet Explorer. Set Default Web Browser to Internet Explorer
3. Then reboot your client machine and upon reboot, check if it is clear of the error code 0x87d00607.

If at step 2, the default browser is already set to Internet Explorer, set it as Microsoft Edge and reboot your machine to check if the error 0x87d00607 is cleared out.

2. Add the SMS_DP Path in the IIS Settings

SMS_DP hosts the log files of DP, files to validate content, pre-stage content (if enabled), and is the temporary storage hub of the package/application before its inclusion in the Content Library. You may encounter the error 0x87d00607 if the SMP_DP path is not properly configured in the IIS Settings of DP. In this scenario, adding the path to SMS_DP in the IIS Settings may solve the problem. But before proceeding, make sure to remove NAP (Network Access Protection), as it has been deprecated by Microsoft in Windows Server 2012 R2, and if you are still using it, then uninstalling it may solve the problem.

1. Log on to the DP server and navigate to its IIS settings.
2. Now select the server and open ISAPI and CGI Restrictions. Open ISAPI and CGI Restrictions in the IIS Settings
3. Then check if an entry for SMS_DP is present there. If not, then add a new entry with the following path:
4. Now apply your changes and check if the error 0x87d00607 is cleared.

3. Use HTTP to the Client Connections

The error code can be caused by the improper configuration of the client connections protocol; the clients are required to connect to the server by using HTTPS protocol. In this scenario, setting the client connections to use HTTP protocol may solve the problem.

1. Open the SCCM and in the left pane, expand Site Configuration.
2. Now select Servers and Site System Rules and in the right pane, open Management Point (in the Site System Roles section).
3. Then select HTTP and apply your changes. Set Client Connections to HTTP in SCCM
4. Wait for at least 5 minutes and check if the error 0x87d00607 is resolved.

If that did not do the trick, check if the DNS server of your organization is functioning properly.

4. Unblock the Source Files of the Package/Application

You may encounter the error code 0X87d00607 2016410105 if the OS of your device does not trust some of the source files and blocks their execution. In this context, unblocking the source files might solve the problem.

1. Navigate to the directory of the source files of your package/application, right-click on any of the files, and select Properties.
2. Then check if an unblock option is available (either checkbox or button), if so, then click on it to Unblock the file. Unblock Security of the File
3. Now repeat the same to unblock all the source files and check if the system is clear of the error code 0X87d00607 2016410105.

This method might work for some files, but for a large number of files, you may use the SysInternels Streams to unblock all files. If that did not work, then check if removing the package/application from the SCCM server, creating a new directory on the SCCM server, and copying the package/application source files to that directory solves the issue.

5. Change the Deployment Options of the Package/Application

You may encounter the error code 0x87d00607 if the Deployment Options of the package/application are not configured to run locally. In this case, setting the Deployment Options to download content and run locally may solve the problem.

1. Open the Properties of your package/application in SCCM and head to the Content tab.
2. Now expand the dropdown of the Deployment Options and select Download Content from Distribution Point and Run Locally. Set Deployment Options to Download Content from Distribution Point and Run Locally
3. Then apply your changes and check (at least after 5 minutes) that the software change returned error is cleared.

6. Disable the Pre-staged Content of the Distribution Point

You may encounter the error code 0X87d00607 in SCCM if you have configured the distribution point to only use the pre-staged content (which will only accept content manually copied to it). In this scenario, disabling the pre-staged content for the distribution point may solve the problem.

1. Open SCCM and open the Properties of the Distribution Point.
2. Now remove the checkmark of Enable This Distribution Point for Prestaged Content and apply your changes. Disable Pre-Staged Content in SCCM
3. Then wait for 5 minutes and check if the error code 0x87d00607 is cleared.

7. Enable Fallback Location for Content

If the client machine cannot access a preferred distribution point, then enabling the fallback location for the content may enable the machine to fetch the same from another source and thus solve the error at hand.

1. Open the Properties of your package/application and head to its Content tab.
2. Now, checkmark the option of Allow Clients to Use a Fallback Source Location for Content and make sure the Deployment Options dropdown is set to Download Content from the Distribution Point and Run Locally. Allow Clients to Use a Fallback Source Location for Content
3. Then apply your changes and check (at least after 5 minutes) if the error code 0X87d00607 2016410105 is cleared.

8. Allow the Users’ Machines to Use Distribution Points

If your organization is using SCCM’s Distribution Points to distribute the packages/applications, then allowing the clients’ machines to use the distribution points from the default site boundary group may clear the 0x87d00607 error. But before proceeding, check if setting the maintenance window of the deployed software to collection solves the issue.

1. Steer to your package/application in the SCCM and open package/application’s Properties.
2. Now head to the Content tab and checkmark the option of Allow Clients to Use Distribution Points from the Default Site Boundary Group. Allow Clients to Use Distribution Points from the Default Site Boundary Group
3. Then apply your changes and check if SCCM’s error 0X87d00607 is cleared.

If that did not do the trick, check if allowing the client machines to download from a cloud source/distribution point solves the problem. If that did not work, you may check if the DP server is not corrupt or is missing from the group of DP servers.

9. Edit Boundaries and Boundary Group in SCCM

The error code 0x87d00607 in SCCM may emerge if the boundaries and boundary group are not properly configured or the IP of the client’s machine is not added to them. In this context, editing the boundaries and boundary groups may solve the problem.

1. Launch the SCCM and navigate to the following path:
2. Now head to the Reference tab of the Boundary Group and checkmark Use This Boundary Group for Site Assignment (under Site Assignment).
3. Then add the server to the boundary group and apply your changes to check if the SCCM issue is resolved. Enable Boundary Group for Site Assignment
4. If not, 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.
5. Keep in mind that adding IPs like 10.22.8.0 to 10.22.9.10 will not add 10.22.9.0 in the boundary group (although, it works in the networking world), so, add the IPs accordingly.
6. Also, check if using the IPv6 IP range of the client machines in the boundary groups sorts the issue.

10. Allow the SCCM Required Ports in the Firewall of the Client Machine

The SCCM might show the error code 0x87d00607 if the SCCM’s required ports are blocked by the firewall on the client machine. In this case, allowing the SCCM’s required ports on the client machine may solve the problem. You may check the SCCM’s required ports as per the protocol from the official Microsoft source and add the required port to the firewall of your client machine. For illustration, we will discuss the process for opening the port of Global catalog LDAP to the Windows Defender Firewall. But before proceeding, check if the ports of the webserver of SCCM are not in conflict with another service (especially, port 80).

Warning: Advance with utmost care and at your own risk as editing the firewall settings is a skillful task and if not done properly, you may cause unintended and everlasting damage to your data/system.

1. Click Windows, type: Windows Defender Firewall, and open it. Open Windows Defender Firewall
2. Now, in the left pane, select Outbound Rules, and in the Action pane, click on New Rule. Create a New Outbound Rule in the Firewall
3. Then select Port as the Rule Type and select the radio button of TCP. Select Port in the New Rule Window
4. Now enter 3268 in the Specific Remote Ports box. Select TCP and Enter 3268 in Specific Remote Ports
5. Then click on Next and select the radio button of Allow the Connection. Select Allow the Connection in the New Outbound Rule
6. Now select all the three types of networks (i.e., Domain, Private, and Public) and click on Next.
7. Then name the rule as per your requirement and click Finish.
8. Now try again to check if SCCM is clear of the error 0x87d00607.

Источник