Adobe 65021566 Deployment Guide - Page 18

Configuration TM — Together on Storage Medium, NEEDS, WARNING

Page 18 highlights

Choosing a Deployment Configuration Configuration TM - Together on Storage Medium Configuration TM - Together on Storage Medium In this configuration, the package and the product install folder are placed together on the same movable storage medium, such as a disk, flash drive, or DVD. This configuration enables a local install and requires editing of the package files. USES This configuration is, in effect, a special form of configuration TT, the difference being that the package and product install folder are put on the target not by copying onto a system disk but by physically mounting a transportable storage medium on the system. This choice is a good one if you have a relatively small number of target systems or if some of your targets are not geographically local. The storage medium can be passed from one target to another. Any user with administrative privileges can mount the storage medium on the target and invoke the Uber program with no input or configuration necessary. NEEDS Both the package and the entire product install folder must fit on a single medium. 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 storage medium must be mounted on each target system before the package can be executed. WARNING: The Delete Installer option in the package should be set to "false". Because it is mounted as a peripheral, the product install folder is local and the install program will attempt to remove it if the installation is successful and this option is turned on. PATH FORM Use a relative path from package to product install folder. Be sure to place them in the proper relative locations on the storage medium so that the path will resolve correctly when the package is deployed. See the relative path examples on page 17 . 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 18

  • 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 TM — Together on Storage Medium
Document Version 1.0
Sep 2009
18
Configuration TM — Together on Storage Medium
In this configuration, the package and the product install folder are placed together on the same movable
storage medium, such as a disk, flash drive, or DVD. This configuration enables a local install and requires
editing of the package files.
USES
This configuration is, in effect, a special form of configuration TT, the difference being that the package
and product install folder are put on the target not by copying onto a system disk but by physically
mounting a transportable storage medium on the system.
This choice is a good one if you have a relatively small number of target systems or if some of your targets
are not geographically local. The storage medium can be passed from one target to another. Any user with
administrative privileges can mount the storage medium on the target and invoke the Uber program with
no input or configuration necessary.
NEEDS
Both the package and the entire product install folder must fit on a single medium. 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 storage medium must be mounted on each target system before the package can be executed.
WARNING:
The Delete Installer option in the package should be set to “false”. Because it is mounted as a
peripheral, the product install folder is local and the install program will attempt to remove it if the
installation is successful and this option is turned on.
PATH
FORM
Use a relative path from package to product install folder. Be sure to place them in the proper relative
locations on the storage medium so that the path will resolve correctly when the package is deployed. See
the relative path examples on
page 17
.
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.