Adobe 65019371 Deployment Guide - Page 17

Configuration TT — Together on Target, Relationship of Adobe Deployment Package

Get Adobe 65019371 PDF manuals and user guides View all Adobe 65019371 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 17 highlights

Choosing a Deployment Configuration Configuration TT - Together on Target Configuration TT - Together on Target In this configuration, the package and the product install folder are placed together on the same drive on all targets. This configuration enables a local install and requires editing of the package files. USES This configuration is useful if you want to avoid a network install, your targets have enough disk space to hold the product install folder, and you have a logistically feasible way of copying the product install folder to all of the target machines. NEEDS Both the package and the entire product install folder must fit on a single drive on the target. For some point products, the product install folder may be relatively small; for the suite products, especially the Master Collection, it is quite large. The Delete Installer option in the package can be set to "true", so that the product install folder is automatically removed after the install has successfully completed. However, if the install fails for any reason, the product install folder is not removed, even if this option is set to "true". PATH FORM Use a relative path from package to product install folder. The package and product install folder must be placed on the same drive. Be sure to place them in the proper relative locations so that the path will resolve correctly when the package is deployed. Examples of a few obvious choices are given below. The first two examples assume a product install folder named PIF. Relationship of Adobe Deployment Package and Product Install Folder Package folder and product install folder are in same parent folder (common choice when deploying with ARD) Package folder is inside the product install folder (recommended choice when deploying with SMS/SCCM) Package folder contents are placed in the product install folder You have a CS4_Deploy folder containing: == a Packages folder and a PIFS folder == One or more packages in the Packages folder == One or more product install images in the PIFS folder, named by product Value of InstallerLocation Element in Package Files ../PIF ../ ./ ../../PIFS/WebPremium Using a relative path requires you to edit the package files before copying the package to the target machines. See "Editing Package Files" starting on page 37 for details. Document Version 1.0 Sep 2009 17

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
Choosing a Deployment Configuration
Configuration TT — Together on Target
Document Version 1.0
Sep 2009
17
Configuration TT — Together on Target
In this configuration, the package and the product install folder are placed together on the same drive on
all targets. This configuration enables a local install and requires editing of the package files.
USES
This configuration is useful if you want to avoid a network install, your targets have enough disk space to
hold the product install folder, and you have a logistically feasible way of copying the product install folder
to all of the target machines.
NEEDS
Both the package and the entire product install folder must fit on a single drive on the target. For some
point products, the product install folder may be relatively small; for the suite products, especially the
Master Collection, it is quite large.
The Delete Installer option in the package can be set to “true”, so that the product install folder is
automatically removed after the install has successfully completed. However, if the install fails for any
reason, the product install folder is not removed, even if this option is set to “true”.
PATH
FORM
Use a relative path from package to product install folder.
The package and product install folder must be placed on the same drive. Be sure to place them in the
proper relative locations so that the path will resolve correctly when the package is deployed. Examples of
a few obvious choices are given below. The first two examples assume a product install folder named
PIF
.
Using a relative path requires you to edit the package files before copying the package to the target
machines. See
"Editing Package Files" starting on page 37
for details.
Relationship of Adobe Deployment Package and
Product Install Folder
Value of InstallerLocation
Element in Package Files
Package folder and product install folder are in same parent folder
(common choice when deploying with ARD)
../PIF
Package folder is inside the product install folder
(recommended choice when deploying with SMS/SCCM)
../
Package folder contents are placed in the product install folder
./
You have a
CS4_Deploy
folder containing:
== a
Packages
folder and a
PIFS
folder
== One or more packages in the
Packages
folder
== One or more product install images in the
PIFS
folder, named by
product
../../PIFS/WebPremium