@MrR0g3rs What did you set as the ownership and permissions of the install_cylance_with_token.sh file when you used Composer to create the .pkg for it? That error is telling you that the Jamf binary didn't have the necessary permissions to execute the script when your Files and Process command tried to run.
BTW, you might want to consider putting "Security" tools like Cylance on the Mac _after_ your other standard items are installed.
@MrR0g3rs What did you set as the ownership and permissions of the install_cylance_with_token.sh file when you used Composer to create the .pkg for it? That error is telling you that the Jamf binary didn't have the necessary permissions to execute the script when your Files and Process command tried to run.
BTW, you might want to consider putting "Security" tools like Cylance on the Mac _after_ your other standard items are installed.
Thanks. I do have Cylance set to install on enrollment, rather than as a part of the Prestage, is that the right position in the install. So, should the permissions in Composer be set to root?
Thanks. I do have Cylance set to install on enrollment, rather than as a part of the Prestage, is that the right position in the install. So, should the permissions in Composer be set to root?
@MrR0g3rs Make sure in Composer you've given root Read and Execute permissions on that file
Another thing to ask, is are you running multiple policies at Enrollment, or do you have a single policy triggered by Enrollment that then runs a configuration script to trigger additional policies? If the former you should take a look at one of the following:
The DEPNotify app and the DEPNotify-Starter script
The swiftDialog app and @dan-snelson's script to drive it: https://snelson.us/2022/09/setup-your-mac-via-swiftdialog-1-2-7/