Named_Walkthrough_CCP1.7

Creative Cloud Packager 1.7: Walk-through for CCT Packaging

© 2014 Adobe Systems Incorporated. All Rights Reserved. 1 Rev. 1.7

Workflow for IT Administrators

Packaging Tool

Download CCP from Creative.Adobe.com

Obtain Software

Software downloaded automatically from Creative Cloud by CCP

Package Software

Use Creative Cloud Packager to package software

Deploy Package and Exceptions

© 2014 Adobe Systems Incorporated. All Rights Reserved.

Step 1: Log into Adobe.com

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

© 2014 Adobe Systems Incorporated. All Rights Reserved.

Step 2: Download Creative Cloud Packager

1.  Choose Deployment Tools

© 2014 Adobe Systems Incorporated. All Rights Reserved.

Step 2: Download Creative Cloud Packager

1.  Download Creative Cloud
Packager (CCP) in the

appropriate platforms
2.  A Windows package must

be made on Windows
3.  A Mac package must be

made on a Mac

© 2014 Adobe Systems Incorporated. All Rights Reserved.

Step 3: Install Creative Cloud Packager

Launcher Application

Installs the Creative Cloud Packager

© 2014 Adobe Systems Incorporated. All Rights Reserved.

Step 4: Accept License Agreement for Creative Cloud Packager

Accept the License Agreement

© 2014 Adobe Systems Incorporated. All Rights Reserved.

Step 5: Log in with your VIP Admin Credentials

aka Named License

© 2014 Adobe Systems Incorporated. All Rights Reserved.

Step 5: Log in with your VIP Admin Credentials

[email protected]
l l l l l l

© 2014 Adobe Systems Incorporated. All Rights Reserved.

Step 6: Create a Package

Click here

© 2014 Adobe Systems Incorporated. All Rights Reserved.

Step 7: Name and Configure the Package

A C:\Users\IT_Admin\Desktop B

A.  Name the package
B.  Save to Desktop

© 2014 Adobe Systems Incorporated. All Rights Reserved.

Step 7: Name and Configure the Package

C:\Users\IT_Admin\Desktop

C C). Choose “Named License”

© 2014 Adobe Systems Incorporated. All Rights Reserved.

Step 7: Name and Configure the Package

C:\Users\IT_Admin\Desktop

F F. Click for Additional Options
E

E. Choose to have apps &
updates show in the apps panel

© 2014 Adobe Systems Incorporated. All Rights Reserved.

Step 8: Advanced Configuration Options

\ Disabling AIR will prevent Community
\ Help from being installed
If you are wanting to install all
© 2014 Adobe Systems Incorporated. All Rights Reserved. components of CCT you will want to
deselect this option.

Choose how updates are handled.
Option 1 IT controls and
distributes the updates.
Option 2 admin users can update
without IT intervention.

Step 9: Select Package Language

A) Select Package Language

27 Languages
are available

© 2014 Adobe Systems Incorporated. All Rights Reserved.

Step 10: Choose Creative Cloud apps to Package

B) Select CC Apps to package
C) Enable this option to select
and package CC & CS6 apps

© 2014 Adobe Systems Incorporated. All Rights Reserved.

Option: Packaging Updates only

Click to see available updates Note: All CC
patches are

cumulative.

© 2014 Adobe Systems Incorporated. All Rights Reserved.

How do I learn about updates?

Keep up to date with the latest Creative Cloud updates . . .
https://blogs.adobe.com/creativecloudenterpriseupdates

© 2014 Adobe Systems Incorporated. All Rights Reserved.

18

Step 11: Start Packaging

Click to Package

© 2014 Adobe Systems Incorporated. All Rights Reserved.

Step 12: Package Complete

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 app installers are cached to quickly build other packages.

© 2014 Adobe Systems Incorporated. All Rights Reserved.

Step 13: Find the Package Folder

Deploy entire folder to users Desktop and install from there

Installers

Exceptions require additional steps
Windows only

there are no Mac exceptions

© 2014 Adobe Systems Incorporated. All Rights Reserved.

Build Folder: Installers

Installer MSI
or PKG file

Use Setup.exe to install

© 2014 Adobe Systems Incorporated. All Rights Reserved.

But first go to: Exceptions Folder

Exceptions require additional steps to deploy.
See: Deploying Exceptions
http://www.adobe.com/go/ccp_exceptions
First, read the ExceptionsInfo.txt for instructions

