creative cloud packager 1.6: walk-through presentation · pdf filedownload creative cloud...

© 2014 Adobe Systems Incorporated. All Rights Reserved.

Creative Cloud Packager 1.6: Walk-through Presentation Steve Adler | Senior Solutions Consultant | Education Team

1 Rev. 1.6B

Table of Contents Packaging Workflow

Packaging Creative Cloud for Enterprise

Creating a License File

Packaging Captivate

Resource Links

Ports and Troubleshooting


Workflow for IT Administrators (internet required)

Deploy Package and Exceptions

Package Software

Use Creative Cloud Packager to package software (Adobe ID required)

Download Adobe Installers

Software downloaded from Creative Cloud by CCP ( or Optional Media)

Serial Number (if not using Named Deployment)

Get Serial Number from Adobe Licensing Website (LWS)

Packaging Tool

Obtain CCP from Adobe Licensing Website or from the Adobe Enterprise Dashboard


Creative Cloud Packager

Package the following products:

§  Creative Cloud for teams

§  Creative Cloud for enterprise

§  Captivate

§  Presenter

§  FrameMaker

§  Technical Communicators Suite

§  Photoshop Elements (Mac only)

§  Premiere Elements (Mac only)

3

Converts Adobe’s proprietary installers to industry-standard installers: MSI for Windows PKG for Mac


Packaging Creative Cloud for enterprise with the Creative Cloud Packager

4


Step 1: Log into Adobe Licensing Website

1.  Go to http://licensing.adobe.com

2.  Get your CCE Serial Number If Named Deployment is not being used

3.  Download Creative Cloud Packager


Adobe Licensing Website (LWS)


Step 2: Get your CC Serial Number

What’s the difference between a video and non-video serial number? Adobe video products include Third Party Components that won’t run properly without using a Video Serial Number.

If your package includes any of the Adobe Video/Audio applications at right, use the Video Serial Number.

Adobe Products which require a Video Serial Number Adobe Premiere Pro Adobe After Effects Adobe Audition Adobe SpeedGrade Adobe Prelude


Step 3: Install Creative Cloud Packager

Launcher Application Installs the Creative Cloud Packager

Important Note You’ll need a Macintosh to package Mac applications

You’ll need a Windows PC to package Windows applications

(64-bit recommended)


Step 4: Accept License Agreement for Creative Cloud Packager

Accept the License Agreement


Step 5: Select the Enterprise Option


[email protected]

Best Practice: Use an Institutional Adobe ID Note: We recommend using an institutional ID such as [email protected] rather than an individual’s email address. You can create a forward, alias or distribution list for this purpose.

l l l l l l

Step 6: Log in with your CC Admin Credentials (internet required)


A.  Name the package B.  Choose a Save location

A BDesign Team Package C:\Users\IT_Admin\Desktop

Step 7: Name and Configure the Package


Design Team Package C:\Users\IT_Admin\Desktop


C

Choose Serial Number License to package for traditional deployment: No log-in required, no access to cloud services or storage

DChoose Named License to manage users via the Adobe Enterprise Dashboard or as Trial Software




E

E. Choose 32 or 64-bit package (Windows only)


E. Click for Additional Options


F



Advanced Configuration Options

Mac Screen Shown Cannot disable AIR

via CCP Windows

When enabled, this option redirects updates to your own internal Adobe update server.

When on, this option allows Admin users to update the software on their own.

This option (default) turns off the ability for users to update on their own. IT will manage and deploy updates.

The CC Desktop application is a multipurpose utility which requires end-user administrative privileges and internet access. This option is disabled by default for Creative Cloud for enterprise.


Step 8: Enter Volume Serial Number (internet required)

1234 5678 3366 2202 4011 9055

NOTE Not required for

Named User Deployment

Example is not a

valid serial number


Step 9: Select Package Language (internet required)

Select Package Language*

27 Languages available

For each language option, a new package must be created.

See this link for a list of supported languages by application or service.

New binary builds for 2014


Step 10: Select Applications to Package (internet required)

Enable this option to select and package previous versions

Indicates item has been partially downloaded and updates need to be downloaded.

Indicates item has been fully downloaded and is ready to package.


Click to Package

Start Packaging (internet required)


Package Complete (internet required)

Top Tip Creative Cloud applications are large. A full download is over 12GB

To save time, select all the apps and build a Creative Cloud Complete Package and let them download after you leave for the day.

All of the installers will be cached which will allow you to quickly build your other packages.


Installers

Exceptions require additional steps to deploy to end-user workstations.

Find the Package Folder


Installer MSI or PKG file

Build Folder: Installers

Uninstall Package file on Mac

On Windows, use the MSI uninstall command: msiexec /uninstall <pkg_name>.msi /quiet


Exceptions Folder

Exceptions require additional steps to deploy. See: Deploying Exceptions http://www.adobe.com/go/ccp_exceptions

Exceptions Deployer app may be run to push down exceptions to clients.

Exceptions are only on Windows – To avoid the exceptions process, see best practices


Exceptions

§  Acrobat XI Pro (Windows only)

§  Must be deployed separately and before the rest of the CC apps as an exception

§  CCP serializes Acrobat during the install

§  Alternative Solution – Use the Acrobat Customization Wizard and package with separate SN.

§  Muse CC 2014 (Windows only)

§  Must be deployed as an exception on Windows

§  Muse requires an AdobeID at launch for end-users

§  For more details about deploying Muse, see: http://helpx.adobe.com/creative-cloud/packager/installing-products-exception-folder.html#If you are installing Adobe Muse

§  Adobe Lightroom (Windows only)

Recommendation If your organization already has an approved, working package of Acrobat, use that instead of packaging Acrobat as an exception.


Packager Preferences

Click for Preferences


Cache folder for Downloads

The Creative Cloud Packager caches downloads. You can set your preferred download folder or purge the download cache to save disk space.


28

How do I learn about updates?

Keep up to date with the latest Creative Cloud Updates

https://blogs.adobe.com/creativecloudenterpriseupdates


Deployment & Update Management

Local Adobe Update Server

Client Machines with Adobe Remote Update Manager (RUM)

CC Apps & Updates

Deployment

MSI or PKG

Online

Optional

Offline

IT Admin with CCP


Option: Packaging Updates only (internet required)

Click to see available updates

Note: All CC patches are cumulative.


Option: Packaging Updates only (internet required)

Deselect to create an update-only package


Command Line Tools Installed with the Creative Cloud Packager

32

Windows: C:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp\CCP\utilities

Mac: Applications/Utilities/Adobe Application Manager/CCP/utilities

AUSST

Adobe Update Server Setup Tool §  Used to configure an in-house Adobe

Update Server

RUM

Remote Update Manager

§  Remotely update end-user CC installations

§  Apply silently to non-admin users

XDA*

Exceptions Deployer Application

§  Utility to help push out components which CCP cannot package

APTEE Adobe Provisioning Toolkit Enterprise Edition §  Post Serialization §  Re-Serialization

* Found in the main CCP folder

© 2013 Adobe Systems Incorporated. All Rights Reserved. 33

In a crunch to deploy?

Reduce the number of different packages for use in your institution A majority of machines can benefit from common package deployment •  Logical collections of Apps that work together create efficiencies in

deployment

Cover the majority of your machines first and then deploy to the machines requiring exceptions. Consider a separate install of Acrobat using the Acrobat Customization Wizard Consider a Lightroom reduced distribution •  For departments of labs that require Lightroom (Win)


Build Packages in useful bundles

Video Bundle Bridge CC and Updates After Effects CC (2014) Audition CC (2014) Media Encoder (2014) Prelude CC (2014) Premiere Pro CC (2014) SpeedGrade CC (2014) Design Bundle Bridge CC and Updates Illustrator CC (2014) InDesign CC (2014) Muse CC (2014) * Photoshop CC (2014) Media Encoder CC (2014) Edge Animate CC (2014)

