Adobe Creative Suite 4 Deployment Manual

Tüüp
Deployment Manual
ADOBE® CREATIVE SUITE® 4
Document Version 1.0 Sep 2009
ENTERPRISE
DEPLOYMENT GUIDE
© 2009 Adobe Systems Incorporated and its licensors. All rights reserved.
Adobe® Creative Suite® 4 Enterprise Deployment Guide
This guide is licensed for use under the terms of the Creative Commons Attribution Non-Commercial 3.0 License. This
License allows users to copy, distribute, and transmit the guide for noncommercial purposes only so long as (1) proper
attribution to Adobe is given as the owner of the guide; and (2) any reuse or distribution of the guide contains a notice
that use of the guide is governed by these terms. The best way to provide notice is to include the following link. To view
a copy of this license, visit http://creativecommons.org/licenses/by-nc-sa/3.0/
Adobe, the Adobe logo, Adobe Connect, Adobe OnLocation, Adobe Premiere, Acrobat, After Effects, Contribute, Creative
Suite, Dreamweaver, Encore, Fireworks, Flash, Illustrator, InCopy, InDesign, Kuler, Photoshop, Pixel Bender, Soundbooth,
and Version Cue are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States
and/or other countries. Apple and Mac are trademarks of Apple Inc., registered in the United States and other countries.
Microsoft, Windows, and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the
United States and/or other countries. UNIX is a registered trademark of The Open Group in the US and other countries.
All other trademarks are the property of their respective owners.
Adobe Systems Incorporated, 345 Park Avenue, San Jose, California 95110, USA..
Document Version 1.0 Sep 2009 3
Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Enterprise Deployment Description & Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Advantages of Adobe Deployment Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Adobe Package Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
The Enterprise Deployment Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
CS4 Deployment Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
1 Planning for Deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Identifying User Groups & Their Needs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Making Your Package List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
How Products Correlate to Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Identifying the Package You Need . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Choosing a Deployment Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Configuration TT — Together on Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Configuration TM — Together on Storage Medium . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Configuration TS — Together on Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Configuration IT — Product Install Folder on Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Configuration IM — Product Install Folder on Physical Medium . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Configuration IS — Product Install Folder on Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Specifying Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Filling Out the Specification Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Choosing Shared Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Choosing Supporting Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2 Preparing for Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Preparing the Product Install Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Creating Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Using the Deployment Toolkit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Editing Package Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Testing Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3 Deploying Adobe® Packages with ARD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Execution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Installing Adobe CS4 software with a deployment package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Uninstalling Adobe CS4 software with a deployment package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Contents
Document Version 1.0 Sep 2009 4
4 Deploying Adobe® Packages with SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Creating an SMS Package with SMS 2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Create a New SMS Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Select Distribution Points for the SMS Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Create Programs for the SMS Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Advertise the SMS Package Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Creating an SMS Package with SCCM 2007 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Create a new SMS package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Create Programs for the SMS Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Select Distribution Points for the SMS Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Advertise the SMS Package Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
5 Post-Install Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Administrative Control Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Disabling Adobe Product Improvement Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Suppressing Application Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Suppressing Updates with the Install Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Suppressing Updates with System Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
On Windows® . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
On the Mac. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Document Version 1.0 Sep 2009 5
Introduction
This document is the central document in a set that provides you with the information you need to deploy
Adobe® Creative Suite® products in an enterprise environment. The following figure shows the entire
document set and how the documents are related.
Deployment and Provisioning Concepts — This document defines Adobe product and enterprise
deployment process terms used throughout the document set.
NOTE: You should read the Concepts document first, before attempting to use the other documents in
the set.
Enterprise Deployment Guide — This is the document you are reading. It identifies the main
characteristics of and assumptions about enterprise deployment and gives you the information you
need to deploy Adobe Creative Suite products using Adobe deployment packages. It explains how
you can use ARD and SMS to deploy Adobe deployment packages. It tells you how to set configuration
options after an install.
Enterprise Deployment Toolkit Guide — This document tells you how to use the Adobe deployment
toolkit to create deployment packages that enable you to easily do enterprise installs of Creative
Suite®4 products.
Enterprise Deployment Reference — This document contains detailed information about the
components that make up a Creative Suite product. Future versions may add information about the
structure and operation of Adobe packages, details of how the Adobe install program, Setup, works,
and guidance on how to do an enterprise install without an Adobe package.
Deployment and
Provisioning
Enterprise
Deployment Toolkit
Enterprise
Planning Sheets
1
2
3
FAQ
Introduction/Process/Concepts
Tuning Deployment
Preparation
Deployment
Guide
Concepts
Enterprise
Deployment
Guide
Reference
Enterprise
Deployment
YOU ARE HERE
Enterprise Deployment Description & Assumptions
Document Version 1.0 Sep 2009 6
Enterprise Deployment Planning Sheets — A collection of planning worksheets you can use to plan,
record, and communicate your deployment decisions.
Enterprise Deployment Description & Assumptions
While enterprise situations vary widely in the number of machines involved, how those machine are
connected and configured, how they are managed and accessed, and what their deployment framework
is, there are some fundamental characteristics they have in common. The information in this document set
assumes the following common characteristics:
1. User Groups — A given customer has more than one group of users. Each group uses a different set of
software applications to accomplish their jobs. Someone in the company determines which users
belong to which groups, and what applications each group needs.
2. Software Purchases — Someone in the company decides which products to buy to optimize product
coverage across all groups and minimize cost to the company. Adobe Creative Suite products come in
two forms: point products and suite products. This person decides which type of product to buy and
how many seats of each are needed. All products are purchased with a volume license. Volume
licenses for Adobe products are available directly from Adobe or from a reseller; serial numbers are
downloaded from the Adobe licensing web site.
3. Communication — The people who identify the user groups and make the software purchasing
decisions convey this information to the system administrators who install the software.
4. System Administrator Responsibilities — An administrator’s job is to take the install media for software
purchased by the company and put the correct set of applications on each user’s machine. In order to
do this, he must have the serial number for each product.
In order for the administrator to do his job, he must know what user groups have been identified,
which computers belong to each group, who is in each group, which set of applications each user
group needs, and how many copies of which products the company has purchased. Based on this, he
decides which serial number to use when installing an application for a user group.
5. Media Type — CS4 products come in two forms: product media (DVDs) and product ESDs (electronic
software distribution). Product ESDs are the preferred form for use in enterprise deployments.
6. Configuration — In almost all cases, a network is needed to perform part or all of the deployment.
Advantages of Adobe Deployment Packages
Using deployment packages created with the Adobe CS4 deployment toolkit to install CS4 products gives
you a number of advantages:
1. Deployment packages enable enterprise installs — An enterprise install is a silent, customized install.
A silent install requires no input from end users on the systems on which it is executed. This means
that all choices affecting what is installed and how it is installed are made before the install is
performed. These choices are stored in the package.
When creating a deployment package, you choose the applications and components you wish to
install from the product you are packaging. When packaging products on Windows® that include
Adobe® Photoshop®, you can also include the 64–bit version of Photoshop® and some related
components that can be installed on 64–bit machines.
Adobe Package Limitations
Document Version 1.0 Sep 2009 7
You can also easily choose install options that may not be available when you use the Adobe install
program directly, or that would be available in silent install mode only with hand editing and placing
configuration files on the systems where the install program runs. For example, you can choose
package options that affect the behavior of the install program and the package program when they
run. You can direct the install program to ignore conflicting processes. You can direct the package
program to remove the product install folder from the system after a successful install, recovering disk
space on the target machines as part of the package action. You can also choose options that affect
the behavior of the installed applications, such as suppressing the display of the EULA, registration
prompts, and automatic updating activity.
2. Package creation is easy with the CS4 deployment toolkit — The toolkit has an easy-to-use GUI that
makes it simple to create a deployment package that can both install and uninstall the applications
you specify. It offers great advantages over assembling a package manually by using Setup in record
mode and preparing and creating a number of XML files by hand.
3. Your product serial number is verified before installation — The toolkit prompts you for the serial
number of your product, and verifies that the number you enter is a valid volume licensing serial
number. If it is not, the toolkit indicates that there is a problem and allows you to enter a different
number. You cannot proceed with package creation until you provide a valid number. So you are
assured that the install that takes place when this package is executed will not fail because of serial
number problems, and that the install program will never prompt the end user on a target system to
supply a serial number during the install.
4. The system requirements for the CS4 deployment toolkit are modest — While the Adobe install program,
Setup, can be run in a mode which just records the applications you choose without actually installing
them, it requires the system on which it runs to meet the system requirements of the applications you
choose to include in this process. The toolkit does not impose this restriction; therefore, it can be run
on systems with more modest capacities.
5. There is a table in the Enterprise Deployment Toolkit Guide which lists the system requirements
necessary to run the CS4 deployment toolkit.
NOTE: The deployment toolkit does not perform an install; it just creates a deployment package that
records the install decisions you make ahead of time. The actual install is performed by the Adobe install
program, Setup, located in the product install folder associated with the package. Setup is invoked by a
program in the package that uses the configuration information in the package to create necessary
configuration files for Setup and invokes Setup with appropriate command line arguments to ensure a
silent install.
Adobe Package Limitations
There are a few things that Adobe deployment packages cannot do:
They do not support snapshot installations.
They cannot be used to deploy system or application configuration information other than what is
explicitly described in this document. In particular, you cannot use one to deploy application–specific
preference settings. The CS4 applications do not implement application preferences in a consistent
manner across applications, nor do the implementations conform to existing platform standards.
The Enterprise Deployment Process
Document Version 1.0 Sep 2009 8
The Enterprise Deployment Process
The following figure shows a simplified view of the process for deploying Adobe Creative Suite 4 software,
using Adobe deployment packages:
1. Planning — There are decisions to make before you create deployment packages and distribute them.
The planning sheets, along with the information in this document and in the Enterprise Deployment
Toolkit Guide, will help you get everything ready to go. The planning step affects all the other steps.
2. Downloading the product ESD — The specific manner in which this occurs differs on Mac and
Windows®, but the net affect is the same; when you are done, you have a product install folder on your
admin system or staging area that contains the product install program and everything it needs to
install the product. You decide where to put this folder during the planning process.
3. Creating deployment packages — Once the product install folder is on or available from your admin
system, you can create the Adobe deployment package or packages necessary to install that product.
The Enterprise Deployment Toolkit Guide contains detailed instructions on how to create deployment
packages.
4. Testing the packages — Once the packages are created, you should test them on a test system to make
sure everything executes without error. This test setup should mirror the one you use to deploy the
packages to your target systems. This document contains the necessary information to do this step.
5. Deploying the packages — You can use a third party tool such as ARD or SMS (SCCM) to deploy your
packages if you so choose; Adobe has tested these tools with Adobe deployment packages. Other
such tools may also be reasonably expected to work, although Adobe has not tested them.
WARNING for Windows: The packages created by the CS4 Deployment Toolkit silently use the Adobe
installer subsystem, which in turn uses the native Windows installer, MSI. Therefore, you cannot wrap
an Adobe install package inside of a Windows package for use with MSI because Windows prohibits
such a recursive use of MSI.
Chapter 1 in this document covers step 1.
Chapter 2 in this document covers steps 2,3, and 4.
You will also need the Enterprise Deployment Toolkit Guide for step 3.
Chapters 3, 4, and 5 cover step 5.
Product
Install
Product
Deployment
2
Admin System
Target Systems
ESD
Pkg
Test System
1
Deployment
Pkg
Deployment
Pkg
Deployment
Pkg
4
5
Folder
3
Worksheets
CS4 Deployment Packages
Document Version 1.0 Sep 2009 9
CS4 Deployment Packages
An Adobe CS4 deployment package is an encapsulation of an invocation of a CS4 product install program
which could be done by hand in a laborious and error–prone process. It provides an automated way of
invoking a CS4 install program to perform an enterprise install – a silent, customized install. Each package
can install just one CS4 product.
You create packages with the CS4 deployment toolkit. When creating a package, one of the first things you
do is point the toolkit at the product install folder for the product you are packaging. The toolkit scans this
folder and presents you with a list of applications and components that can be installed, from which you
make your choices. You can also set a number of options that affect the behavior of the install program
and of the installed applications. All of these choices are recorded in the package.
When you save a newly created package, what you have is a folder containing four things:
Two executable programs — AdobeUberInstaller and AdobeUberUninstaller;
Two configuration files — AdobeUberInstaller.xml and AdobeUberUninstaller.xml.
The executables do what their names suggest: they install and uninstall a particular Adobe product. The
executables are called the Uber programs; the XML files are called the package files. When you execute a
package, you invoke one of the Uber programs. The Uber program in turn invoke the Adobe install
program, Setup.
Deployment packages are always executed on the target systems. “Executing a package” means invoking
one of the Uber programs. When the AdobeUberInstaller program is invoked:
It uses the information in the AdobeUberInstaller.xml file to construct files that Setup uses when it
runs;
It adds or modifies system configuration files that Setup uses when it runs;
It invokes Setup with appropriate command line arguments so that the install happens as you
configured it in your package.
When Setup completes, AdobeUberInstaller cleans up after it, removes the product install folder from
the target systems if so specified in the package, and terminates.
Document Version 1.0 Sep 2009 10
1
Planning for Deployment
Before you use the Adobe® Creative Suite®4 enterprise deployment toolkit to make packages, you need to
do a good deal of thinking and planning. This section gives you all the information you need to to that
planning. The Enterprise Deployment Toolkit Guide helps you through the process of creating packages with
the toolkit. You then come back to this document to do the final step of deployment — getting the
packages you have created, and their associated product install folders, into the right places so the target
systems can invoke the package and install the product.
There are several steps to your planning process:
1. Identifying your user groups and their application needs.
2. Identifying the packages you need to create to install those applications for those users.
3. Deciding how you will deploy the packages. There are six basic deployment configurations from
which you can choose.
4. Specifying the packages themselves before you create them.
Steps 3 and 4 are somewhat interrelated; you may find yourself doing them in tandem.
The four sections in this chapter each address one of these planning steps.
Identifying User Groups & Their Needs
You will need one or more deployment packages for every unique user group in your enterprise. Your first
planning step is to identify each user group that needs a particular application or set of applications to do
their job. If you or someone else at your company has already purchased the Creative Suite®4 products,
this step has undoubtedly already been done, but it may or may not be written down in a form useful to
you at this stage in planning.
Use Enterprise Deployment Planning Sheet #1: User Groups & Packages for CS4 Products for this step. You will
continue to use this planning sheet in the second planning step.
NOTE: Use a pencil to fill in this planning sheet, as some iterative planning will be taking place on it, and
you may need to erase some things.
At this point, you want to fill out the first four columns:
GROUP NAME: Identify each user group for which you have purchased (or will purchase) CS4 software.
The labels you choose to identify your user groups are for your own use only; they are not included
anywhere in the deployment package, so there are no restrictions on how you name them.
PRIMARY APPLICATIONS NEEDED: For each user group, write down the list of CS4 applications people in that
group need to do their jobs. The primary applications are listed in the first column of the
application/suite matrix on
page 11 .
PLATFORMS: Circle, underline, or otherwise highlight the platform(s) the users in the group work on.
PRODUCT: List here the CS4 product(s) that have been purchased (or will be purchased) that provide the
applications you have listed. This list will consist of point product and/or suite product names. Do not
Identifying User Groups & Their Needs
Document Version 1.0 Sep 2009 11
distinguish between Mac and Windows® versions when you list the product names here. You will do
that in a later step.
An example planning sheet is shown below.
You may find the following table useful in filling out these four columns. It shows the six CS4 suite
products along the top, with the CS4 point products down the left side. Dots in the body of the table show
which point product primary applications are included in which suite. If a user group needs every
application in a particular suite, you can just write “All of <suite-name>” in the APPLICATIONS NEEDED
column on the planning sheet.
NOTE: The display name for Photoshop in the toolkit is always just “Photoshop”. It is understood that the
extended version of Photoshop exists in all versions of Creative Suite except for Design Standard CS4.
PLANNING SHEET #1: USER GROUPS & PACKAGES FOR CS4 PRODUCTS
GROUP NAME PRIMARY APPLICATIONS NEEDED PLATFORMS PRODUCT(S)
PACKAGE
COUNT
PACKAGE NAME
(S)
Writers Adobe InDesign, Adobe InCopy Mac Win Design Premium
InCopy
Photographers Adobe Photoshop Mac Win Design Premium
Layout Folks Photoshop, Adobe Illustrator,
InDesign
Mac Win Design Premium
Web Makers Adobe Dreamweaver, Adobe Flash,
Adobe Fireworks
Mac Win Design Premium
Design
Standard
CS4
Design
Premium
CS4
Web
Standard
CS4
Web
Premium
CS4
Master
Collection
CS4
Production
Premium
CS4
Acrobat® 9 Pro
 
