Adobe 65019371 Deployment Guide - Page 23

Choosing a Deployment Configuration Configuration IS - Product Install Folder on Server The path-related arguments to the Uber program are defined below: Argument -server=MediaLocation MediaLocation is assumed to be an explicit network path and the Uber program attempts to mount it. On Windows, MediaLocation must be a UNC path of not more than 250 characters, of the form \\servername\volume\pathname On the Mac, MediaLocation must be an AFP path of the form afp://servername/volume/pathname -user=Name Name is the name of a user on the system where the Uber program is being invoked, who has permission to mount the path given for the -server argument. -password=PWD PWD is the password for the user specified in the -user argument. Required/Optional Optional argument. If used, the Uber program ignores the InstallerLocation path in the package files. Use only with -server argument. On Windows, this argument is optional if the credentials of the user invoking the Uber program allow the mounting of the MediaLocation specified. If specified, and your network environment uses domain-based accounts, be sure to specify the user name in domain\username form. On the Mac, this argument is always required if the -server argument is given. This argument is required only if the -user argument is also given. The two go together; either specify both, or specify neither. Both are required on the Mac. Using an explicit network path is useful if you have different network configurations in different parts of your organization. In this case, you may have different paths to a server, or different servers, and you may not be able to determine the correct path from a given target until the time when the Uber program is invoked. In this case, you can write deployment scripts that determine the appropriate server for a given target and invoke the Uber program with the correct path as a command line argument. In this way, you can use the same Adobe package with multiple deployment scripts, each designed for a specific network configuration where the product install folder is mounted in a different place. See "Editing Package Files" starting on page 37 for how to put an explicit network path in the package files on Windows. At this point, you need to fill out a planning sheet #3 for each package you plan to create. Fill out as much of the information as you can now; if you have not yet actually downloaded the product ESD yet, you may have to wait to specify some of the paths until that is done. However, by the time you are ready to create the packages, all of this information should be filled out for the chosen configuration. Document Version 1.0 Sep 2009 23