Web Bundle Bridge CC and Updates Dreamweaver CC (2014) Photoshop CC (2014) Edge Animate CC (2014) Media Encoder (2014) Muse CC (2014) * Fireworks CS6 & updates Acrobat Pro – Win – Package with Separate SN and Customization Wizard Acrobat Pro – Mac - Package with Separate SN and Customization Wizard *Muse CC (2014) – Exception process on Windows


Consider Add-on Bundles for Web and Gaming Development

By request or for limited distribution Web Developer Add-on (by request) Edge Inspect CC (requires Admin Access to use) Edge Reflow CC (Preview) Edge Code CC (Preview) ExtendScript Toolkit CC (requires Admin Access to use) Gaming Developer Bundle (by request) Gaming SDK 1.3 Flash Professional CC and Mobile (2014) Flash Builder Premium Adobe Scout CC


Consider Separate installs for Exceptions (Windows only)

* Separate Installs Acrobat Pro – Win – Package with Separate SN and Acrobat Customization Wizard Acrobat Pro – Mac – Can be included in other packages or can be packaged with Separate SN and Acrobat Customization Wizard LightRoom 5 – Exception on Windows *Muse CC (2014) – Exception on Windows follow exceptions process InCopy CC (2014) (requires shared network folder access for collaboration)


Appendix 1: Preparing and Testing

37


Preparing and Testing Packages

http://helpx.adobe.com/creative-cloud/packager/preparing-deploy.htmlCreating packages

In order to create packages, you should: •  Read the Creating Packages article, which walks you through

invoking and using the CC Packager. •  Know where the CC Packager is installed on the

administrative machine. •  When all of the planning is completed, create all of your

packages, using the information you created in the planning stage.

•  When you are finished creating the packages, you should test them before deployment.

Note: you should not package on a system that contains extracted CC applications – see next slide


Uninstalling Packages

http://helpx.adobe.com/creative-cloud/packager/preparing-deploy.html To remove CC packagers from a machine •  For an install package, run the package uninstaller program on the system.

You can do this with with the uninstall file located in the build folder:

•  Or the MSI/PKG package: •  On Windows, use the MSI uninstall command:

•  msiexec /uninstall <pkg_name>.msi /quiet •  On Mac OS, use the following command:

•  sudo installer -pkg <uninstall_pkg_name> -target / •  When the uninstall is finished, check the install location to see that the

applications were removed. (Use the Creative Cloud Cleaner Tool) •  http://helpx.adobe.com/creative-suite/kb/cs5-cleaner-tool-installation-

problems.html •  Run the cleaner tool and restart

•  You can also use a network management system to uninstall


Appendix 2: Ports & Troubleshooting

40


Ports & Hostnames Required for Creative Cloud Packager

Address Ports

ccmdls.adobe.com 443

ims-na1.adobelogin.com 80 443

ims-prod06.adobelogin.com 443

na1r.services.adobe.com 80 443

prod-rel-ffc-ccm.oobesaas.adobe.com 443

lm.licenses.adobe.com 80 443

ccmdl.adobe.com 80

swupmf.adobe.com 80

swupdl.adobe.com 80

41

The following host/port combinations may need to be whitelisted in order to package Creative Cloud for Enterprise:


Problems? Check the CCP Log Files

§  Creative Cloud Packager fails and won’t run? Open the pdapp.log file in a text editor and search for “ERROR” or “FATAL”

§  Windows: %temp%

§  Mac OS: ~/Library/Logs/

§  Errors running the Creative Cloud Packager? Open the Package Builder log file in a text editor

§  Windows: %temp%

§  Mac OS: ~/Library/Logs/ Package Builder log is named as follows: AdobePBhhmmss_ddmmyy.log where hhmmss_ddmmyy = hour|minute|second_date|month|year

