Quantcast
Channel: Adobe Community: Message List - Deployment for Creative Cloud for Team, Enterprise, & CS
Viewing all articles
Browse latest Browse all 13660

Re: Creative Cloud Packager 1.2 Builds error on Install...

$
0
0

Hi eacraft,

Please quit CC desktop if running at the backend and try installing in the given sequence:

 

Note: It is recommended that Creative Cloud Packager should not be installed on a system where one or more Creative Suite products or Creative Cloud Manager products have been installed.

Adobe Application Manager 3.1 and Creative Cloud Packager can be installed and used on the same machine. However, they should not be running simultaneously for package creation.

 

Sequence of installation of packages in the Exceptions folder

 

Except for Acrobat for Windows, all packages in the Exceptions folder should be deployed afteryou have deployed the main MSI or PKG package. However, Acrobat for Windows should be deployed before you deploy the main package.

Therefore, if you are using Exceptions Deployer Application to deploy Acrobat on Windows, you should run Exceptions Deployer Application before deploying the main MSI package. For all other packages, you run Exceptions Deployer Application after deploying the main packages. If theExceptions folder contains Acrobat for Windows as well as other packages, you run Exceptions Deployer Application twice—once before deploying the main MSI package (this will deploy Acrobat for WIndows) and once after deploying the main MSI package (this will deploy the other packages).

 

Please check for any conflicting processes if running at the backend: http://helpx.adobe.com/creative-cloud/packager/resolving-process-confl icts.html

 

Regards,

Romit Sinha


Viewing all articles
Browse latest Browse all 13660

Trending Articles