© 2014 Adobe Systems Incorporated. All Rights Reserved.

Windows Exceptions

Acrobat Pro (Windows only)

§  Must be deployed separately and before the rest of the CC apps

§  Advanced tuning of Acrobat are done with the Acrobat Customization Wizard
§  Muse

§  Must be deployed separately on Windows
§  For more details about deploying Muse, see:

http://helpx.adobe.com/muse/kb/deploying-muse-enterprise.html

§  Lightroom

§  For more details about deploying Lightroom, see:
http://helpx.adobe.com/creative-cloud/packager/installing-products-exception-
folder.html

© 2014 Adobe Systems Incorporated. All Rights Reserved.

Packager Preferences

Click for
Preferences

© 2014 Adobe Systems Incorporated. All Rights Reserved.

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.

© 2014 Adobe Systems Incorporated. All Rights Reserved.

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* RUM

Exceptions Deployer Application Remote Update Manager
§  Utility to help push out components §  Remotely update end-user CC
which CCP cannot package installations
§  Apply silently to non-admin users

AUSST APTEE

Adobe Update Server Setup Tool Adobe Provisioning Toolkit Enterprise
§  Used to configure an in-house Adobe Edition
Update Server
§  Post Serialization
§  Re-Serialization

* Found in the main CCP folder 27

© 2014 Adobe Systems Incorporated. All Rights Reserved.

Ports & Hostnames Required for Creative Cloud Packager

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

License ccmdls.adobe.com:443
Validation ims-na1.adobelogin.com:443, 80

Product ims-prod06.adobelogin.com:443
Download prod-rel-ffc.oobesaas.adobe.com:443

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

Packaging lm.licenses.adobe.com:443, 80
Services ccmdl.adobe.com:80

Language swupmf.adobe.com:80
Support
swupdl.adobe.com:80
Adobe ID na1r.services.adobe.com: 80, 443
 
Sign-in

© 2014 Adobe Systems Incorporated. All Rights Reserved.

28

Resources

§  Deploying CCT Video
http://tv.adobe.com/watch/creative-suite-in-the-enterprise/deploying-creative-
cloud-for-teams-with-creative-cloud-packager/

§  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 Adobe Acrobat with the Creative Cloud
http://helpx.adobe.com/creative-cloud/packager/deploying-acrobat.html

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

§  Deploying Muse CC 2014 or Adobe Lightroom (Exceptions)
http://helpx.adobe.com/creative-cloud/packager/installing-products-exception-
folder.html

© 2014 Adobe Systems Incorporated. All Rights Reserved.

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 Network Endpoints
http://adobe.com/content/dam/Adobe/en/devnet/creativesuite/pdfs/
ServiceAndSiteURL_List.pdf

© 2014 Adobe Systems Incorporated. All Rights Reserved.

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

© 2014 Adobe Systems Incorporated. All Rights Reserved. 31

© 2014 Adobe Systems Incorporated. All Rights Reserved.

This
 short
 presenta-on
 is
 designed
 to
 acquaint
 you
 with
 the
 procedures
 and
 tools
 for
 packaging
 Crea-ve
 
Cloud
 for
 Teams.
 You
 can
 also
 view
 these
 as
 notes
 with
 the
 icon
 in
 the
 top
 le=
 in
 PDF
 form.
 

1
 

Let’s
 take
 a
 look
 at
 the
 packaging
 workflow.
 

 
With
 CCT,
 you
 will
 download
 the
 packaging
 tool
 crea-ve.adobe.com.
 
 On
 the
 right
 hand
 side
 of
 the
 
screen
 you
 will
 see
 IT
 tools
 and
 can
 dowload
 the
 packager
 in
 the
 appropriate
 OS.
 The
 new
 Crea-ve
 Cloud
 
Packager
 downloads
 so=ware.
 You
 then
 package
 the
 so=ware
 using
 CCP
 and
 deploy
 as
 usual.
 

 
The
 Crea-ve
 Cloud
 Packager
 is
 available
 for
 both
 Mac
 and
 Windows
 and
 delivers
 standard
 Mac
 PKG
 and
 
Windows
 MSI
 files
 for
 deployment.
 

2
 

The
 first
 step
 is
 to
 log
 into
 the
 Crea-ve.adobe.com
 to
 obtain
 your
 Crea-ve
 Cloud
 Packager
 so=ware.
 
3
 

