Choosing a Deployment Configuration
Configuration TS — Together on Server
Document Version 1.0 Sep 2009
19
Configuration TS — Together on Server
In this configuration, the package and the product install folder are placed together on the same drive on
one or more servers. This configuration enables a network install and requires editing of the package files.
USES
This configuration is useful for situations in which you want all of your targets to access the package and
the product install on from the same server.
This is a good choice if your target machines are widely distributed physically or geographically, or if you
have some other reason for preferring a network install. This is the recommended configuration if you plan
to deploy the Adobe deployment package using SMS 2003 or SCCM 2007.
One advantage of this configuration is that it makes no reference to the server names, so you can use it
whether you have just one server or multiple servers that you use to host your product install folders.
NEEDS
Both the package and the entire product install folder must fit on a single drive on the server. 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 network bandwidth between the server and the target must be sufficient to allow an acceptable level
of performance for a network install.
Each target must have access to at least one server.
Each target must mount the server volume before the package can be executed.
WARNING:
The Delete Installer option in the package should be set to “false”.
PATH
FORM
Use a relative path from package to product install folder. You must be sure to copy the package and
product install folder into the proper relative locations on the server(s) so that the path will resolve
correctly when the package is deployed. See the relative path examples on
page 17
. For
recommendations when deploying with SMS or SCCM, refer to Chapter
4
.
Using a relative path requires you to edit the package files before copying the package to the server(s).
See
"Editing Package Files" starting on page 37
for details.
