Adobe 65019371 Deployment Guide - Page 22

Choosing a Deployment Configuration Configuration IS - Product Install Folder on Server Configuration IS - Product Install Folder on Server In this configuration, the package can be anywhere on the target (physically on the target or mounted from a server) and the product install folder is on one or more servers. This configuration enables a network install and may or may not require editing of the package files. USES This configuration is useful when you want the targets to access the product install folder on a server and perform a network install. It doesn't matter whether the package is copied to each target or is also mounted on the target. In either case, the package still executes on the target. This is a common configuration when using enterprise deployment software such as ARD to deploy an Adobe package. It may be a good choice if your target machines are widely distributed physically or geographically. NEEDS 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 servers 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. The package must be copied to or mounted on all target machines before it can be executed. The server hosting the product install folder may or may not be mounted before the package is executed, depending on the path form used (see below). If you are using an explicit network path, you must have a standard network configuration and all users deploying the package must have access to the server specified in that path. WARNING: The Delete Installer option in the package should be set to "false". PATH FORM With this configuration, you have two path form choices:  Absolute path - If you can mount the product install folder on all targets using the same path before the Uber program is invoked, you can use an absolute network path. In addition, if you can mount the product install folder using the same path when you create the package, you do not need to edit the package files before deploying them. When using an absolute path, you must mount the product install folder on all targets before executing the package. Explicit network path -If you cannot or do not want to mount the product install folder on all targets before they execute the Uber program, you can have the Uber program do the mount for you. In this case, you must use an explicit network path.  On the Mac, you must specify an AFP path. You pass this path, along with the user name and password of a user with mount privileges, as command line arguments when invoking the Uber program. The command line path overrides any path set in the package files.  On Windows, you must specify a UNC path. As on the Mac, you can pass the path to the Uber program as a command line argument, although the user name and password arguments are optional as long as the user who invokes the Uber program has the necessary permissions. The command line path overrides any path set in the package files. Alternatively, if the invoking user has the necessary permissions, you can put the UNC path in the package files instead of on the command line. When the Uber program sees a UNC path in the package file, it will attempt to mount it. Document Version 1.0 Sep 2009 22