Adobe 65019371 Deployment Guide - Page 20

Configuration IT — Product Install Folder on Target, NEEDS

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 20 highlights

Choosing a Deployment Configuration Configuration IT - Product Install Folder on Target Configuration IT - Product Install Folder on Target In this configuration, the package and the product install folder are both on the target, but may be on different drives. This configuration enables a local install, and may or may not require 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, you have a logistically feasible way of copying the product install folder to all of the target machines, and you don't want to have to edit the package files. This configuration differs from configuration TT in only one respect: the package and the product install folder may not be on the same drive, so an absolute path between the two is required. Chances are the toolkit is not on the same drive as the product install folder during package creation, so saving the path as an absolute one is a logical thing to do. You can avoid having to edit this absolute path after package creation if you can place the product install folder on the same drive/path both when creating the package on an admin machine and deploying it on the targets. This is a common configuration for those who use ARD to deploy the package. NEEDS 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. You must guarantee that the absolute path specified in the package can be duplicated and is adequate to house the product install folder on every target system. 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 an absolute local path from package to product install folder. If you can place the product install folder in a drive with the same drive letter, or on the desktop, both on the system where you create the package and on all targets when deploying it, you do not need to edit the package files. Document Version 1.0 Sep 2009 20

  • 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 IT — Product Install Folder on Target
Document Version 1.0
Sep 2009
20
Configuration IT — Product Install Folder on Target
In this configuration, the package and the product install folder are both on the target, but may be on
different drives. This configuration enables a local install, and may or may not require 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, you have a logistically feasible way of copying the product install folder to
all of the target machines, and you don’t want to have to edit the package files.
This configuration differs from configuration TT in only one respect: the package and the product install
folder may not be on the same drive, so an absolute path between the two is required. Chances are the
toolkit is not on the same drive as the product install folder during package creation, so saving the path as
an absolute one is a logical thing to do. You can avoid having to edit this absolute path after package
creation if you can place the product install folder on the same drive/path both when creating the package
on an admin machine and deploying it on the targets.
This is a common configuration for those who use ARD to deploy the package.
NEEDS
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.
You must guarantee that the absolute path specified in the package can be duplicated and is adequate to
house the product install folder on every target system.
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 an absolute local path from package to product install folder. If you can place the product install folder
in a drive with the same drive letter, or on the desktop, both on the system where you create the package
and on all targets when deploying it, you do not need to edit the package files.