Adobe 65019371 Deployment Manual
  1. Manuals
  2. Brands
  3. Adobe Manuals
  4. Software
  5. 65019371
  6. Deployment manual
Adobe 65019371 Deployment Manual

Adobe 65019371 Deployment Manual

Deployment guide
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
ADOBE® CREATIVE SUITE® 4
ENTERPRISE
DEPLOYMENT GUIDE
Document Version 1.0
Sep 2009

Advertisement

Table of Contents
loading

Related Manuals for Adobe 65019371

Summary of Contents for Adobe 65019371

  • Page 1 ADOBE® CREATIVE SUITE® 4 ENTERPRISE DEPLOYMENT GUIDE Document Version 1.0 Sep 2009...
  • Page 2 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.

  • Page 3: Table Of Contents

    Uninstalling Adobe CS4 software with a deployment package ....... .
  • Page 4 Disabling Adobe Product Improvement Program ........

  • Page 5: Introduction

    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.

  • Page 6: Enterprise Deployment Description & Assumptions

    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.

  • Page 7: Adobe Package Limitations

    Adobe Package Limitations 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.

  • Page 8: The Enterprise Deployment Process

    The Enterprise Deployment Process 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: Worksheets Admin System Deployment Deployment Test System Deployment Deployment Product Install...

  • Page 9: Cs4 Deployment Packages

    CS4 Deployment Packages 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 –...

  • Page 10: Planning For Deployment

    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.
  • Page 11 SER GROUPS ACKAGES FOR RODUCTS PACKAGE GROUP NAME PRIMARY APPLICATIONS NEEDED PLATFORMS PRODUCT PACKAGE NAME COUNT Writers Adobe InDesign, Adobe InCopy Design Premium InCopy Photographers Adobe Photoshop Design Premium Layout Folks Photoshop, Adobe Illustrator, Design Premium InDesign Web Makers Adobe Dreamweaver, Adobe Flash,...

  • Page 12: Making Your Package List

    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.
  • Page 13 Making Your Package List Identifying the Package You Need 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.

  • Page 14: Choosing A Deployment Configuration

    Media Files Location you specify in the toolkit is saved in the package files. <?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) -->...
  • Page 15 Choosing a Deployment Configuration Identifying the Package You Need 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.
  • Page 16 Choosing a Deployment Configuration Identifying the Package You Need 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.

  • Page 17: Configuration Tt - Together On Target

    Examples of a few obvious choices are given below. The first two examples assume a product install folder named Relationship of Adobe Deployment Package and Value of InstallerLocation...

  • Page 18: Configuration Tm - Together On Storage Medium

    Choosing a Deployment Configuration Configuration TM — Together on Storage Medium 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.

  • Page 19: Configuration Ts - Together On Server

    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.

  • Page 20: Configuration It - Product Install Folder On Target

    Choosing a Deployment Configuration Configuration IT — Product Install Folder on Target 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.

  • Page 21: Configuration Im - Product Install Folder On Physical Medium

    Choosing a Deployment Configuration Configuration IM — Product Install Folder on Physical Medium Configuration IM — Product Install Folder on Physical Medium 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 a single piece of product media. This configuration enables a local install and may or may not require editing of the package files.

  • Page 22: Configuration Is - Product Install Folder On Server

    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.
  • Page 23 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.

  • Page 24: Specifying Packages

    Specifying Packages Filling Out the Specification Worksheet Specifying Packages You now have everything you need to specify each package on your package list. In this section you will use the worksheet called “Enterprise Deployment Planning Sheet #2: CS4 Deployment Package Specification”.
  • Page 25 Automatic update checking - Each time a CS4 application is invoked, it checks to see if any application updates are available from Adobe. The user is not aware of this check unless a product update is found, at which time the application displays a dialog asking the user if he wishes to update the application.
  • Page 26 Adobe recommends that all target systems be in a quiet state (no active users or applications) before deploying a package on them.
  • Page 27 If your users plan to run multiple applications at the same time, more system RAM is recommended, but is not required at install time. For system requirements for individual point products, go to http://www.adobe.com/products/. Half way down the left side of this page there is a pull-down menu that lists all the products. Select the product you want and click Go.
  • Page 28 Both versions of Photoshop will be installed on any 64-bit machine on which this package is deployed. Both 32-bit and 64-bit versions of the Adobe Fonts All supporting component are declined, but since this package also contains Illustrator and InDesign, both of which require this component, the package will include the 32-bit version.

  • Page 29: Choosing Shared Components

    Delete installer after ... OpenGL 2.0 Suppress updates INDOWS ONLY INSTALL OPTION Configure for 64-bit..Photoshop 32-bit Adobe Fonts All 64-bit Default values shown in bold Adobe Fonts All 32-bit PRIMARY APPLICATIONS OPTIONAL SHARED COMPONENTS OPTIONAL SUPPORTING COMPONENTS Photoshop...
  • Page 30 Adobe Interactive Runtime Environment. AIR is a cross-operating system runtime that enables you to use your existing HTML/Ajax, Flex, or Flash web development skills and tools to build and deploy rich Internet applications to the desktop. Adobe AIR applications support native desktop integration, including clipboard and drag-and-drop support, local file IO, system notification, and more.
  • Page 31 Extension Manager Media Encoder Media Encoder Add. Exporter Media Player Adobe Premiere Pro Func. Content Pixel Bender ** 64-bit version exists for 64-bit configuration, but is displayed on Supporting Components list NOTE: For the Contribute and Encore applications, Extension Manager is dependent on Bridge. That is, if you turn Bridge on, Extension Manager also comes on.

  • Page 32: Choosing Supporting Components

    Extra color profiles for various regions: European Union (EU), Japan (JA), and all other regions (NA). Required for Flash, Illustrator, InDesign, and Photoshop. Adobe Color - Photoshop Specific CS4 Specific color profiles required for Photoshop. Adobe Color * Recommended Recommended color profiles for various regions: European Union (EU), Japan Settings CS4 (JA), and all other regions (NA).
  • Page 33 Spelling and hyphenation data files used by the Linguistics library. Required for Contribute, Flash, Illustrator, InDesign, and Photoshop. Adobe WinSoft Linguistics Plug-in A variant of the Adobe Linguistics component useful for Middle Eastern, North African, and central European languages. Required for Flash, Illustrator, InDesign, and Photoshop.
  • Page 34 The TIN library adds glyphlets to their parent fonts. SING is required for InDesign and InCopy in all languages. Adobe Type Support CS4 Type support used to display fonts. Required for most CS4 applications.
  • Page 35 Specifying Packages Choosing Supporting Components After Effects Presets CMaps ++ Color EU Recommended Settings Color JA Extra Settings Color NA Extra Settings Color Photoshop Specific Color Video Profiles AE Color Video Profiles CS ColorCommonSetCMYK ColorCommonSetRGB Connect CSI ++ Default Language Dynamiclink Support ExtendScript Toolkit Flash Player 10 Active X...

  • Page 36: Preparing For Deployment

    Preparing the Product Install Folder Before you run the Adobe® deployment toolkit to create packages, you must place the product install folder for each product you plan to package in the desired location so the toolkit can find it. Have both planning sheets #2 and #3 for each package handy.

  • Page 37: Creating Packages

    Creating Packages Using the Deployment Toolkit Creating Packages Using the Deployment Toolkit In order to create packages, you need a number of things:  You need the document Enterprise Deployment Toolkit Guide which contains directions for invoking and using the toolkit. ...

  • Page 38: Testing Packages

    Creating Packages Editing Package Files Testing Packages If you are deploying with ARD, skip this section and go to Chapter If you are deploying with SMS/SCCM, skip this section and go to Chapter Now that you have created your packages, you will want to test them before deploying them widely. 1.
  • Page 39 Creating Packages Editing Package Files The following table lists all the error codes that the install program (Setup) can return: Code Description Code Description Application installed successfully Exit and restart Unable to parse command line Unsupported operating system version Unknown user interface mode specified Unsupported file system Unable to initialize ExtendScript Another instance running...

  • Page 40: Deploying Adobe® Packages With Ard

    Remote Management in the left pane and select the sharing features you want to enable. The “Copy Items” choice should be selected. 2. The Adobe package you are going to deploy is on or accessible from your admin machine. 3. The corresponding Adobe ESD (a .dmg file) is on or accessible from your admin machine.

  • Page 41: Execution

    Execution Installing Adobe CS4 software with a deployment package If you copied the Adobe package and product install folder to the target systems (configuration TT), you are now ready to run the AdobeUberInstaller program on each target machine. If you copied these items to one or more servers (configuration TS), you must make sure that all target machines have remote access to the folder on the server that contains these items.
  • Page 42 When the command is executed on the target machines, the Send UNIX Command dialog box displays the status of the process. When the process terminates, the End Adobe Setup message is displayed with an exit code.

  • Page 43: Uninstalling Adobe Cs4 Software With A Deployment Package

    Uninstalling Adobe CS4 software with a deployment package Uninstalling Adobe CS4 software with a deployment package You can use the same Adobe deployment package to uninstall any software you installed with that package. The steps are similar to those you followed to install the software.

  • Page 44: Deploying Adobe® Packages With Sms

    When using Adobe deployment packages to install CS4 software, you have two things to hand to SMS instead of one: you have the Adobe deployment package itself, which is a folder with four things in it, and you have the product install folder associated with that Adobe package. Furthermore, the XML files in the Adobe deployment package contain a path to the product install folder.
  • Page 45 Preparation In order to do this, you must combine the Adobe package and the product install folder in such a way that they appear as a single entity to SMS, before you create the SMS package for them. The best way to do this...

  • Page 46: Creating An Sms Package With Sms 2003

    Click on the Set button to the right of the Source directory field. This pops up the Browse for Folder dialog and browse for the desired path. This is the SMS package’s link to the Adobe product install folder containing the Adobe deployment package(s). Then click OK to select the highlighted path, and click OK again to dismiss the Browse for Folder dialog.

  • Page 47: Select Distribution Points For The Sms Package

    Create Programs for the SMS Package If the SMS package you just created contains a single Adobe deployment package, you need to create two programs for the SMS package: one to install and one to uninstall. If the SMS package contains multiple Adobe deployment packages, you need to create an install and an uninstall program for each Adobe package.

  • Page 48: Advertise The Sms Package Programs

    Preparation Advertise the SMS Package Programs  In the Command Line field, enter the command to be executed, as described at the beginning of this section.  Set any other fields on this tab as desired.  Click Next. 3. Specify any program requirements. Set fields on this tab as desired and click OK.
  • Page 49 Preparation Advertise the SMS Package Programs 4. Select the collection to receive the advertisement.  The name of the program you just selected for advertisement is displayed. Below it, select “Advertise this program to an existing collection” and browse for the desired collection. Your choice will be displayed in the Collection field.

  • Page 50: Creating An Sms Package With Sccm 2007

    Directory dialog. Select the type of path you want to use (UNC or local) and browse for or type in the desired path. This is the SMS package’s link to the Adobe product install folder that contains the Adobe deployment package(s). Then click OK.

  • Page 51: Create Programs For The Sms Package

    Create Programs for the SMS Package If the SMS package you just created contains a single Adobe deployment package, you need to create two programs for the SMS package: one to install and one to uninstall. If the SMS package contains multiple Adobe deployment packages, you need to create an install and an uninstall program for each Adobe package.

  • Page 52: Select Distribution Points For The Sms Package

    Creating an SMS Package with SCCM 2007 Select Distribution Points for the SMS Package  Enter an explanatory comment that describes what the program does.  In the Command Line field, enter the command to be executed, as described at the beginning of this section.
  • Page 53 Creating an SMS Package with SCCM 2007 Advertise the SMS Package Programs  In the SCCM console, navigate to Computer Management > Collections.  Locate the collection you wish to use to advertise this SMS package.  Right-click on the collection name and choose Distribute > Software. In the Distribute Software to Collection wizard, do the following: 2.
  • Page 54 Creating an SMS Package with SCCM 2007 Advertise the SMS Package Programs On the Assign Program tab:  Choose whether or not you want this program to be mandatorily run. If you do, specify the date and time at which you wish to force its execution. Notice that the advertisement date from the previous tab is displayed here for your convenience.

  • Page 55: Post-Install Configuration

    Disabling Adobe Product Improvement Program The Adobe Product Improvement Program (APIP) is offered by all of the CS4 applications and Acrobat 9. This capability is built into the applications and collects data about features usage when the application is run.

  • Page 56: Suppressing Updates With System Files

    Suppressing Application Updates  With a special installation configuration file — If you do not use Adobe deployment packages, but run Setup directly, you can create a special configuration file and place it so that Setup finds it when it runs.

  • Page 57: On The Mac

    If a DWORD value named DisableLUAPatching exists with the Installer key, set its value to 1; if not, create one and set its value. LUA stands for Low-rights User Account. On the Mac You can suppress application updates for all users for all Adobe applications. Navigate to the directory /library/preferences In a text editor or plist editor, create a new file called com.adobe.AdobeUpdater.Admin.plist...

This manual is also suitable for:

65021566 - creative suite 4 design premiumCreative suite 4 design premium

Table of Contents