-
-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Allow uploading .zip files #87
Comments
Do you have any documentation for this? I've always put everything required into a flat package myself. |
I have never really come across any documentation from the Jamf side, this is just something that works (perhaps unofficially?). I have encountered a couple apps where this method works well. The F5 Big-IP Edge Client is one. If you zip the installer package with the configuration file I know that some adobe installers used to run from zip files as well, but I don't deploy those any longer so I'm not sure how things are working today. |
Yes, Adobe CC apps are still bundle-style pkgs and they need to be zipped to upload to Jamf. (The GUI, Jamf Admin and JamfUploader handle that). I just had no idea that you could put extra files in the archive. Did you ever try putting more than one package in the zip? |
Multiple packages in one zip is not something I have ever tried. |
I just tried it, and only one of the packages in the zip was installed (alphabetically it was the second package, so who knows how it chooses which one). So I guess the content beyond the package is only useful if the installer package is looking for it. Still, no reason not to allow JamfUploader to deal with them. I'll add it to the list (well, Issues is the list, so it's already here!). |
Jamf distribution points are capable of accepting .zip files that contain a .pkg (and optionally other config files). The Jamf agent will then unzip the file and run the pkg installer contained within. This is useful when certain installers require some configuration file or other data to be present in the same directory during installation.
I am requesting that JamfPackageUploader support this workflow, if possible.
The text was updated successfully, but these errors were encountered: