Patch Management; installer: Error the package path specified was invalid

Just ran into this today as well. Add me to the list ha ha.

Ditto. Soooo frustrating re: Adobe pkgs.

Still a problem in JAMF Pro 10.6.2 (on macOS 10.13.6).

Steps to reproduce:

1.) Adobe CC pkgs (created via a template in the Adobe Admin Console) are downloaded from adobe.com and then added to Jamf Pro via Jamf Admin (which zips the pkg because it has not been a flattened).

2.) These packages are added to a Patch Policy within Jamf Pro Patch Management.

3.) Executing the policy results in the zipped pkg being downloaded from the jss, but failing to install on the client machine. In our case, the reported error is “ installer: Error the package path specified was invalid: '/Library/Application Support/JAMF/Downloads/InDesignCC_Install-13.1.0.76.pkg.zip'.”

My naive assumption is that there is a disconnect between the actual package name that exists on disk after downloading and unzipping, and the pkg name that patch management framework expects to find when it goes to perform the installation.

I haven't yet tried flattening the original adobe pkg prior to uploading to the jss.

For my was working, just changing the name of the PKG

1. Open Jamf Admin application
2. Remove the existing pkg file
3. Change the name of the pkg file on your local computer.
4. Push the pkg file to the repository.
5. Go to the policy affected for this issue and add the new pkg file with the new name.

For my works!

I'm sure most folks have found workarounds while JAMF continues to work on this defect, but here is my workaround in case anyone else is still stumped by this:

https://www.jamf.com/jamf-nation/discussions/26531/patch-management-and-adobe-cc-products#responseChild174188

Same issue here as well... Trying workaround.

Hey guys, I just stumbled across exact the same issue while trying to update the lates MS Office.
Did someone have success with installing PKGs through the Patch Management?
DMGs seem to work just fine though.

Update: I just uploaded the same PKG, but uncompressed. That seems to work for some reason...

Just started to use patch management which I like, using it for Office 2019 and is working well until I ran into Adobe! I have an open case will see what Jamf support says. Thanks!

@NPU-Casper Any news about this? I just ran into the same issue with the Adobe CC Installer, which cannot be used uncompressed.

Any news on this, as ive just come across this trying to roll the latest office updates.
Im not using the pkg within a zip either, im using the direct Office update .pkg files from :https://docs.microsoft.com/en-us/officeupdates/update-history-office-for-mac

Is this still an issue as im on jamf 10.12.0-t1555503901

Cheers all

@ccsshelpdesk & others, I am too experiencing this issues with single app MS pkgs downloaded from macadmins.software and patch policies
Weird thing is patch policies work perfectly on some computer and fail random on few others - using the same, Distribution Points - with the usual message "installer: Error - the package path specified was invalid: '/Library/Application Support/JAMF/Downloads/Microsoft_Excel_16.29.19090802_Installer.pkg'. or any other MS app installer
JSS 10.13 on premise with 10.13.6 & 10.14.6 clients
Login policies with the very same packages work...
Thank you!
Any help/hint will be greatly appreciated!

I am encountering this in MacOS 10.15, running JAMF 10.15.1.

Installation failed. The installer reported: installer: Error - the package path specified was invalid: '/Library/Application Support/JAMF/Downloads/...

If I install from Self Service, it works. If I use JAMF Imaging (only to install packages, no OS), all packages fail with the same error.

**FIXED by creating a Privacy Policy giving Allow access to SystemPolicySysAdminFiles and SystemPolicyAllFiles

Hey @T3Helpdesk two questions: What application are you trying to update and is giving these errors? And to which application did you give the access through PPPC?

I am having this same error when using patch policies to update Zoom. Oddly enough, it seems that all the devices having the problem are running macOS 10.14.6

I tried the workaround of renaming the package and uploading it again, with no success, and the workaround for Adobe updaters wouldn't make much sense with this app.