error deploying packages - both DMGs and PKGs are failing

BCitc
New Contributor

The error message I get is "Installation failed. The installer reported: installer: Error the package path specified was invalid: '/Library/Application Support/JAMF/Downloads/packagename.pkg'

I have done searches and found one or two that sound similar but say something like 'fixed the http flag and that solved my problem' but offer no explanation about what they fixed.

1 ACCEPTED SOLUTION

Grant_Klingbeil
New Contributor III

What happens if we disable the HTTP tab? Are we able to deploy the packages over AFP/SMB?

With HTTP enabled, it doesn't matter if we switch AFP to SMB because it will prefer to use HTTP first.

View solution in original post

7 REPLIES 7

CasperSally
Valued Contributor II

Make sure that 'everyone' has read access to the caspershare and propogate permissions.

BCitc
New Contributor

That did not work. I get the same error. I've enabled both http and ssh. I have tried the 'require authentication' option under the http tab. I just changed the share to smb from afp and am trying that now.

jarednichols
Honored Contributor

It sounds like permissions on your CasperShare

Grant_Klingbeil
New Contributor III

What happens if we disable the HTTP tab? Are we able to deploy the packages over AFP/SMB?

With HTTP enabled, it doesn't matter if we switch AFP to SMB because it will prefer to use HTTP first.

Grant_Klingbeil
New Contributor III

What happens if we disable the HTTP tab? Are we able to deploy the packages over AFP/SMB?

With HTTP enabled, it doesn't matter if we switch AFP to SMB because it will prefer to use HTTP first.

BCitc
New Contributor

sorry for the delayed response. I disabled http and that did the trick - the log reports the package as successfully deployed. Thank you

Now I just need to figure out what I did wrong with the capture process since the package (an HP printer driver in this case) did not actually install on the target machine.

jarednichols
Honored Contributor

What's your JSS running on? If it's IIS that's providing HTTP/S services you need to add MIME types to handle pkg, mpkg, dmg etc etc. That could explain what you experienced.