Help Center

Follow

Deploy Adobe Creative Cloud

Purpose:
You wish to deploy Adobe Creative Cloud products using the Creative Cloud Packager provided by Adobe.

IMPORTANT: As some of the comments indicate in our original Silently Install Adobe Creative Cloud blog post, some installations may require the Setup.exe file created by the Creative Cloud Packager rather than the MSI. In those cases, please see the, Adobe Creative Cloud Using the Setup.exe (Instead of the MSI) KB.

Resolution:
Deploying Adobe Creative Cloud products to multiple machines is covered in the following topics:

I. Requirements
II. Considerations
III. 
Download, run, and configure the Creative Cloud Packager
IV. Deploy the created MSI package(s)
V. Troubleshooting deployment issues


I. Requirements:

  • In order to download the Creative Cloud Packager from Adobe, you will need to be an administrator of an Adobe Creative Cloud account.
  • You cannot deploy using Creative Cloud for Individuals (requires Team, Enterprise, or Education Creative Cloud plans).
  • While the deployment method outlined in this article can be accomplished using PDQ Deploy in free mode, changes will need to be made to create separate deployments based, for example, on OS architecture.

II. Considerations:

  • The guidance in this article is focused on Creative Cloud for Teams. The steps for Creative Cloud for Enterprise and Education vary, but should be intuitive enough to allow successful deployment given the general instruction expressed in this article. Where there is significant deviation between Teams and other plans, notes have been provided.
  • Since the size of a Creative Cloud package can be significant, it is recommended you use the Pull copy mode instead of the default Push copy mode (File > Preferences > Performance). This will also require placing the Repository on an accessible file share. For more information, see: PDQ Deploy: Understanding Push and Pull Deployments
  • For the greatest level of performance where multiple file servers exist and the deployment audience is greater than 30 machines, the use of Distributed File System Replication (DFSR) is highly recommended. For more information, see: PDQ Deploy and Microsoft DFS
  • If users do not have local admin access on their respective machines and therefore do not have access to the Creative Cloud App Panel, the Creative Cloud Package can also be used to push out updates to machines with installed Creative Cloud products.

III. Download, run, and configure the Creative Cloud Packager

1. Download the Creative Cloud Packager by logging in to https://www.adobe.com/ and selecting Manage team (or the appropriate management link). In the management window, select Deployment Tools then select the Download Win > package.

2. This will download the CCPLauncher.exe. Launch the executable and login if required.

3. Click on Create Package.

4. Give the package a name, a location where the package should be saved, and the architecture (32 or 64-bit).

5. Select the License Type (see note below) Once the license type has been selected, package configurations will be displayed.

NOTE: Named License is available for the Teams plan. Serial Number License is available for the Enterprise plan, and Device License is available for the education plan. You should only see the applicable license(s) applicable to your account.

6. In Package configurations, de-select the Applications & Updates via the Apps Panel options if the users are not also local administrators.

NOTE: Applications & Updates via the Apps Panel allows for/does the following, if the users are also local administrators:

  • Users are notified of updates by Adobe.
  • Users can install updates from Adobe.
  • Users can install other Creative Cloud programs they are licensed to receive.

If this is not selected, users will not see the Apps Panel and will not be notified of updates or prompts to install available programs.

7. Click Next.

8. Select the appropriate language.

9. Once selected, you will be prompted to select the applications and/or updates you wish to build into your installer. Make the appropriate selection.

NOTE: As indicated in the figure above, for multilingual offices you can also select the Match OS Language, which will install the applications based on OS locale. This negates needing to create multiple packages in specific languages.

10. Once you’ve made the appropriate application and/or update selections, click Build. And wait.

You should now have a directory containing the installer (MSI) for the Creative Cloud products.

IV. Deploy the created MSI package(s)
In the example below, the steps were completed using the above installer. Instead of creating one package, however, two were created, a 32-bit and a 64-bit package. In our test environment, we have both 32 and 64-bit machines and will be testing both by creating one package that deploys to either architecture based on conditions (requires PDQ Deploy Pro or Enterprise*).

1. In PDQ Deploy, click New Package or Ctrl+N from the toolbar or click on File > New Package or right-click the Packages folder in the navigation tree and select New Package.

2. Name the package something reasonable and choose the appropriate Copy Mode (see II. Considerations above) if not already set globally (Pull should be default in your global settings if you have followed the recommendations at the top of this article).

3. Click on Step 1, give the step a title. For the Install File, navigate to the directory where you downloaded the Creative Cloud 32-bit installer (Step 4 above in III. Download, run, and configure the Creative Cloud Packager).

The path will be <DownloadDirectoryx86>\Build\<filename>.msi -in this example, the directories were downloaded into the Repository.

IMPORTANT: Make sure to check Include Entire Directory. If this is not checked, the deployment will fail.

4. Click on the Conditions tab and select the O/S Version. Since Adobe Creative Cloud products will only run on Windows 7 and above, exclude XP and Vista. Exclude servers unless required.

Select the appropriate architecture. Since this step is installing the 32-bit Creative Cloud applications, select 32-bit from Architecture.

5. Add a new Install Step.

6. Click on Step 2, give the step a title. For the Install File, navigate to the directory where you downloaded the Creative Cloud 64-bit installer (Step 4 above in III. Download, run, and configure the Creative Cloud Packager).

The path will be <DownloadDirectoryx64>\Build\<filename>.msi -in this example, the directories were downloaded into the Repository.

IMPORTANT: Make sure to check Include Entire Directory. If this is not checked, the deployment will fail.

7. Click on the Conditions tab and select the O/S Version. Since Adobe Creative Cloud products will only run on Windows 7 and above, exclude XP and Vista. Exclude servers unless required.

Select the appropriate architecture. Since this step is installing the 64-bit Creative Cloud applications, select 64-bit from Architecture.

8. Save the package.

9. Deploy.

IMPORTANT: While we make every effort to test on multiple platforms and architectures, it is highly recommended you test the deployment before a general release into production. Given the possibility of the package being substantially sized, testing will provide important information on bandwidth limitations and deployment times. In our tests, a single instance of Photoshop took anywhere from 15 - 20 minutes to deploy.

*This can be accomplished in Free mode using two separate packages and choosing the appropriate machines to deploy to based on architecture.

V. Troubleshooting Deployment Issues:
If the package deployment fails and/or you receive a 1603 error, please try the following.

  • Machines should be fully patched and not in need of a reboot.
  • Check to ensure sufficient space is available on the drive where Adobe CC will be installed. Some Creative Cloud deployments can be several gigabytes in size, which includes the files copied to the target and the installed size.
  • Clear out %WINDIR%\Temp directory.
  • Review the troubleshooting steps in this article: http://support.adminarsenal.com/entries/448443

See Also:
Adobe:
Create or Edit Packages
Deploy Packages
Installation Parameters

Admin Arsenal:
PDQ Deploy: Understanding Push and Pull Deployments
PDQ Deploy and Microsoft DFS

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk