PENDING Msi detection method failed

[micdam]

I,
i create an application for an msi and it fails with thi error:
it seems the detection method failed , i changed the detection method using folder searc or registry key but it alaways fails




OR



OR






The error code 0x87d00324 (-2016410844) but the setup process will work and after few minutes was installed.

here the logs
CITaskMgr.log:
###############################
![LOG[State transition to (ExecutionFailure), Param(-2016410844) : CITask(ScopeId_7192767D-1971-4A16-AA90-BC19073048AF/DeploymentType_da2c6721-0f72-4173-9751-7688161c6dc8.1..Install.Enforce)]LOG]!><time="16:58:27.233-120" date="09-05-2018" component="CITaskMgr" context="" type="1" thread="1724" file="citask.cpp:1311">
<![LOG[State transition to (ExecutionFailure), Param(-2016410844) : CTaskConsumer(ScopeId_7192767D-1971-4A16-AA90-BC19073048AF/DeploymentType_da2c6721-0f72-4173-9751-7688161c6dc8.1.{1B4FD9AA-F1C1-4C4D-8D2D-900C61B9F3AC})]LOG]!><time="16:58:27.233-120"
date="09-05-2018" component="CITaskMgr" context="" type="1" thread="1724" file="citaskconsumer.cpp:387">
#############################


CIAgent.log
########################
Line 286: <![LOG[CCIInfo::SetError - Setting CI level error to (0x87d00324).]LOG]!><time="16:58:27.355-120" date="09-05-2018" component="CIAgent" context="" type="2" thread="11372" file="ciinfo.cpp:1397">
Line 475: <![LOG[CCIInfo::SetError - Setting CI level error to (0x87d00324).]LOG]!><time="16:59:05.411-120" date="09-05-2018" component="CIAgent" context="" type="2" thread="4408" file="ciinfo.cpp:1397">
##########################

 

[Edy]

with the reg key detection method, just select the option "This registry settings must exist". Better yet, install the app on your machine and then when adding the clause, just browse to the reg key that is already in place. i never had any issue with using the uninstall reg key of the product.

 

[Prajwal Desai]

curious to understand why didn't the second detection method work (msi product code).

 

[micdam]

But the better key to select is
HKEY_LOCAL_MACHINE\SOFTWARE\Bitdefender
or under the branch :
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Endpoint Security

thanks

 

[Prajwal Desai]

You can go with first option.

 

[Edy]

am pretty sure the uninstall string is located here HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall

 

[micdam]

curious to understand why didn't the second detection method work (msi product code).

perhaps the msi has been created with ORCA?

 

[micdam]

You can go with first option.

do you mean
But the better key to select is
HKEY_LOCAL_MACHINE\SOFTWARE\Bitdefender ?

 

[micdam]

am pretty sure the uninstall string is located here HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall

there is no reg key under HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall

for bitdefender

 

[Prajwal Desai]

perhaps the msi has been created with ORCA?

Did you check if the product picked up by SCCM actually matches with that of app ?.

 

[Prajwal Desai]

do you mean
But the better key to select is
HKEY_LOCAL_MACHINE\SOFTWARE\Bitdefender ?

Yes

 

[micdam]

Yes

It doesn't work
the error is the same but the installation goes on

 

[Edy]

based on what other people said, it is possible that you still have other Endpoint Protection installed on the machine? they said you would need to uninstall them first.

 

[micdam]

based on what other people said, it is possible that you still have other Endpoint Protection installed on the machine? they said you would need to uninstall them first.

No because i,m trying to install the endpoint in this phase
it seems it is only the detection method that fails because the installation goes on silently and after some minutes it end succesfully as i'm aspecting


the OS is just installed with sccm os task sequence without any endpoint

 

[Edy]

as a workaround, you can actually use a script to create a text file with your deployment and set your detection method to detect that text file.

 

[micdam]

as a workaround, you can actually use a script to create a text file with your deployment and set your detection method to detect that text file.

That is to say?


have you got any exaple to suggest me or a web link to visit?

 

[Olivier]

Hi,
I was facing the same kind of problem.
An MSI application deployed to users was failing MSI detection method.
The same application with same MSI detection method worked with deployment on computers instead of users.
The particularity was that this application had been installed during task sequence.
I reinstalled the computer with TS but without the application, then installed the application deployed to users, and now the MSI detection is working.
I suspect a bug on MSI detection method for an application deployed on users if it has been installed by TS.

 

[Edy]

Hi,
I was facing the same kind of problem.
An MSI application deployed to users was failing MSI detection method.
The same application with same MSI detection method worked with deployment on computers instead of users.
The particularity was that this application had been installed during task sequence.
I reinstalled the computer with TS but without the application, then installed the application deployed to users, and now the MSI detection is working.
I suspect a bug on MSI detection method for an application deployed on users if it has been installed by TS.

You have to bear in mind that the detection method for users and computers maybe different. As an example, the registry keys for users and computers are in different locations. Installation for users normally would be under hkcu not hklm. You need to be careful what you use for the detection method.

 

[Olivier]

I am using the MSI detection method :

 

[Edy]

I am using the MSI detection method :
View attachment 1989

when you deployed the app to user, check if the Product Code exist by running the command below on Powershell

get-wmiobject Win32_Product | Format-Table IdentifyingNumber, Name, LocalPackage -AutoSize

. do the same for computer.