Posted on 11-27-2017 01:16 PM
Since a couple of days, Adobe packages created with CreativeCloudPackager receive beneath error on installing/upgrading through Patch Management.
installer: Error the package path specified was invalid: '/Library/Application Support/JAMF/Downloads/AdobePremiereProCC-12.0.pkg.zip'.
A couple of weeks ago it worked fine in patch management, and it still does for other applications like MSOffice, Skype, Chrome, Firefox.
All devices will fail the patch management policie.
Even when i create new packages on a new fresh machine, this still happens.
When i run the .pkg regular on a machine it works, when we deploy it within a policy it works, or update a existing installation through a policie there are no problems.
So, only through the Patch Management section Adobe install/update packages fail.
anyone an idea?
- Creating new patch management policies
- Creating new fresh packages with CreativeCloudPackager
Executing Patch Policy Adobe Premiere Pro CC Copying AdobePremiereProCC-12.0.pkg.zip... Installing AdobePremiereProCC-12.0.pkg.zip... installer: Error the package path specified was invalid: '/Library/Application Support/JAMF/Downloads/AdobePremiereProCC-12.0.pkg.zip'.
Thijs - bol.com
Posted on 11-27-2017 01:39 PM
I'm getting similar errors with an Adobe package as well. It is odd that the same package works perfectly fine outside of the patch policy.
Posted on 11-28-2017 12:58 AM
@hodgesji Appreciate your response, thanks!
Yea really odd, it went fine with the first batch of 2018 release's, but then it got broke.. :'(
For me, good to hear i am not the only one.
Thijs - bol.com
Posted on 11-28-2017 01:07 PM
Ditto here as well. I have been working with JAMF tech support, but no dice so far.
Posted on 11-28-2017 11:48 PM
Posted on 12-05-2017 05:47 PM
@txhaflaire @hodgesji any luck with this? I have my escalated JAMF call tomorrow so I will keep you posted....unless you have found a magical fix!
Let me know.
Posted on 12-06-2017 03:23 AM
Posted on 12-19-2017 02:18 PM
Adding myself to the list of those seeing this. Hadn't stumbled upon the thread until now, but seeing this across the board on our machines.
Posted on 12-20-2017 12:31 PM
@Taylor.Armstrong & Others, the only workaround for this is to use regular polcies with a smartgroup to deploy the .pkg/update because that is still working fine.
But, fact is Adobe needs to fix or Jamf have to tweak some things.
Thijs - bol.com
Posted on 12-21-2017 01:51 AM
I just ran into this same issue after trying to get adobe installers into patch management.
It happened for Acrobat, photoshop, indesign and illustrator
Posted on 02-02-2018 12:21 AM
Looks like this is still an issue. I'm running Jamf Pro 10.1.1, trying to incorporate Acrobat Pro DC into patch management, and getting the "installer: Error the package path specified was invalid" message
Posted on 02-07-2018 12:01 AM
I'm still sparring with JAMF support to get a solution on this, nothing so far.
Posted on 02-20-2018 01:55 AM
Also got this issue with Acrobat Pro Dc-18.011.20035. Works fine when running through installer or installing it manually. Only fails through Patch Management.
Posted on 02-22-2018 12:21 PM
You can add me to the list of people experiencing this same issue.
Posted on 02-23-2018 10:55 AM
Just FWIW - Acrobat Pro Dc-18.011.20035 working for me through Patch Management in test so far.
Posted on 03-08-2018 10:04 AM
@Taylor.Armstrong any other patches working? What version of the JSS are you running?
Still the same issue for me.
Posted on 03-08-2018 10:59 AM
@jgwatson : Running 10.0 here. I haven't bothered going back to test any other Adobe patches - RUM works well enough for now. All other 3rd party patches seem to work great.
Posted on 04-02-2018 05:56 AM
Issue is still going on, anyone made some progress in this one?
Posted on 04-03-2018 12:14 PM
I'm in the same boat as well. Just uploaded a bunch of updated .pkgs and no joy installing via Patch Management. Jamf.... please advise.
Posted on 04-12-2018 07:53 AM
Posted on 05-16-2018 06:47 AM
Running 10.4.1 with an https DP. Still seeing this problem with patch management and .pkg.zips. You'd think it wouldn't be that tough to have the jamf agent extract the archive locally before installing. Unfortunately we can't edit those patch policies to put something like that in there manually.
Posted on 06-21-2018 07:39 AM
Running into this with the Creative Cloud Desktop app. This really needs to be fixed! I can see it download the .pkg.zip, and then generate a .pkg.unzipped, both in the JAMF Downloads directory, but no joy on installing it.
Posted on 06-21-2018 09:03 AM
I had a case opened and was said it's a known issue :
PI-005423 and says "Adobe installs with new patch management fails".
The product issue was discovered in version 10.1.1, but has not been fixed yet. As a workaround, we should be able to push the package using policy.
Posted on 06-21-2018 01:14 PM
Yeah, that's what we had to resort to. So much for Adobe Patch Management, eh?
Posted on 07-03-2018 07:59 AM
Bump. Come on, JAMF. This needs to be fixed.
Package itself seems fine - I can download locally, unzip, and install w/out any issue.
When running from patch management, it downloads (I can see it in the downloads folder), verifies integrity, then the package deletes itself, and fails saying it cannot find the path.
Everything on my end points to this being a Jamf bug, not an Adobe one (for once!)
Posted on 07-04-2018 12:09 PM
Still needs to be fixed indeed :(
Posted on 07-13-2018 11:16 AM
Just ran into this today as well. Add me to the list ha ha.
Posted on 08-16-2018 10:24 AM
Ditto. Soooo frustrating re: Adobe pkgs.
Posted on 09-11-2018 10:42 AM
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-220.127.116.11.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.
Posted on 10-11-2018 06:25 AM
For my was working, just changing the name of the PKG
For my works!
Posted on 10-13-2018 09:28 AM
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:
Posted on 10-14-2018 02:26 AM
Same issue here as well... Trying workaround.
Posted on 03-15-2019 08:33 AM
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...
Posted on 07-02-2019 02:56 PM
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!
Posted on 07-09-2019 04:30 AM
@NPU-Casper Any news about this? I just ran into the same issue with the Adobe CC Installer, which cannot be used uncompressed.
Posted on 07-24-2019 07:28 AM
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
Posted on 09-13-2019 01:26 PM
@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...
Any help/hint will be greatly appreciated!
Posted on 10-09-2019 09:11 AM
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.
Posted on 11-11-2019 06:40 AM
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?
Posted on 11-14-2019 02:11 AM
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.