Detection rule keeps failing

Question

Detection rule keeps failing

Draconna 486

Hello I have an application (Avaya One X) which installs ok, but the detection keeps failing so in software center it will say "failed". If I point it to the installation path, that does not work and there does not appear to be a registry entry for Avaya. The install only works as a application, I already tried a package. I have also tried to lookup documentation online but haven't found anything as of yet to help me with it. Thank you.

Answer accepted by question author

2 additional answers

Your answer

Answer 1

Nathan Giannini 161

@Draconna Have you tried using a custom script as the detection method? I find PowerShell pretty reliable and something simple like this should do the trick

$path =  "${env:ProgramFiles(x86)}\Avaya\Avaya one-X Communicator\onexcui"  
If (Test-Path $path) {  
    Write-Host  "INSTALLED"  
}

Draconna 486 Reputation points

2022-11-14T14:51:59.413+00:00

Thank you Nathan, here is what worked for me. Thanks again, saved me a lot of time trying to get this to work and now I can use this for other difficult apps.

$path = "${env:C:\Program Files (x86)\Avaya\Avaya one-X Communicator\onexcui"
If (Test-Path $path) {
Write-Host "INSTALLED"
}

Answer 2

Rahul Jindal 11,511

If it is onexcui is a folder then adding a \ after Avaya x communicator folder should fix things. If onexcui is a file then add the extension after it.

Answer 3

Pavel yannara Mirochnitchenko 13,426 MVP

Use %ProgramFiles% instead and tick that option to 32bit assiosiation.

Share via

Detection rule keeps failing

2 additional answers

Your answer