Adobe 65021566 Deployment Guide - Page 7

Adobe Package Limitations

Page 7 highlights

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. 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. Document Version 1.0 Sep 2009 7

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57

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.