§  View the list of common installation and launch log errors

§  http://helpx.adobe.com/x-productkb/global/installation-launch-log-errors-creative.html

42


Appendix 3: Creating a License File

43


Why create a License File?

Convert a Trial license to a Serialized License Convert a Serialized License to a Trial or Named User License Migrate from Creative Cloud for teams to Creative Cloud for enterprise.

44

Solve the common serialization issues with the Creative Cloud Packager


Step 1: Create License File


A.  Name the package B.  Choose a Save location

A BSerialize Design Team C:\Users\IT_Admin\Desktop

Step 2: Name the Package and Set Save Location


Step 3: Enter Volume Serial Number (internet required)

8555 9021 4988 7541 2323 5002

Example is not a valid serial

number


Build Complete


Serialization

Remove a Volume Serialize Number

Installer Folder for Serialization

Mac


Packaging Adobe Captivate Please contact you SC for more information

50


Appendix 5: Resource Links

51


Creative Cloud Resources

52

•  CREATIVE CLOUD DOCUMENTATION

http://tinyurl.com/ccenterprise

•  EDU DEPLOYMENT PRIMER

http://tinyurl.com/edudeploy

• CC PACKAGER DOCUMENTATION

http://tinyurl.com/ccpackager

• CREATIVE CLOUD TECHNICAL REQUIREMENTS

http://tinyurl.com/cctechnical

• ENTERPRISE TOOLKIT FOR ACROBAT

http://tinyurl.com/acroetk

• WHAT’S NEW IN CREATIVE CLOUD

http://tinyurl.com/ccnewfeatures


Resources

§  Creative Cloud Updates Blog https://blogs.adobe.com/creativecloudenterpriseupdates/

§  Creative Cloud Packager Help http://helpx.adobe.com/creative-cloud/packager.html

§  Deploying Exceptions http://www.adobe.com/go/ccp_exceptions

§  Deploying Muse CC 2014 http://helpx.adobe.com/creative-cloud/packager/installing-products-exception-folder.html#If you are installing Adobe Muse

§  Creative Cloud for Enterprise Help http://helpx.adobe.com/creative-cloud/creative-cloud-enterprise.html

§  Adobe Installation and Licensing Blog http://blogs.adobe.com/oobe/

§  Acrobat Enterprise Toolkit for Acrobat http://www.adobe.com/devnet-docs/acrobatetk/

§  Deploying Adobe Acrobat with the Creative Cloud http://helpx.adobe.com/creative-cloud/packager/deploying-acrobat.html


Resources

§  Deploying Adobe packages with ARD http://helpx.adobe.com/creative-cloud/packager/deploying-packages-ard.html

§  Deploying Adobe packages with SCCM http://helpx.adobe.com/creative-cloud/packager/deploying-packages-sccm.html

§  Deploying Adobe Packages with Third Party Tools http://helpx.adobe.com/creative-cloud/packager/using-third-party-deployment-tools.html

§  Using the Remote Update Manager (RUM) http://helpx.adobe.com/creative-cloud/packager/using-remote-update-manager.html

§  Using the Update Server Setup Tool (AUSST) http://helpx.adobe.com/creative-cloud/packager/update-server-setup-tool.html

§  Creative Cloud for enterprise Network Endpoints http://helpx.adobe.com/content/dam/help/attachments/Creative_Cloud_for_enterprise_Service_Endpoints.pdf


Adobe Enterprise Dashboard Resources

§  Adobe Enterprise Dashboard Help http://helpx.adobe.com/creative-cloud-enterprise/help/aedash.html

§  Introduction to Adobe Enterprise Dashboard (Video) https://tv.adobe.com/watch/creative-cloud-for-enterprise/introduction-to-adobe-enterprise-dashboard/

creative cloud packager 1.6: walk-through presentation · pdf filedownload creative cloud...

Documents