if you create a policy to dump your cylance token and the installer package into the root folder on the client machine, then kickoff installer -pkg /CylancePROTECT.pkg -target /
that will get it installed and activated.

@balexander667 has it right. I built a bash script based on Cylance's documentation that dumps it all to the same folder and launches the installer from the directory, using the token as a parameter. It takes some tweaking, but it will work.

Thanks for your input! I was able to successfully create a single Cylance installer that installs with the license BUT once I combine that pkg file in Composer with other apps, the scripts stop working. The most I can do when I combine all the apps is have the installer place the pkg and .sh file in a tmp folder. For whatever reason, even though I am initiating the same script as my single test installer (where Cylance installs fine with the license), it won't install after I combine it with other apps.

it's seems like combining multiple installers in to a single package is probably not the most efficient route to go. For this very reason; when you run into any issues, narrowing down the culprit becomes exponentially more complicated. I would think single app per pkg and then layering policies would be the right move.

While i didn't do my cylance deployment via jamf (it was several years ago and before my employer at the time ponied up for jamf so i used ARD), I think it would make sense to use the "Execute command" option in "File and Processes" of the policy instead of a script for the deployment, just add "installer -pkg /CylancePROTECT.pkg -target /" (no quotes).

the other benefit of single app deployment packages/policies is, that same policy can be added to Self-Service and you'll have less clutter in your admin panel.

Yea, seperate those installers and check this thread about Cylance

https://www.jamf.com/jamf-nation/discussions/19218/installing-cylance-package

The Files and Processes method is what I use. I built the package in Composer to copy the files I need to /private/tmp. I add that package to the Policy and then add the Files and Processes section to call the script I added to the package. It seems to work pretty well for us.

Thank you everyone for your guidance. Just to reiterate, I am only using Composer to create this installer, I AM NOT USING jamf to push any policies (our target machines will not be managed by jamf so I don't have any ability to push any policies, our organization also doesn't have self-service setup).

I might just need to have 2 separate installers since when combining Cylance with other apps seems to break the process.

@Chris_Hafner I actually used your solution to put together my first working instance of Cylance awhile back when we were trying to find a way to push the app! Thank you for that! The problem I am having is that I am only using Composer to bundle Cylance with other apps, but I am not using jamfpro to push any polcies. I am trying to put together an installer that a user can just click and run since our target machines will not be managed on jamfpro.

Ah... OK. Somewhere in the lower middle of that thread is the way in which you would do that. Just make sure that you have a postinstall script added in Composer and use that to place the isntall command, instead of having it run from the policy.

Example:

@Chris_Hafner My original script pointed to the file path of the .sh file and didn't have sudo. I edited the postinstall script to include the sudo command, but now the package installer just fails :(

Do you have any info on the failure?

This is the message I receive after the pkg fails to install.

what are you using to perform the install? (ard?)

The only thing that stands out to me is it seems you don't have your Cylance Token encapsulated, have you checked that cyagent_install_token is being populated with the correct token?

Here is an example of my InstallCylanceProtect.sh

#!/bin/sh
#!/bin/bash

echo 'TOKEN' > /private/tmp/Cylance/cyagent_install_token 
sudo installer -pkg /private/tmp/Cylance/CylancePROTECT.pkg -target /

exit 0

We are handing the users a flashdrive with the pkg file on it, so the user is going to run the installer.

@andrew.clark.viv yes it is the correct token. I have also isolated the Cylance installer and ran the same exact commands (with just the Cylance app) and that seemed to work fine. So something is happening when I combine it with other apps and the postflight script. I spoke with support and they told me that there's not much else I can do. I may just have to have 2 separate installers.

try this as an "after" script with your token info inserted. it works for our environment. sometimes popup still happens but you can bypass that and script will take of your token.

https://github.com/northice/LDMS-Scripts/blob/master/SWD%20%26%20Provisioning%20Scripts/Cylance%20Token%20Replacement/CylanceTokenReplacement.sh

RE Cylance installer:

the first couple of lines of the cylance postinstall script (at least mine) looks like this:

#!/bin/sh

INSTALL_TOKEN_FILE="/tmp/YvUnIpzc2omyt1ln"
if ! [ -e "$INSTALL_TOKEN_FILE" ]
then
    INSTALL_TOKEN_FILE="$(/usr/bin/dirname "$PACKAGE_PATH")/cyagent_install_token"
fi

in my install I perform an echo $TOKEN > /tmp/YvUnIpzc2omyt1ln before running the cylance installer. then it doesn't matter where it installs from and it will pick up the token.

further down the postinstall it runs

if [ -e "/tmp/YvUnIpzc2omyt1ln" ]
then
   /bin/rm /tmp/YvUnIpzc2omyt1ln
fi

so you shouldn't neet to perform manual cleanup. From what I can tell there's nothing identifying, special or unique about the file name YvUnIpzc2omyt1ln and it's just a bunch of random characters - been deploying the standard Cylance pkg like this for a while without issue.