Named_Walkthrough_CCP1.7

Once
 you’ve
 selected
 all
 of
 the
 apps
 and
 updates,
 you
 are
 ready
 to
 package.
 

 
Click
 the
 Build
 bu_on
 to
 begin
 the
 build
 process.
 

 

19
 

When
 the
 process
 completes,
 you
 will
 see
 the
 Summary
 screen.
 

 
This
 process
 may
 take
 some
 -me
 to
 download
 the
 so=ware.
 

 
You
 can
 build
 various
 packages
 which
 deploy
 only
 certain
 applica-ons
 if
 needed
 for
 different
 groups
 in
 
your
 organiza-on
 or
 you
 can
 deploy
 the
 en-re
 product
 set.
 If
 deploying
 the
 en-re
 product
 set
 it
 will
 take
 
a
 considerable
 amount
 of
 -me.
 

20
 

Let’s
 take
 a
 look
 at
 the
 result
 of
 the
 process.
 

 
You’ll
 see
 a
 build
 folder
 and
 –
 possibly–
 and
 excep-ons
 folder.
 
 

21
 

The
 build
 folder
 contains
 the
 installer
 file
 and
 the
 Adobe
 so=ware
 which
 is
 now
 ready
 to
 push
 down
 to
 
your
 users.
 

 
This
 will
 include
 a
 MSI
 file
 for
 Windows
 or
 a
 PKG
 file
 for
 Mac
 

22
 

The
 Excep-ons
 folder
 contains
 so=ware
 which
 cannot
 be
 packaged
 by
 the
 Crea-ve
 Cloud
 Packager.
 

 
On
 the
 Windows
 plaUorm,
 Adobe
 Acrobat
 and
 Muse
 would
 be
 an
 excep-on.
 If
 you
 are
 deploying
 
Acrobat
 this
 should
 be
 done
 PRIOR
 to
 CC
 installa-on.
 On
 the
 Mac,
 as
 long
 as
 you
 deployed
 Air
 there
 will
 
be
 no
 excep-ons.
 

 
You
 can
 double-­‐click
 the
 Excep-onInfo.txt
 file
 for
 more
 details
 about
 how
 to
 package
 the
 excep-on
 and
 
I’ve
 included
 a
 link
 here
 to
 help
 with
 this.
 

 

23
 

I
 already
 men-oned
 that
 CCP
 may
 create
 an
 Excep-ons
 folder.
 The
 Excep-ons
 folder
 contains
 items
 that
 
need
 addi-onal
 steps
 to
 deploy.
 

 
Acrobat
 Pro
 and
 Adobe
 Muse
 on
 Windows
 requires
 addi-onal
 steps.
 
 

 
CCP
 outputs
 a
 MSI
 file
 which
 you
 should
 use
 with
 your
 standard
 Windows
 deployment
 tool.
 
 

 
Acrobat
 should
 be
 installed
 BEFORE
 the
 rest
 of
 the
 CC
 applica-ons.
 
 

 
When
 the
 CC
 installer
 runs,
 it
 will
 serialize
 Acrobat.
 You
 may
 customize
 Acrobat
 further
 using
 the
 
Acrobat
 Customiza-on
 Wizard,
 just
 don’t
 enter
 a
 serial
 number
 in
 the
 tool.
 

24
 

The
 Crea-ve
 Cloud
 Packager
 has
 some
 Preferences
 you
 can
 control
 .
 .
 .
 
25
 

The
 Crea-ve
 Cloud
 Packager
 caches
 downloads.
 You
 can
 set
 your
 preferred
 download
 folder
 or
 
purge
 the
 download
 cache
 to
 save
 disk
 space.
 So,
 if
 you
 package
 Photoshop,
 you
 won’t
 have
 to
 
download
 it
 again.
 

 

26
 

When you download CCP, a number of command-line utilities are also installed.
I’ve included the path to the installations so you can find them.
•  The Exceptions Deployer Application., which is available at the root of the CCP folder, helps you

package items that CCP cannot directly package. Examples of apps that CCP cannot packager are
Acrobat on Windows or Muse on either platform.
•  The Remote Update Manager– or simply RUM– is a command-line tool that allows you– as an
admin– to remotely push down updates to your Creative users. It may be used in conjunction with
the Adobe Update Server Setup Tool to re-direct those updates to an in-house server where the
updates are stored.
•  The Adobe Update Server Setup tool which is used to configure an in-house update server.
•  The Adobe Provisioning Toolkit allows you to serialize or reserialize Adobe Creative software after
you install it.
•  You may not need to use all of these tools, especially if you also use a third party packaging and
deployment tool.
•  While we’ve offered several of these tools in the past, [ build ]we now include all of these tools in
the CCP download.

 

27
 

The
 Crea-ve
 Cloud
 Packager
 needs
 access
 to
 certain
 Adobe
 hostnames
 and
 
ports
 to
 package
 the
 so=ware.
 
 

 
Our
 latest
 version
 of
 the
 Crea-ve
 Cloud
 Packager
 also
 support
 Proxy
 PAC
 
servers
 for
 organiza-ons
 which
 use
 them.
 

28
 

Here
 are
 some
 resources
 to
 help
 you
 with
 packaging.
 
29
 

Here
 are
 some
 resources
 to
 help
 you
 with
 packaging.
 
30
 

If
 you
 can’t
 get
 the
 Crea-ve
 Cloud
 Packager
 to
 run–
 or
 the
 applica-on
 reports
 errors
 when
 you
 use
 it–
 
checking
 out
 log
 files
 can
 help
 you
 find
 the
 problem.
 

 
If
 Crea-ve
 Cloud
 Packager
 won’t
 run
 at
 all,
 you
 might
 want
 to
 take
 a
 look
 at
 the
 pdfapp.log
 file.
 You
 can
 
find
 the
 loca-ons
 for
 this
 file
 listed
 here
 for
 Windows
 and
 Mac.
 If
 you
 open
 this
 file
 in
 a
 text
 editor,
 you
 
can
 look
 through
 it
 fairly
 easily
 and
 you’ll
 likely
 be
 able
 to
 find
 an
 error
 code
 listed.
 

 
In
 the
 pdfapp.log
 file,
 look
 for
 “error”
 or
 “fatal”
 

 
If
 the
 Crea-ve
 Cloud
 Packager
 runs,
 but
 reports
 errors,
 you’ll
 want
 to
 take
 a
 look
 at
 the
 log
 file
 for
 the
 
Crea-ve
 Cloud
 Packager.
 
 Examining
 this
 file
 may
 give
 you
 insight
 into
 why
 the
 package
 would
 not
 
complete.
 

 
And,
 of
 course,
 if
 you
 need
 more
 help,
 your
 Solu-ons
 Consult
 can
 get
 you
 in
 touch
 with
 our
 Adobe
 
Support
 organiza-on
 to
 assist
 you
 directly.
 Our
 support
 technicians
 can
 examine
 the
 log
 file(s)
 and
 
provide
 a
 solu-on.
 

 

31
 

32