0x87D00325 SCCM Error

Question

_{Thursday, September 22, 2016 3:16 PM}

Hello,

I'm deploying an application to devices.  the deployment is correct exept for 10% of the devices which shows the following error: 0x87D00325

- I understand the meaning of the error: Application was still detected after uninstall completed.

- Looking to the Appenforce log shows the exitcode of 0  (success)

- trying to unistall/Reinstall  the application manually from the device,==> uninstall is greyed out ==> can not

- Googling for the answer shows that the process of unistalling was not done while the the process of installing the new version was done. that means I need to configure a delay time or sleep time.

But my problem is that the Unistall script is written on Powershell, so on the SCCM the unistall instruction looks like:

C:\C:\Program Files\...\...\script.ps1 -force

Is there a way adjust the unistall  instruction ?

Why its happing for a few devices and not all ?

Thank you all

All replies (3)

_{Sunday, September 25, 2016 6:44 PM ✅Answered | 1 vote}

Hi,

Thank you for the reply.

The error happen for few workstations. checking the these workstations they still have the old version of the application. the problem is a matter of time (delay), the process of the installation of the new version complete before the end of the Uninstall of the old version.

I fixed the error by adding a delay on the install script ( powershell command: start-sleep) and just change the uninstall script for the machine having problems.

It works like a sharm, I think Microsoft needs to add the delay feature for the uninstall on there GUI when creating the application.

Thank you anyway

_{Thursday, September 22, 2016 3:53 PM}

Just because the PoSH script ran and completed without an error doesn't mean it actual uninstalled anything or did what was expected per your defined detection criteria. You need to validate these things.

Jason | http://blog.configmgrftw.com | @jasonsandys

_{Sunday, September 25, 2016 9:18 PM}

It sounds like your uninstaller is spawning another process to perform the actual installation and thus there is no way for them to wait on a process that they don't know exists. Adding a delay addresses the symptom in simple cases for sure but doesn't really fix the problem which lies with the uninstaller. This is something that can cause issues with installers as well. You should file a UserVoice item to have a delay added.

Jason | http://blog.configmgrftw.com | @jasonsandys