How To Fix SCCM Deployment Error 0X87D00324

SCCM is without doubt one of the best instruments for deploying purposes and updates on a big scale. But nearly as good as it’s, often, you should still face deployment points such because the 0X87D00324 error.

This error code, particularly, signifies that the appliance was put in, but it surely couldn’t be detected by the configuration supervisor. As for why this occurs, generally, both the detection technique or the values in use are incorrect.

Validating these will resolve this error for many customers, however there are just a few different options you possibly can attempt as nicely. We’ve listed the steps to use all these within the information under.

What Causes Error 0X87D00324 During SCCM Deployment?

The 0X87D00324 error happens as a result of the usage of an incorrect detection technique throughout SCCM deployment. In uncommon circumstances, chances are you’ll encounter this error regardless of using the proper detection technique if there are different points regarding command synchronicity or network entry.

How to Fix Error 0X87D00324 During SCCM Deployment?

Since an incorrect detection technique causes this error generally, validating it and guaranteeing all of the values are right will resolve this error more often than not. You’ll discover all the required particulars relating to this within the sections under.

Validate the Detection Method

The Configuration Manager detects an software by verifying its GUID (Unique Application Identifier) from the registry. If the verification fails as a result of an incorrect path or unsuitable GUID, or every other motive, the detection fails, and error 0X87D00324 is returned. The steps to resolve these points are listed under:

1. In the ConfigMgr console, navigate to Software Library > Overview > Application Management > Applications.
2. Select an software and click on Deployment Types or Deployment Properties.
3. Right-click the appliance and choose Properties.
4. In the MSI file properties window, swap to the Detection Method tab.
   
5. Select the required detection technique and click on on Edit or Edit Clause.
6. In the Detection Rule window, choose Windows Installer because the setting sort.
   
7. Verify that the listed product code is right by checking the registry entry on the shopper machine. The registry path is:
   32 bit: HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftWindowsCurrentVersionUninstall 
   64 bit:
   HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionUninstall
8. The listing of keys in curly brackets {} are the product codes for varied packages. Select one in every of them and examine the Display Name. Repeat this till you discover this system you’re making an attempt to put in.
9. Once you discover that, confirm that the GUID matches with the product code used within the Detection Clause.
   

Even after the detection clause is corrected, you should still encounter this error. This is probably going as a result of ConfigMgr makes use of binary differential replication (BDR). Basically, it solely resends new or modified content material as a substitute of sending all of the supply recordsdata to attenuate network bandwidth utilization. You can simply repair this problem by refreshing the deployment with the next steps:

1. Open the Configuration Manager properties on the shopper laptop.
2. Run the Machine Policy Request and Evaluation Cycle within the Action tab.
3. Once the brand new policy is obtained, the deployment will work, and the appliance will set up with none errors.

Add Delay to Detection

Some installers can spawn a toddler course of to carry out the precise set up. If the preliminary course of exits however the set up isn’t full but, ConfigMgr will attempt to detect the product however inevitably fail.

In circumstances like this, including a easy script to add a timeout is sufficient to repair this problem. You may add a sleep interval after the set up course of by including Start-Sleep -seconds 60throughout the PSADT installer script after the msi set up instructions. A 60-second delay is mostly sufficient, however you possibly can modify it as you favor.

User Reported Fixes

Note: User-reported fixes typically solely apply to area of interest eventualities, however they’re price trying into nonetheless.

One consumer reported dealing with the 0X87D00324 error as a result of he solely copied the GUID (product code), and never the curly brackets, as he didn’t suppose they have been mandatory. We have a tendency to not discover small issues like this, so be sure to give the product code a double examine.

Another consumer reported that he wrote a script however couldn’t deploy it as an software. The motive why this occurred was that the script was working as an account that didn’t have network entry. Using a network entry account and guaranteeing it has entry to the appliance you’re making an attempt to deploy will resolve the difficulty in such eventualities.