Next,
 you’ll
 download
 the
 Crea-ve
 Cloud
 Packager.
 Under
 the
 le=
 hand
 column,
 Admin
 Tools
 you
 will
 
find
 Deployment
 Tools,
 click
 for
 the
 op-ons
 to
 download
 CCP.
 You
 will
 need
 to
 download
 for
 the
 
appropriate
 plaUorm
 or
 both
 if
 deploying
 a
 PC
 and
 a
 Mac
 version
 of
 CCT.
 

4
 

You
 will
 need
 to
 download
 
 CCP
 for
 the
 appropriate
 plaUorm
 or
 both
 if
 deploying
 a
 PC
 and
 a
 Mac
 version
 
of
 CCT.
 You
 will
 also
 find
 a
 video
 tutorial
 here
 as
 well.
 

 
The
 Acrobat
 por-on
 is
 only
 if
 you
 have
 purchased
 a
 subscrip-on
 to
 Acrobat
 as
 a
 single
 app
 and
 u-lizes
 a
 
different
 deployment
 methodology.
 We
 have
 a
 deck
 which
 walks
 through
 Acrobat
 as
 a
 single
 app
 
deployment,
 please
 request
 it
 from
 your
 reseller
 or
 Adobe
 representa-ve.
 

5
 

You’ll
 need
 to
 download
 the
 Crea-ve
 Cloud
 Packager
 and
 install
 it.
 
 

 
You’ll
 need
 a
 Mac
 version
 to
 package
 Mac
 so=ware
 and
 a
 Windows
 version
 to
 package
 Windows
 
so=ware.
 

 
Note,
 if
 you
 have
 already
 downloaded
 the
 Crea-ve
 Cloud
 Packager,
 updates
 will
 be
 delivered
 to
 the
 
applica-on
 on
 launch.
 

6
 

A=er
 installa-on,
 you
 will
 need
 to
 accept
 the
 license
 agreement.
 
7
 

CCT
 customers
 should
 select
 the
 op-on
 for
 Crea-ve
 Clouds
 Team
 Customer,
 then
 enter
 the
 AdobeID/
Password
 combo
 used
 to
 access
 crea-ve.adobe.com
 as
 an
 admin.
 

 
Note,
 you
 will
 need
 to
 be
 online
 with
 internet
 access
 to
 use
 the
 Crea-ve
 Cloud
 Packager.
 

8
 

enter
 the
 AdobeID/Password
 combo
 used
 to
 access
 crea-ve.adobe.com
 as
 an
 admin.
 

 
Note,
 you
 will
 need
 to
 be
 online
 with
 internet
 access
 to
 use
 the
 Crea-ve
 Cloud
 Packager.
 

9
 

Then,
 click
 the
 Create
 Package
 bu_on
 

 
edit
 an
 exis-ng
 package.
 It
 must
 have
 been
 created
 with
 CCP
 1.4
 to
 edit.
 

 
In
 CCP
 1.6
 you
 can
 now
 create
 a
 license
 file.
 This
 is
 used
 in
 educa-on
 when
 you
 need
 to
 move
 from
 CCT
 
to
 device
 licenses
 or
 from
 an
 EEA
 to
 device
 licenses.
 Please
 see
 the
 Educa-on
 device
 license
 deck
 for
 
more
 specific
 details.
 

10
 

Give
 the
 package
 a
 name
 (A)
 and
 choose
 the
 save
 loca-on
 (B)
 for
 the
 package.
 
 

 
Save
 the
 file
 to
 your
 local
 machine.
 We
 do
 not
 recommend
 saving
 to
 a
 network
 drive.
 Package
 files
 are
 
large
 and
 can
 run
 to
 mul-ple
 gigabytes.
 If
 the
 file
 transfer
 is
 interrupted,
 the
 package
 will
 fail.
 

 

11
 

Select
 Package
 with
 Named
 License
 from
 the
 License
 Type
 pop-­‐up
 menu.
 
12
 

New
 in
 CCP
 1.7
 the
 Crea-ve
 Cloud
 Desktop
 App
 is
 installed
 (op-on
 E
 above).
 This
 applica-on
 installs
 a
 
shortcut
 icon
 which
 allows
 end
 users
 access
 to
 apps/updates,
 assets
 (their
 storage),
 marketplace,
 
typekit,
 and
 Community
 which
 features
 Behance.
 You
 can
 choose
 to
 turn
 off
 the
 apps
 and
 update
 panel
 
