Solution 4: Unblock source files from execution Solution 3: Change Client connections to use HTTP Solution 2: Add SMS_DP Path in IIS ISAPI and CGI Restrictions Settings Solution 1: Change default web browser to Microsoft Edge or Internet Explorer The software change returned error code 0x87D00607 (-2016410105).įollow the below solution steps to resolve Software Center returned error code 0x87D00607 (-2016410105) issue. You can try starting the installation again, or if the problem continues, the information shown in the section below can assist your helpdesk in troubleshooting. There was a problem downloading the software. No more 0x87D00324(-2016410844) error.Problem Symptom: Software Center returned error code 0x87D00607 (-2016410105) when deploying a package or application through Microsoft System Center Configuration Manager (SCCM) but the content is not found. Now, Distribute Content > Deploy to selected collections. Modify the Detection Rule settings to match this config: To make the change, in the bottom panel, click the Deployment Types tab > right-click on the name and click Properties:Ĭlick the Detection Method tab > click the Edit Clause button: The solution to is to change the Detection Rule presence from Windows Installer, to File System. This happens due to the Detection Method of the application not working with the Windows Installer settings. However -when I did that with the Firefox MSI, specifically-I got an error in the Software Center Portal, error 0x87D00324:
The icon will change from the default, to your custom icon > click OK to save:Īt this point, you could just Distribute Content and Deploy the application to selected collections.
* Normally, I copy a 512×512 icon into the same folder as the MSI, and then navigate to that location under the Software Center tab. If you would like a customized app icon, select the properties of the application in the top panel > click the Software Center tab > click the Browse button > navigate to and select the custom icon: Update the application settings to reflect the following config: Right-click on Applications > click Create Application:īrowse to the UNC of the MSI > select the Firefox MSI: Now, in the Configuration Manager console, navigate to the Software Library node > Overview > Application Management > Applications In the example below, it is \\sccm\Mozilla\app\Firefox_72.0\ I ran into one snag, and I thought I’d detail the fix.įirst, before you begin in the Configuration Manager console, copy the Firefox MSI to your file repository.
Deploying the Firefox browser using SCCM is easy, but it isn’t without its caveats.
0 kommentar(er)
