Log in to the Admin Console and navigate to Packages > Preferences.
The Packages page in the Admin Console provides the following functionality. Use them when you plan to deploy Creative Cloud and Document Cloud applications to end users in your Enterprise.
Creative Cloud Packager is no longer in development and no updates will be provided. Also, Creative Cloud Packager cannot be used to create packages that include Creative Cloud 2019 apps or later. Learn More.
We recommend that you use the create package workflows provided in the Adobe Admin Console.
Download the Creative Cloud Packager, Adobe Extension Manager command-line tool, Adobe Update Server Setup Tool, or Remote Update Manager.
Log in to the Admin Console and navigate to Packages > Tools.
Adobe Creative Cloud Packager makes it easy for you to create packages that contain Adobe Creative Cloud products and updates. These packages can then be deployed to the client machines in your organization.
For more information, see Packager.
Creative Cloud apps released on October 15, 2018 (Creative Cloud 2019) or later are not available in Creative Cloud Packager. For more information, see this document.
Adobe Update Server Setup Tool allows you to set up an on-premise server that hosts Creative Cloud updates. It allows IT to save bandwidth and control when Updates become available for end users.
For more information, see Using Adobe Update Server Setup Tool.
Remote Update Manager allows you to remotely call the updater on a client machine. It allows you to seamlessly manage when your client systems install updates. You can specify a particular product or update all products at the same time. When used with the Adobe Update Server Setup tool, the updates are pulled from your own premise server.
For more information, see Use Adobe Remote Update Manager.
The ExMan command-line tool allows the admin to install extensions and plug-ins from the ZXP file container format. When you create a package, you can select to include extensions or you can download the stand-alone tool for Mac or Windows.
Set preferences for notifications, AUSST, and custom package directories.
Package preferences are local to the logged in Admin. That means, any preferences that you set, apply to you and the packages that you create.
You can choose to receive email notifications for updates available to any Creative Cloud products.
Select Available application versions to display app versions that do not receive security or feature updates.
While creating packages, select Show older versions in the Choose Apps screen.
While Adobe fully supports the latest version of apps, support for older versions is limited. Creative Cloud for enterprise plans also include a designated LTS version that receives security updates. Adobe recommends that you create packages with the latest or LTS versions of the apps. However, if you choose an older app version, see the Creative Cloud Support policy to know the extent to which Adobe provides support for it.
To configure an internal update server, download Adobe Update Server Setup Tool from the Tools section. Next, generate the override file, and paste its contents in the Internal Update Server box.
Also, in the create package workflow, choose this option to redirect updates to the internal update server.
Use this preference to ensure that, if your internal udpate servers is unavailable, your end-user compuers will get Adobe updates from the Adobe servers. Learn more.
If the apps in your packages support custom install directories, specify the directory to which you want the packages to install these apps. For details, see Create packages.
The directory path that you specify must be an absolute path. If you are creating a package to be deployed on Windows computers, specify the path that includes the drive letter. For example: C:\<folder path>.
Also, when creating a folder, you cannot use any of the characters that Windows does not support: \/:*?<>|.