Since the downloaded file is a .zip archive, you'll first need to extract the content of the file.
The extracted folder contains the following file:
- <Package name>_Install.pkg
- <Package name>_Uninstall.pkg
Last updated on
31 Aug 2021
Steps to download Creative Cloud packages for macOS computers using the Adobe Package Downloader.
When creating packages for macOS users in Admin Console, click and run the Adobe Package Downloader to complete package download and save the package to a location of your choice.
Download packages
After you create a package on the Admin Console, the following message indicates that the Adobe Package Downloader is successfully downloaded to your computer.
Follow these steps to use the Adobe Package Downloader to download the macOS package.
In Finder, or in internet browser downloads, double-click the Adobe Package Downloader (.dmg) file.
The Adobe Package Downloader launches.
To get started, double-click the icon.
In the Download screen, you can choose to either download the package to the default location (Downloads folder) or an alternative location. Then click Continue.
Your download will then begin and show it's progress. You can click Learn More for further details about creating and managing packages in the Admin Console.
After the package is downloaded successfully,
click Open in Finder to go to the package location on your computer.
Finally, choose one of the following methods to deploy the package to your end-user computers:
- Install by double-clicking the package file.
- Use third-party tools such as Apple Remote Desktop or Jamf.
Note:
A package is available on the Adobe Admin Console for a maximum of 3 days after you create the package. If you run the Adobe Package Downloader after the package has expired, you will get the following error.
Once the package has expired you will need to recreate a new package in Admin Console and follow the above workflow again.
Install downloaded package
By double-clicking package file
-
-
To install the package, double-click <Package name>_Install.pkg.
-
Click Install.
Using the terminal
-
On the client machine, open the terminal.
-
Run the following command:
sudo installer -pkg <path of Package>/Build/<Package name>_Install.pkg -target /
Uninstall downloaded package
By double-clicking package file
-
Since the file that you download from the Admin Console is a .zip archive. You'll first need to extract the .zip.
The extracted contents contains a Build folder that contains two files:
- <Package name>_Install.pkg
- <Package name>_Uninstall.pkg
-
Double-click <Package name>_Uninstall.pkg.
-
Click Install.
Using the terminal
-
In the terminal, navigate to the folder containing the downloaded package and run the following command:
sudo installer -pkg <path of packageName_Uninstall.pkg > -target /
Issues downloading package
If you experience issues using the Package Downloader, you can find the logs at the following locations:
- ~/Library/Logs/CreativeCloud/ACC/AdobeDownload/DLM.log
- ~/Library/Logs/CreativeCloud/ACC/AdobeDownload/HDInstaller.log
Error codes and solutions
|
Error Code |
Description |
Solution |
|
113 |
Download error. Unable to reach Adobe servers. |
For more details, see How to fix connection errors. |
|
116 |
Download was not completed. |
Your download could not be completed, because we could not create a new directory on your device. Check if you have anti-virus software blocking this download on your device. |
|
118 |
No network available (user is offline) |
|
|
119 |
Server not responding. |
For more details, see How to fix connection errors. |
|
120 |
Insufficient disk space. Please clear space and try again |
Your download could not be completed at this time. Clear files from your device, then try again. |
|
121 |
Error writing to the download file location. |
Your download could not be completed due to your permissions settings on the destination folder. Check the permissions settings on your device and try again. |
|
124 |
Proxy authentication is required |
For details, see How to fix connection errors. |
|
125 |
Invalid URL (for HTTP Error 404) |
For more details, see How to fix connection errors. |