![]() Both of these are correct and current for each architecture, and both come from your same identical package!Īdobe have documented the process to convert your current / new Adobe packages to be “compatible” with Apple Silicon deployments here (remember, this is still via Rosetta 2). As per my comments above ( The Current Situation – General Usage) this will only work for applications that are supported on Rosetta 2. The process requires you to open up your current package, delete and insert a hot fix, clear out any quarantine bits from the package and re-upload to your deployment system of choice.Ĭertainly better than nothing, but still not ideal. Oh and one MacAdmin has knocked up a script that can semi-automate the package manipulation process with a copy on the MacAdmins Slack here. Obviously test fully with your own specific use-case and environment! Progress is comingĪdobe are working on bringing full support (as you can imagine!) as fast as possible. No I don’t have insider information, but the following is observable: ADOBE CREATIVE CLOUD FOR MAC M1 FULL The Adobe re-packaging KB ( Deploy packages to Apple Silicon devices) specifically mentions “ Temporary workaround to deploy Named User or Shared Device Licensing packages to Apple desktop devices that use the M1 chip.” (emphasis is mine). ![]() ADOBE CREATIVE CLOUD FOR MAC M1 DOWNLOAD.ADOBE CREATIVE CLOUD FOR MAC M1 SOFTWARE.ADOBE CREATIVE CLOUD FOR MAC M1 INSTALL.
0 Comments
Leave a Reply. |