if
 you
 wish
 to
 control
 your
 users
 apps
 and
 the
 updates.
 In
 order
 to
 install
 apps
 or
 updates
 the
 users
 will
 
need
 to
 be
 admins.
 

 
You
 can
 click
 the
 Package
 Configura-on
 link
 (F)
 to
 get
 to
 some
 advanced
 op-ons.
 

13
 

If
 you
 want
 users
 to
 use
 community
 help
 you
 will
 want
 to
 deselect
 this
 op-on.
 
 

 
Generally
 speaking,
 IT
 Admins
 do
 not
 need
 to
 change
 any
 of
 the
 default
 sefngs.
 

 
Update
 Behavior
 
Op-on
 1,
 the
 default
 allows
 you
 IT
 to
 manage
 updates.
 
The
 2nd
 choice
 allows
 admin
 users
 to
 perform
 their
 own
 updates.
 

You
 may,
 op-onally,
 control
 the
 update
 process
 using
 your
 own
 internal
 update
 server.
 
We’ve
 included
 addi-onal
 informa-on
 about
 Adobe’s
 free
 tools
 such
 as
 the
 Adobe
 
Update
 Server
 Setup
 Tool
 (AUSST)
 and
 the
 Remote
 Update
 Manager
 (RUM)
 in
 the
 
appendix
 to
 this
 presenta-on.
 

 
If
 you
 are
 going
 to
 use
 a
 remote
 update
 server,
 you
 will
 want
 to
 enable
 the
 op-on.
 

 
By
 scrolling
 down
 the
 pane
 you
 can
 change
 the
 default
 install
 loca-on.
 

14
 

Select
 the
 Package
 Language
 (A).
 Using
 the
 Crea-ve
 Cloud
 Packager,
 you
 can
 package
 the
 so=ware
 in
 any
 
supported
 language.
 You
 will
 need
 to
 create
 separate
 packages
 for
 each
 language
 you
 want
 to
 install.
 

15
 

Next,
 you’ll
 select
 the
 so=ware
 to
 package
 (B).
 Simply
 click
 the
 checkbox
 next
 to
 the
 applica-on
 you
 
need.
 

 
If
 you
 enable
 “Show
 Archived
 Versions”
 (C),
 CCP
 will
 also
 show
 you
 CS6
 
 versions
 of
 applica-ons.
 See
 
next
 screen
 for
 more
 detail.
 

 

16
 

If
 you
 have
 already
 deployed
 Crea-ve
 Cloud
 apps,
 you
 may
 in
 the
 future
 wish
 to
 deploy
 an
 update.
 

 
Crea-ve
 Cloud
 updates
 and
 upgrades
 are
 no
 longer
 bound
 to
 the
 yearly
 or
 18-­‐month
 release
 cycles
 of
 
the
 past.
 Now,
 Adobe
 is
 delivering
 feature-­‐bearing
 updates
 throughout
 the
 year,
 typically
 each
 month
 
we
 see
 updates
 to
 some
 of
 the
 products.
 

 
If
 you
 twirl
 down
 the
 arrow
 next
 to
 an
 app
 you
 will
 see
 all
 of
 the
 updates
 which
 are
 available
 for
 the
 app.
 
When
 you
 do
 so,
 simply
 deselect
 the
 app
 itself
 –
 in
 this
 case
 Photoshop–
 and
 select
 all
 of
 the
 updates.
 

 
It
 is
 worth
 no-ng
 that
 all
 patches
 for
 Crea-ve
 Cloud
 apps
 are
 cumula-ve.
 

17
 

Unlike
 the
 monolithic
 12-­‐18
 month
 release
 cycle
 of
 the
 past,
 Crea-ve
 Cloud
 apps
 are
 
updated
 more
 or
 less
 con-nuously.
 


 
For
 example,
 since
 the
 June
 release
 of
 Crea-ve
 Cloud,
 we
 have
 had
 a
 significant
 update
 to
 
Photoshop
 which
 introduced
 the
 new
 Generator
 feature
 for
 web
 developers.
 
 

 
Adobe
 updates
 so=ware
 at
 other
 -mes
 for
 OS
 compa-bility,
 bug
 fixes,
 stability
 and
 
security.
 

 
So,
 you
 can
 expect
 the
 cadence
 of
 updates
 to
 increase.
 

 
You
 can
 keep
 up
 with
 the
 latest
 updates
 via
 our
 Crea-ve
 Cloud
 Enterprise
 Update
 blog.
 

18