/build/static/layout/Breadcrumb_cap_w.png

My managed install of Dell Threat Defense by Cylance is failing, what am I doing wrong?

RJzDCH.jpeg8TuAWs.jpegHi All, I hae created a package for Dell Threat Defense (Cylance) which I have attempted to push out to 2 test VM Windows 10 machines and 2 physical Windows 10 machines.  I have installed the software on my machine to be Inventoried, ran inventory to get the software into KACE, and have uploaded the .msi as additional files.

I have used the following command line as recommended by Cylance and can be found in their Deployment guide.

msiexec /i DellThreatDefenseSetup_x64.msi /qn PIDKEY=<INSTALLATION TOKEN> LAUNCHAPP=1 /L*v C:\temp\install.log

I have only associated the package with Windows 10 & Windows 8 in both 32bit & 64Bit versions.

My issue is that when the installation takes place, the notification pops up to advise the installation is about to start and then as soon as is disappears the notification that the installation is finished pops up.  The installation has obviously failed as it hasn't taken long enough to install, the app isn't in Services.msc and there's no install folder.
There is not log file created to see what is happening and I can't make sense (don't know where to look) at the K1000 log files.Has anyone had any issues like this before, am I missing a configuration step?  Any help or advise would be greatly appreciated.



5 Comments   [ + ] Show comments
  • In your "full command line"
    have you changed the........
    PIDKEY=<INSTALLATION TOKEN>
    with an....... "Installation token" ??????
    The installation token is something you should have to substitute in that field I believe. - akmagnum 7 years ago
    • Hi, thanks for your response. Yes, I just didn't think it was a good idea to post it up on an internet forum. - 24alpha 7 years ago
  • If you put "msiexec" in your command line, check "Don't prepend msiexec.exe" line - gwir 7 years ago
    • Thanks Gwir, tried that and it doesn't make any difference. - 24alpha 7 years ago
  • Update: When I run runkbot I see the following error:
    Error: CreateProcess failed: (2) The system cannot find the file specified - 24alpha 7 years ago
  • Does Cylance come as a single MSI file....or is it a bunch of files in a folder.
    If so have you zipped up up the files and uploaded to kace? or have you just uploaded the msi file. Wont work if its only the msi file. You need to upload MSI AND all the dependant files in a zip file.
    ALSO don't zip up the folder.......Rather highlight all the folder contents and then zip them up. Or else WONT work.
    Have you checked the system requirements for the software.
    .NET 4.0 is also a must it seems. Have you checked your version - akmagnum 7 years ago
  • Ok, so I removed the .msi and uploaded the .exe file. Changed the command to the following:
    DellThreatDefenseSetup.exe /q PIDKEY=<exampletoken> LAUNCHAPP=1 /L*v C:\temp\install.log /I

    This is now working. Thank you to those that helped me with trouble shooting ideas. - 24alpha 7 years ago

Answers (2)

Posted by: 24alpha 7 years ago
White Belt
1

Ok, so I removed the .msi and uploaded the .exe file.  Changed the command to the following:
DellThreatDefenseSetup.exe /q PIDKEY=<exampletoken> LAUNCHAPP=1 /L*v C:\temp\install.log /I

This is now working.

Posted by: 24alpha 7 years ago
White Belt
1

Ok, so I removed the .msi and uploaded the .exe file.  Changed the command to the following:
DellThreatDefenseSetup.exe /q PIDKEY=<exampletoken> LAUNCHAPP=1 /L*v C:\temp\install.log /I

This is now working.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