Adobe® After Effects® CS4

Adobe® Contribute® CS4

Adobe® Dreamweaver® CS4

Adobe® Encore® CS4

Adobe® Fireworks® CS4

Adobe® Flash® Professional
CS4

Adobe® Illustrator® CS4
 
Adobe® InCopy® CS4
Adobe® InDesign® CS4

Adobe® OnLocation® CS4

Adobe® Photoshop® CS4
Photoshop Extended CS4

Adobe® Premiere® Pro CS4

Adobe® Soundbooth® CS4

Making Your Package List How Products Correlate to Packages
Document Version 1.0 Sep 2009 12
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
Making Your Package List Identifying the Package You Need
Document Version 1.0 Sep 2009 13
its corresponding applications from the original row to a new one. Then erase that product name
and those applications from the original row.
For each new row you add, enter the same user group name and the same platform choices from
the original row.
At this point, our example worksheet would look like this:
2. Calculate your package count.
For each row on your planning sheet, look in the
PLATFORMS column. If you have chosen only one
platform (double underlined in example above), your package count is 1. If you have chosen both
platforms, your package count is 2. Record these numbers in the
PACKAGE COUNT column.
3. Name each package.
You are now ready to name your packages. Choose a brief but descriptive name for each package on
your list. If you have Mac and Windows versions of the same package, you may want to choose a
common package name and append “Win” or “Mac” to the name. Whatever name you choose, it
should allow you to easily identify that package with its intended user group and usage.
NOTE: Since this package name is used to name the folder on your system that will contain the
package files, the same operating system constraints that apply to folder names also apply to the
package names you choose.
At this point, our example worksheet would look like this:
PLANNING SHEET #1: USER GROUPS & PACKAGES FOR CS4 PRODUCTS
GROUP NAME PRIMARY APPLICATIONS NEEDED PLATFORMS PRODUCT(S)
PACKAGE
COUNT
PACKAGE NAME
(S)
Writers InDesign Mac Win Design Premium
Photographers Photoshop Mac Win Design Premium
Layout Folks Photoshop, Illustrator, InDesign Mac Win Design Premium
Web Makers Dreamweaver, Flash, Fireworks Mac Win Design Premium
Writers InCopy Mac Win InCopy
PLANNING SHEET #1: USER GROUPS & PACKAGES FOR CS4 PRODUCTS
GROUP NAME PRIMARY APPLICATIONS NEEDED PLATFORMS PRODUCT(S)
PACKAGE
COUNT
PACKAGE NAME
(S)
Writers InDesign Mac Win Design Premium 1 InDesignOnly
Photographers Photoshop Mac Win Design Premium 2 PhotoMac
PhotoWin
Layout Folks Photoshop, Illustrator, InDesign Mac Win Design Premium 1 Layout
Web Makers Dreamweaver, Flash, Fireworks Mac Win Design Premium 2 WebMac
WebWin
Writers InCopy Mac Win InCopy 1 InCopyOnly
Choosing a Deployment Configuration Identifying the Package You Need
Document Version 1.0 Sep 2009 14
Choosing a Deployment Configuration
As has already been explained, a deployment package is always associated with one product, and
therefore with one product install folder. The connection between the package and the product install
folder is set during package creation, when the toolkit asks for you for a Media Files Location. Because the
toolkit forces you to browse for this location, the resulting path is always an absolute path and can point
either to a file on the local system or on a mounted drive.
When you save the package, this path is preserved in the package’s two package files as the value of the
InstallerLocation element. The screen shot below shows the toolkit running on a Windows system,
and shows where the Media Files Location you specify in the toolkit is saved in the package files.
If you deploy the package as created, the Uber programs use this path to locate the product install folder
during deployment. Given your enterprise system configuration and the way in which you plan to deploy
the package, this path may not be optimal or even possible. If the original path won’t do for your situation,
you can provide a different path either by editing the path in the package files before deployment or by
providing a path as a command line argument to the Uber program when you invoke it.
In order to determine what your deployment path needs to be, you must identify your deployment
configuration — the physical and logical relationship between the package and the product install folder
at the time the package is executed.
At this point, it might be useful to look at Enterprise Deployment Planning Sheet #3 : CS4 Deployment
Configurations while you read the rest of this section, as the planning sheet summarizes the configuration
descriptions which follow. When you are finished reading about the configuration options, you should fill
out a planning sheet #3 for each package you are going to deploy.
In order to determine which configuration option best meets your needs, you need to answer several
questions:
<?xml version=’1.0’ encoding=’utf-8’?>
<!-- Generated by Adobe CS4 Deployment Toolkit. Place this xml
along with AdobeUberInstaller utility and then execute the
silent installation by invoking AdobeUberInstaller.exe (Win)
or AdobeUberInstaller (Mac) -->
<InstallInfo>
<PackageDescription>
Layout:Photoshop,Illustrator,and InDesign for the
layout folks
</PackageDescription>
<InstallerLocation>
C:\CS4 Master Collection Media\Adobe CS4
</InstallerLocation>
<TargetOS> Windows </TargetOS>
<DeploymentInfo processorFamily="All"
deleteInstallationImage="false"
ignoreProcesses="false">
Choosing a Deployment Configuration Identifying the Package You Need
Document Version 1.0 Sep 2009 15
1. Will you distribute and place the package and the product install folder together or independently?
By together, we mean that the package and product install folder are on the same disk drive or volume
on a computer, or on the same portable disk medium, such as a DVD, flash drive, or movable disk.
An answer of “together” leads to three very similar configuration choices (TT, TM, and TS in the
following figure).
An answer of “independently” leads to a second question.
2. Will you physically place the product install folder on each target or on one or more servers?
Your choice is influenced by the disk capacity of the target machines to which you will deploy the
package as well as by your network bandwidth.
An answer of “on the targets” leads to two similar configurations (IT and IM in the following figure).
An answer of “on servers” leads to a sixth configuration (IS in the following figure).
These six basic deployment configurations are shown below. In this picture the term “package” is
abbreviated to ‘Pkg” and the term “product install folder” is abbreviated to “PIF”.
As already explained, the path from a newly created package to its product install folder is always an
absolute path. Some of the above configurations either preclude the use of an absolute path or make
some other path type more desirable. For configurations TT, TM, and TS, the only sensible choice is a
relative path from the package to the product install folder. Configurations IT, IM, and IS require an
absolute path. Certain instances of configuration IS may require an explicit network path.
These path forms are defined in Table
1. Table 2 lists the valid path form(s) for each deployment
configuration. The rest of this section contains a detailed description of each configuration.
How are the Package & Product Install Folder Placed?
TOGETHER INDEPENDENTLY
Where is the Product Install Folder?
ON TARGET ON SERVER
on same drive
Pkg & PIF
Pkg & PIF
on PORTABLE
TT TM
IM
on TARGET
on same drive
Pkg & PIF
TS
on SERVER
Pkg anywhere
PIF on PORTABLE
STORAGE MEDIUM
Pkg anywhere
PIF on SERVER
IS
STORAGE MEDIUM
IT
Pkg anywhere
PIF on TARGET
on different drive
Choosing a Deployment Configuration Identifying the Package You Need
Document Version 1.0 Sep 2009 16
Table 1: Path Forms for the Package–to–Product Install Folder Link
Relative Path
Relative paths are used to locate the product install folder relative to the location of the package that references it, i.e.
relative to the current working directory of the Uber program when it runs. Relative paths are recommended in cases
where the package and the product install folder are located together on the same drive or volume on a system or on the
same movable storage medium.
A relative path on Windows contains a path component that does not begin with either a slash or backslash ( / or \).
A relative path on the Mac is any path that does not start with a slash( / ).
..\Mystery Files\Follow Me
Mystery Files/Follow Me
Absolute Path
Absolute paths are used to locate the product install folder relative to the target machine, independent of where the
package is located. An absolute path can resolve to either a local directory or a network location.
You cannot determine for certain whether an absolute path is a local path or a network path just by looking at it,
although you can in some instances make an educated guess. For example, on the Mac, network mounts are often made
under the /Volumes folder. On Windows, network mounts are often done on drive letters near the end of the alphabet.
An absolute path on Windows begins with a drive letter and colon followed by a slash or backslash ( / or \ ).
For example:
H:\CS4_Apps\PIFs\WebPremium
An absolute path on the Mac begins with a single slash ( / ). For example:
/CS4_Apps/PIFs/WebPremium
Explicit Network Path
An explicit network path denotes a specific server, a mountable volume on that server, and optionally a path on that
volume. Explicit network paths are useful when the product install folder is remote to the target, especially when it
cannot be mounted on the target before deployment.
Explicit network paths are easily recognizable. On Windows, you must use UNC (Universal Naming Convention) paths,
which begin with two backslashes ( \\ ) or two quoted slashes ( “//” ) and whose first path element is the name of a server.
For example:
\\fileserver.company.com\transfer\CS4-Apps\PIFs\WebPremium
On Mac, you must use AFP (Apple Filing Protocol) paths of the form afp://server-name/volume-name/path.
For example:
afp://fileserver.company.com/transfer/CS4-Apps/PIFs/WebPremium
Table 2: Path Forms Required for Deployment Configurations
Config Package Product Install Folder Path Type
TT Together on same drive on TARGET Relative
TM Together on PHYSICAL MEDIUM mounted on target Relative
TS Together on same drive on SERVER Relative
IT ANYWHERE On different drive on TARGET Absolute local
IM ANYWHERE On PHYSICAL MEDIUM mounted on target Absolute local
IS ANYWHERE On SERVER, mounted on target before deployment
On SERVER, mounted on target during deployment
Absolute network
Explicit Network
Choosing a Deployment Configuration Configuration TT — Together on Target
Document Version 1.0 Sep 2009 17
Configuration TT — Together on Target
In this configuration, the package and the product install folder are placed together on the same drive on
all targets. This configuration enables a local install and requires editing of the package files.
USES This configuration is useful if you want to avoid a network install, your targets have enough disk space to
hold the product install folder, and you have a logistically feasible way of copying the product install folder
to all of the target machines.
NEEDS Both the package and the entire product install folder must fit on a single drive on the target. 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 Delete Installer option in the package can be set to “true”, so that the product install folder is
automatically removed after the install has successfully completed. However, if the install fails for any
reason, the product install folder is not removed, even if this option is set to “true”.
PATH
FORM
Use a relative path from package to product install folder.
The package and product install folder must be placed on the same drive. Be sure to place them in the
proper relative locations so that the path will resolve correctly when the package is deployed. Examples of
a few obvious choices are given below. The first two examples assume a product install folder named
PIF.
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.
Relationship of Adobe Deployment Package and
Product Install Folder
Value of InstallerLocation
Element in Package Files
Package folder and product install folder are in same parent folder
(common choice when deploying with ARD)
../PIF
Package folder is inside the product install folder
(recommended choice when deploying with SMS/SCCM)
../
Package folder contents are placed in the product install folder
./
You have a CS4_Deploy folder containing:
== a
Packages folder and a PIFS folder
== One or more packages in the
Packages folder
== One or more product install images in the
PIFS folder, named by
product
../../PIFS/WebPremium
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.
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.
Choosing a Deployment Configuration Configuration IT — Product Install Folder on Target
Document Version 1.0 Sep 2009 20
Configuration IT — Product Install Folder on Target
In this configuration, the package and the product install folder are both on the target, but may be on
different drives. This configuration enables a local install, and may or may not require editing of the
package files.
USES This configuration is useful if you want to avoid a network install, your targets have enough disk space to
hold the product install folder, you have a logistically feasible way of copying the product install folder to
all of the target machines, and you don’t want to have to edit the package files.
This configuration differs from configuration TT in only one respect: the package and the product install
folder may not be on the same drive, so an absolute path between the two is required. Chances are the
toolkit is not on the same drive as the product install folder during package creation, so saving the path as
an absolute one is a logical thing to do. You can avoid having to edit this absolute path after package
creation if you can place the product install folder on the same drive/path both when creating the package
on an admin machine and deploying it on the targets.
This is a common configuration for those who use ARD to deploy the package.
NEEDS The entire product install folder must fit on a single drive on the target. For some point products, the
product install folder may be relatively small; for the suite products, especially the Master Collection, it is
quite large.
You must guarantee that the absolute path specified in the package can be duplicated and is adequate to
house the product install folder on every target system.
The Delete Installer option in the package can be set to “true”, so that the product install folder is
automatically removed after the install has successfully completed. However, if the install fails for any
reason, the product install folder is not removed, even if this option is set to “true”.
PATH
FORM
Use an absolute local path from package to product install folder. If you can place the product install folder
in a drive with the same drive letter, or on the desktop, both on the system where you create the package
and on all targets when deploying it, you do not need to edit the package files.
  • Page 1 1
  • Page 2 2
  • Page 3 3
  • Page 4 4
  • Page 5 5
  • Page 6 6
  • Page 7 7
  • Page 8 8
  • Page 9 9
  • Page 10 10
  • Page 11 11
  • Page 12 12
  • Page 13 13
  • Page 14 14
  • Page 15 15
  • Page 16 16
  • Page 17 17
  • Page 18 18
  • Page 19 19
  • Page 20 20
  • Page 21 21
  • Page 22 22
  • Page 23 23
  • Page 24 24
  • Page 25 25
  • Page 26 26
  • Page 27 27
  • Page 28 28
  • Page 29 29
  • Page 30 30
  • Page 31 31
  • Page 32 32
  • Page 33 33
  • Page 34 34
  • Page 35 35
  • Page 36 36
  • Page 37 37
  • Page 38 38
  • Page 39 39
  • Page 40 40
  • Page 41 41
  • Page 42 42
  • Page 43 43
  • Page 44 44
  • Page 45 45
  • Page 46 46
  • Page 47 47
  • Page 48 48
  • Page 49 49
  • Page 50 50
  • Page 51 51
  • Page 52 52
  • Page 53 53
  • Page 54 54
  • Page 55 55
  • Page 56 56
  • Page 57 57

Adobe Creative Suite 4 Deployment Manual

Tüüp
Deployment Manual

teistes keeltes