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.

@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.

Cheers,
Thijs - bol.com

Ditto here as well. I have been working with JAMF tech support, but no dice so far.

@jgwatson Thanks for your reply! keep us posted if you got more intel.

@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.

@jgwatson Hi,

Till now, unfortunately not :(

Cheers,
Thijs - bol.com

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.

@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.

Cheers,
Thijs - bol.com

I just ran into this same issue after trying to get adobe installers into patch management.
It happened for Acrobat, photoshop, indesign and illustrator

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

I'm still sparring with JAMF support to get a solution on this, nothing so far.

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.

You can add me to the list of people experiencing this same issue.

Just FWIW - Acrobat Pro Dc-18.011.20035 working for me through Patch Management in test so far.

@Taylor.Armstrong any other patches working? What version of the JSS are you running?

Still the same issue for me.

@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.

Issue is still going on, anyone made some progress in this one?

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.

@txhaflaire no progress here. Nothing from JAMF.

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.

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.

Hello,
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.

Regards

Yeah, that's what we had to resort to. So much for Adobe Patch Management, eh?

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!)

Still needs to be fixed indeed :(