04-15-2023 02:25 AM - edited 04-15-2023 02:27 AM
We have recently updated all our lab machines to the latest Adobe apps.
Mostly everything has been ok, however we have had some machines the won't install Acrobat DC.
The acrobat DC package has been installed on over 200 machines, so don't believe it's an issue with the package.
I have created a new package from admin console and it just fails to install if you run in manually. On the problem machines.
I have two policies one to cache the package and one to install packages from cache.
Unsure if this ventura issue as thats where I'm seeing it currently. However.
Probably worth saying this is site wide Adobe upgrade on over 300 machines. So it maybe that I have not found a Monterey machine yet from what I have checked.
Does anyone have any ideas? I'm running out of idea on what it could be.
Thanks
Posted on 04-15-2023 11:41 PM
Hello @tdenton ,
Console version of Adobe Acrobat is Intel based installer and hence I believe this package will false on Apple Silicon based Mac devices where Rosetta is not installed.
-Sam
Posted on 04-17-2023 04:26 AM
I've seen this here and there with Acrobat. On a Mac with Acrobat installed, drag the Adobe Acrobat DC folder into Composer's Source Window. Change permissions to what you like. Create a package.
Try this package on the failed Macs.