Adobe Plugin Mass Deployment

If you plan to use Managed packages, you can:

• Create a Managed Package with elevated privileges turned on.
• Create pre-configured packages using Adobe Templates.
• Create customized packages that contain any one or more of the following:
  • Adobe apps and services
  • Configuration options
  • Marketplace plugins

Use this package to maintain greater control of the Adobe applications and updates that your users can install.

1. Sign in to the Admin Console and navigate to the Packages > Packages.

2. Click Create a Package.

3. Choose Managed Package and click Next.

   

4. On the Configure screen, select the required options:

   • Choose a Platform: Choose the operating system and the processor support from the following:
     • macOS (Universal)
     • macOS (Intel)
     • macOS (Apple Silicon)
     • Windows (64-bit)
     • Windows (32-bit)
     • Windows (ARM)

   Note: 

   A package made for one operating system and architecture type, cannot be deployed on another.

   • It's necessary to create separate packages for Windows 64-bit, Windows 32-bit, and Windows ARM devices.
   • It's necessary to create separate packages for macOS (Intel) and macOS (Apple Silicon) devices. Alternatively, you can create a macOS (Universal) package, and use this to install apps on both macOS (Intel) and macOS (Apple Silicon) machines.

    

   • Language: Select the language in which to create the package.
   • Use OS Locales: Enable this option to create a package that deploys in the OS language of client machine. The OS language is the default fallback language in which the package is deployed.

5. Click Next.

6. On the Choose Apps screen, click next to the corresponding applications to include them in the package, and then click Next.

    

   Click Next on this step if you need to create a lightweight package (without Adobe apps) that includes either or both of the following:

   • Configuration options
   • Marketplace plugins

   

   Note: 

   If you deploy an application which has special system requirements on an unsupported machine the installer will fail. If required, see the system requirements for the application you are installing.

   App Add-ons: Certain Adobe apps come with Add-ons. So, when you add an app that includes one or more Add-ons, you have the option to include the add-ons in the package you're creating. By default, Add-ons are not included in the package.

   

7. (Not currently available for Windows ARM devices) On the Choose Plugins screen, search and select plug-ins to include in the package, and click Next.

   You can select the Show Compatible Plugins Only check box to display the plug-ins that are compatible with the apps in the package. This filter doesn't appear if you only have the Creative Cloud desktop app in your package.

   To view the list of selected plug-ins, click Selected Plugins.

   Note: 

   The plug-ins that you include in the package do not necessarily need the supporting application to be part of the same package. You can include plug-ins and extensions for apps that are previously installed on your users' computers. Also, if a computer does not have the targeted application for a plug-in, the plug-in is not installed on the computer.

   

8. On the Options screen, choose the required options and select Next.

    

   If you've not selected any apps and have selected one or more plugins, then you have the following options:

   • Create a plugin-only package by keeping the Configuration Options turned off.
   • Create a plugin and configuration package by turning the Configuration Options on.

   To create a configuration-only package, no apps or plugins should be selected. In this case, the Configuration Options switch will not be available, and the Configuration Options screen will be visible.

    

   Creative Cloud Desktop Options:

   • Enable self-service install: Allow users to install and update applications from Apps panel in the Creative Cloud desktop app. Learn more.
   • Allow non-admin to update and install apps: Enable self-service for end users who do not have administrative privileges, to install, and manage their applications and updates. Learn more.
   • Disable auto-update for end users: Ensure that end users will not be able to automatically update their applications via the Creative Cloud desktop app. Learn more.
   • Enable self-service plugin install: Allow end users to install and update plug-ins from the Marketplace tab in Creative Cloud desktop app. If deselected, the users can't browse or install any plug-ins using the Creative Cloud desktop app. Whenever you toggle this option, users must quit and relaunch. Alternatively, they must sign out and sign back into the Creative Cloud desktop app for the changes to reflect. Learn more.
   • Disable file syncing: Suppress the automatic syncing of files to client systems. Useful when you are installing packages in a test environment where you want to suppress file syncing. Read more on disabling file syncing. This option is available for Creative Cloud subscribers in commercial and educational organizations only. It is not available for subscribers in government organizations.
   • Enable browser-based login: By default, users must sign in using the Creative Cloud desktop app. Choose this option to redirect users to sign in via the browser. Learn more.
   • Enable install of beta apps: Enables end users to install and update beta apps from the Creative Cloud desktop app. This means that end users can then go to the Creative Cloud desktop app and install or update these apps. Learn more.
   • Install package to custom install directory: Enables you to install the apps in this package to a custom install directory. The directory is defined in the Packages > Preferences tab in the Admin Console. Learn how to set the Preferences.

    

   Also read about other customization options, in Creative Cloud app & services | Customizations.

   Management Options:

   • Enable Remote Update Manager: Enables the use of Remote Update Manager. Adobe Remote Update Manager lets you remotely run the updater on the client with the benefit of executing as an administrator. Learn more.
   • Redirect to internal update server: Enables you to redirect all updates for this package to an internal update server. The internal server details are specified in an override XML in the Packages > Preferences tab of the Admin Console. Learn how to set the Preferences.
   • (Not currently available for Windows ARM or macOS (Apple Silicon) devices) Create a folder for extensions and include the UPIA command-line tool: This option is enabled if you have plug-ins in the package. It creates a subfolder in the package folder to include extensions to install with the package. For more, see Manage Extensions in packages.
   • Install package to custom install directory: Enables you to install the apps in this package to a custom install directory. The directory is defined in the Packages > Preferences tab in the Admin Console. Learn how to set the Preferences.

9. On the Finalize screen, enter the name of the package, review the package details, included applications, and plug-ins. Then, click Create package.

    

   It displays a message after the build process completes. If the package is built successfully, the message also indicates the time period for which the package is available for download from the Admin Console.

   If you want to check the remaining time for the existing packages in the details pane, click  for the package.

10. In the Save As dialog box, choose a location in your computer to save the package.

11. To download and distribute the package later, click Download for the required package if the package is up to date. If not, click anywhere on the row for the package, click Update in the details drawer that opens to first update the package.