Skip to main content

We're in the process of configuring another Jamf instance for a separate group. One issue I'm running in to is with a specific package we created using Composer. After a tech enrolls the device, they run a self-service Audit Check and it checks to make sure the 6 security tools are running. When it runs, it copies a script to the /Shared folder and then runs the script. We use the same package in our Prod and QA site, but for the new site, when you run it, it always errors out. I've even tried creating the pkg again.

Error


Downloading https://xxx.jamfcloud.com/jcds/downloads/Audit_Script.pkg...
Verifying package integrity...
Installing Audit_Script.pkg...
Installation failed. The installer reported: installer: Error - the package path specified was invalid: '/Library/Application Support/JAMF/Downloads/Audit_Script.pkg'.

 

@SMR1 Do you have Composer set to sign packages with the certificate from your original JSS? Try turning off signing if so.

Hi @SMR1 ,


Did you apply the following settings when creating the .pkg in Jamf Composer?



  1. Change file ownership to Root and group to Admin.
             

  2. Apply the following permissions to all folders, subfolders, and files:

    • Apply Permissions to Applications and All Enclosed Items

    • Apply Owner and Group to Applications and All Enclosed Items

    • Apply Owner to Applications and All Enclosed Items

    • Apply Group to Applications and All Enclosed Items

    • Apply Mode to Applications and All Enclosed Items


       






I have applied these settings, and my packages always work successfully.


 

try giving the Path in quotes "/Library/Application Support/Jamf/Downloads/Audit_script", The error says that the path is invalid, or try giving the path as 


/Library/Application\\ Support/Jamf/Downloads/Audit_script

@SMR1 Do you have Composer set to sign packages with the certificate from your original JSS? Try turning off signing if so.


@sdagley I don't have it set to sign with anything. I did have to create 2 other packages, but those both worked fine, it's just the Audit one.

Hi @SMR1 ,


Did you apply the following settings when creating the .pkg in Jamf Composer?



  1. Change file ownership to Root and group to Admin.
             

  2. Apply the following permissions to all folders, subfolders, and files:

    • Apply Permissions to Applications and All Enclosed Items

    • Apply Owner and Group to Applications and All Enclosed Items

    • Apply Owner to Applications and All Enclosed Items

    • Apply Group to Applications and All Enclosed Items

    • Apply Mode to Applications and All Enclosed Items


       






I have applied these settings, and my packages always work successfully.


 


@agungsujiwo Yes, the permissions are set correctly. I've created 2 other packages and they both work fine.

try giving the Path in quotes "/Library/Application Support/Jamf/Downloads/Audit_script", The error says that the path is invalid, or try giving the path as 


/Library/Application\\ Support/Jamf/Downloads/Audit_script


@Shyamsundar I'm not pointing it to that path, I'm assuming Jamf is trying to add it there prior to installing it. On the device I enrolled, it shows that the path does exist. 

I just think it's weird that the same package works in Prod and QA, but not the new site. Unless there is some configurations missing.

@sdagley I don't have it set to sign with anything. I did have to create 2 other packages, but those both worked fine, it's just the Audit one.


@SMR1 If you examine that package with Suspicious Package does it report any errors?

@SMR1 If you examine that package with Suspicious Package does it report any errors?


I did not, because I just downloaded the working pkg from our Prod site and used that. Since that didn't work, I tried creating a new pkg.

I did not, because I just downloaded the working pkg from our Prod site and used that. Since that didn't work, I tried creating a new pkg.


@SMR1 Take a look at install.log on a Mac exhibiting the problem and try to isolate the messages for the failed install to see if they're more informative that what Jamf reported in the policy log (and post them if you'd like the peanut gallery to look for clues)

@SMR1 Take a look at install.log on a Mac exhibiting the problem and try to isolate the messages for the failed install to see if they're more informative that what Jamf reported in the policy log (and post them if you'd like the peanut gallery to look for clues)


@sdagley I didn't get information from there, but I did try creating some other packages using composer, but the same thing happen's. I'll do some more digging and maybe open a case. Thanks for the assistance as always.

Reply


Terms & ConditionsCookie settings