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

Transcription

1 Creative Cloud Packager 1.6: Walk-through Presentation Steve Adler Senior Solutions Consultant Education Team Table of Contents Packaging Workflow Packaging Creative Cloud for Enterprise Creating a License File Packaging Captivate Resource Links Ports and Troubleshooting 1 Rev. 1.6B

2 Workflow for IT Administrators (internet required) Packaging Tool Obtain CCP from Adobe Licensing Website or from the Adobe Enterprise Dashboard Serial Number (if not using Named Deployment) Get Serial Number from Adobe Licensing Website (LWS) Download Adobe Installers Software downloaded from Creative Cloud by CCP ( or Optional Media) Package Software Use Creative Cloud Packager to package software (Adobe ID required) Deploy Package and Exceptions

3 Creative Cloud Packager Package the following products: Creative Cloud for teams Creative Cloud for enterprise Captivate Presenter FrameMaker Converts Adobe s proprietary installers to industry-standard installers: MSI for Windows PKG for Mac Technical Communicators Suite Photoshop Elements (Mac only) Premiere Elements (Mac only) 3

4 Packaging Creative Cloud for enterprise with the Creative Cloud Packager 4

5 Step 1: Log into Adobe Licensing Website 1. Go to 2. Get your CCE Serial Number If Named Deployment is not being used 3. Download Creative Cloud Packager

6 Adobe Licensing Website (LWS)

7 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

8 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)

9 Step 4: Accept License Agreement for Creative Cloud Packager Accept the License Agreement

10 Step 5: Select the Enterprise Option

11 Step 6: Log in with your CC Admin Credentials (internet required) l l l l l l Best Practice: Use an Institutional Adobe ID Note: We recommend using an institutional ID such as [email protected] rather than an individual s address. You can create a forward, alias or distribution list for this purpose.

12 Step 7: Name and Configure the Package Design Team Package A C:\Users\IT_Admin\Desktop B A. Name the package B. Choose a Save location

13 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 D Choose Named License to manage users via the Adobe Enterprise Dashboard or as Trial Software

14 Step 7: Name and Configure the Package Design Team Package C:\Users\IT_Admin\Desktop E E. Choose 32 or 64-bit package (Windows only)

15 Step 7: Name and Configure the Package Design Team Package C:\Users\IT_Admin\Desktop F E. Click for Additional Options

16 Advanced Configuration Options 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. This option (default) turns off the ability for users to update on their own. IT will manage and deploy updates. When on, this option allows Admin users to update the software on their own. Mac Screen Shown Cannot disable AIR via CCP Windows When enabled, this option redirects updates to your own internal Adobe update server.

17 Step 8: Enter Volume Serial Number (internet required) NOTE Not required for Named User Deployment Example is not a valid serial number

18 Step 9: Select Package Language (internet required) Select Package Language* For each language option, a new package must be created. See this link for a list of supported languages by application or service. 27 Languages available New binary builds for 2014

19 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.

20 Start Packaging (internet required) Click to Package

21 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.

22 Find the Package Folder Installers Exceptions require additional steps to deploy to end-user workstations.

23 Build Folder: Installers Installer MSI or PKG file Uninstall Package file on Mac On Windows, use the MSI uninstall command: msiexec /uninstall <pkg_name>.msi /quiet

24 Exceptions Folder Exceptions require additional steps to deploy. Exceptions Deployer app may be run to push down exceptions to clients. See: Deploying Exceptions Exceptions are only on Windows To avoid the exceptions process, see best practices

25 Exceptions Acrobat XI Pro (Windows only) Recommendation If your organization already has an approved, working package of Acrobat, use that instead of packaging Acrobat as an exception. 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: you are installing Adobe Muse Adobe Lightroom (Windows only)

26 Packager Preferences Click for Preferences

27 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 28

