To install applications or updates from the Apps panel, users must have administrative privileges. You can also retrospectively enable the Apps panel.
Elevated Privileges This option allows users to manage applications and updates even when they do not have Administrator privileges. Once you have deployed a package with elevated privileges, to revoke the elevated privileges later, you need to create a Creative Cloud desktop app-only package with Elevated Privileges deselected and deploy it.
Package configurations The settings for package configuration include options such as whether to ignore conflicting processes during installation. To review or change the package configuration settings, click Change. The Advanced Configurations screen appears. Adobe Update Manager Behavior: In an individual product installation, the Adobe Application Manager launches automatically every day at 2: The user is not aware of this check unless a product update is found, at which time the application displays a dialog on the end-user machine to inform the user that an update is available.
In addition to suppressing the automatic update behavior, it disables the Update option from the Help menu in the applications; users can no longer actively look for updates on their own. If you choose this option, the IT admin must download and deploy updates for their users. Use internal update server You can choose to redirect the automatic update process to check for updates with your own update server, rather than the Adobe update server.
For this option, it's necessary to host updates on an internal server, and redirect the Adobe Application Manager to look there for updates. You do this by providing the path to an XML configuration file that contains information about the hosted server.
You are recommended not the deploy these configuration files on an admin computer on which you are running Creative Cloud Packager.
You might experience issues during package creation. Remote Update Manager Adobe Remote Update Manager lets you remotely run the updater on the client with the benefit of executing as an administrator. Select this option to enable the use of Remote Update Manager. For more information, see Remote Update Manager. Deploy to default application directory: Specify directory during deployment: Allows the end users to specify the installation path during the deployment of the package.
Enter the path to the location to a specific installation location Adobe Remote Update Manager lets you remotely run the updater on the client with the benefit of executing as an administrator. To save any changes to configuration you made and return to the Package Details screen, click Save.
To return to the Package Details screen without making any changes, click Cancel. However, this configuration change is not saved. In the Package Details screen click Next. If you selected the Enterprise, Government, or Education user account type in the Sign In Screen, and are using a Serial Number License you are prompted to enter the enterprise license key.
If you do not have your enterprise license key, you can find it at licensing. Enter the key and then click Next. The Application and Updates screen appears. Select the checkboxes appropriately.
Core Components is always selected, and you cannot deselect it. This option deploys the common licensing infrastructure to client machines. To create a package that only contains the Creative Cloud for desktop app, enable Adobe Creative Cloud from the Package's Advanced Configurations screen. By default, only the latest versions of the software are displayed.
Enable Show Archived Versions to display a list of archived applications. You can package archived versions of software as well. If the product or update that you selected has already been downloaded to your machine, a Down Arrow appears next to its name.
You can also select the language you want to package in, using the drop-down list on the upper-right side. Ensure that the target devices meet the system requirements of the apps being packaged.
Deploying apps on unsupported systems c give unexpected results. When you package an update for the latest version of some of the applications, you can apply the package to a system that does not already have the base version of the application installed. You can identify such apps with the icon. The latest version of Photoshop update can be installed on a machine that may not have the Photoshop base version. So while creating a package, you can choose to package only the update version for the apps that can be deployed without their base versions.
Browse to the location where the offline media is located. On a Mac, place the DMG file in a directory and browse to that directory. Select the products and updates to package. When you have made your selection, click Done to return to the Application and Updates screen. Click Build to start packaging the selected applications and updates.
It then builds the package. The progress is displayed on the Download Progress and the Build Progress screens. When the build completes successfully, the Summary page appears. This page displays a summary of the products or components included in the build. The name of the folder in which the package is created is displayed on the screen.
Clicking the folder name opens the folder. You can click the Build Log link to see the detailed progress report, including any errors. This file is located in the folder that you specify for the package. This configuration file is for internal use only - do not modify or delete this file.
Deploy packages As part of the build process, two folders are created: The Build folder also contains the following files: For exception media such as msi or exe of latest version of Muse, the exception installer is copied in the following location and the user needs to install this exception separately: This file contains the details of the processes that conflict with the installaion of the applications that you have added to the package.
The file is created as an XML file to allow you to automate the process of managing the conflicting processes. Also, when a user is installing the package, if any of these conflicting processes are running the installation with fail.
These processes should be closed before installing the CCP package.