Adobe 65019371 Deployment Guide - Page 12

Making Your Package List How Products Correlate to Packages Making Your Package List After you have a complete list of user groups and the applications each one needs to do their jobs, you are ready to determine how many packages you need to deploy those applications for those users. In order to determine your package count and what each one should contain, you need to understand a few concepts about Adobe product and package design. How Products Correlate to Packages In order to determine how many deployment packages you need to create, and what each package deploys, you need to understand the relationship between a CS4 product and a package. When you purchase a CS4 product, you get the product either on DVDs (product media) or via an electronic download (product ESD). The product ESD is highly recommended for enterprise deployment. However, the Enterprise Deployment Toolkit Guide does contain instructions for those who use product media instead. There is a one-to-one correspondence between a deployment package and a CS4 product. A package is designed to package a single product install folder, which includes the install program, Setup, and all the application and component code, configuration information, and all the other information it needs to install the product. Additionally, each product comes with a single serial number; as an install program can take only one serial number, a package can deploy only a single product. As a result of this one-to-one relationship, a deployment package has a link to one and only one product install folder. You cannot create a single package that includes multiple CS4 products. For example, you can buy Photoshop CS4 and Illustrator CS4 separately as point products, but you cannot create one deployment package to install both of them; you must create one package to install Photoshop and a different package to install Illustrator. If you purchase InCopy CS4, you must make a package to install just InCopy. In fact, this is the only way to package InCopy CS4 because it is not included in any of the suite products. A package can install multiple applications only if all of those applications are installed from a suite product. So, you can install both Photoshop and Illustrator from a single package only if you have purchased a suite product that contains both of those applications. You can create multiple deployment packages from a single CS4 product. For a suite product, different packages can deploy different subsets of the applications included in the suite. You can even create multiple packages that deploy the same single application, with different install options and application options. However, all of the packages created from a given product are all deployed using the same serial number and the same product install folder. Identifying the Package You Need Now that you have a user group/applications list and understand the restrictions on a given package, you are ready to identify all the packages you need to create. Continue working on planning sheet #1 that you started in the previous section. 1. For every row that specifies multiple products, add more rows so that each resulting row specifies only one product.  For each row that lists more than one product in the PRODUCT(S) column, you need to make one or more extra rows for that groups. If there are two products listed, you need one extra row; if there are three products listed, you need two extra rows, etc. To split up your single row most efficiently, identify the product with the smallest subset of applications (for instance, a point product, or a suite product with only one or two applications from it) and move that product and Document Version 1.0 Sep 2009 12