29 Deployment & Update Management MSI or PKG IT Admin with CCP CC Apps & Updates Deployment Local Adobe Update Server Client Machines with Adobe Remote Update Manager (RUM) Online Offline Optional 2013 Adobe Systems Incorporated. All Rights Reserved.

30 Option: Packaging Updates only (internet required) Click to see available updates Note: All CC patches are cumulative.

31 Option: Packaging Updates only (internet required) Deselect to create an update-only package

32 Command Line Tools Installed with the Creative Cloud Packager Windows: C:\Program Files (x86)\common Files\Adobe\OOBE\PDApp\CCP\utilities Mac: Applications/Utilities/Adobe Application Manager/CCP/utilities XDA* Exceptions Deployer Application Utility to help push out components which CCP cannot package RUM Remote Update Manager Remotely update end-user CC installations Apply silently to non-admin users AUSST Adobe Update Server Setup Tool Used to configure an in-house Adobe Update Server APTEE Adobe Provisioning Toolkit Enterprise Edition Post Serialization Re-Serialization * Found in the main CCP folder 32

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) 2013 Adobe Systems Incorporated. All Rights Reserved. 33

34 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 2013 Adobe Systems Incorporated. All Rights Reserved. 34

35 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 2013 Adobe Systems Incorporated. All Rights Reserved. 35

36 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) 2013 Adobe Systems Incorporated. All Rights Reserved. 36

37 Appendix 1: Preparing and Testing 37

38 Preparing and Testing Packages 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

39 Uninstalling Packages 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) Run the cleaner tool and restart

40 Appendix 2: Ports & Troubleshooting 40

41 Ports & Hostnames Required for Creative Cloud Packager The following host/port combinations may need to be whitelisted in order to package Creative Cloud for Enterprise: Address Ports ccmdls.adobe.com 443 ims-na1.adobelogin.com ims-prod06.adobelogin.com 443 na1r.services.adobe.com prod-rel-ffc-ccm.oobesaas.adobe.com 443 lm.licenses.adobe.com ccmdl.adobe.com 80 swupmf.adobe.com 80 swupdl.adobe.com 80 41

42 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 42

43 Appendix 3: Creating a License File 43

44 Why create a License File? Solve the common serialization issues with the Creative Cloud Packager 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

45 Step 1: Create License File

46 Step 2: Name the Package and Set Save Location Serialize Design Team A C:\Users\IT_Admin\Desktop B A. Name the package B. Choose a Save location

47 Step 3: Enter Volume Serial Number (internet required) Example is not a valid serial number

48 Build Complete

49 Installer Folder for Serialization Serialization Mac Remove a Volume Serialize Number

50 Packaging Adobe Captivate Please contact you SC for more information 50

51 Appendix 5: Resource Links 51

52 Creative Cloud Resources CREATIVE CLOUD DOCUMENTATION EDU DEPLOYMENT PRIMER CC PACKAGER DOCUMENTATION CREATIVE CLOUD TECHNICAL REQUIREMENTS ENTERPRISE TOOLKIT FOR ACROBAT WHAT S NEW IN CREATIVE CLOUD Adobe Systems Incorporated. All Rights Reserved. 52

53 Resources Creative Cloud Updates Blog Creative Cloud Packager Help Deploying Exceptions Deploying Muse CC you are installing Adobe Muse Creative Cloud for Enterprise Help Adobe Installation and Licensing Blog Acrobat Enterprise Toolkit for Acrobat Deploying Adobe Acrobat with the Creative Cloud

54 Resources Deploying Adobe packages with ARD Deploying Adobe packages with SCCM Deploying Adobe Packages with Third Party Tools Using the Remote Update Manager (RUM) Using the Update Server Setup Tool (AUSST) Creative Cloud for enterprise Network Endpoints Creative_Cloud_for_enterprise_Service_Endpoints.pdf

55

56 Adobe Enterprise Dashboard Resources Adobe Enterprise Dashboard Help Introduction to Adobe Enterprise Dashboard (Video)