What's covered

When you purchase a volume license for Adobe Creative Suite 3, Adobe provides an option that allows you to run a silent installation (that is, an installation with preselected options and no interface) on Windows or Mac OS X. In a silent installation, a custom installer runs the installers for each product in the suite by using command-line installation tools. Silent installations are also used as basis for enterprise deployment of Creative Suite 3.

Overview of silent installation

Configuring a silent installation consists of configuring the appropriate XML installer files. Then installation can be begun using a command line.

Configuring XML installer files

By default, a silent installation installs all components of Creative Suite 3 in the default location. The interface settings will be the defaults. So, when the first Creative Suite application is launched, the user will be prompted to supply a serial number, accept the End-User License Agreement (EULA) and enter registration information. Also, the Adobe Update Manager will automatically check for available updates.

Creative Suite 3 uses XML files to configure these behaviors: application.xml.override, install.xml and uninstall.xml. For complete details on how to configure these files, see the white paper listed below in "Complete deployment information."

  • application.xml.override

    This file configures the interface elements that appear during the first launch of a Creative Suite 3 application. You will need to create this file and place it in the main 'driver' payload folder.



  • install.xml and uninstall.xml

    These files control which components of Creative Suite are installed and uninstalled, respectively. You can modify these file to remove individual component 'payloads'. The same modifications need to be made to both files. Default versions of these files can be found in the "deployment" folder found in the folder which contains the suite setup programs.

Note: You can use the --record=1 option from setup.exe to create your own install.xml and remove.xml file.

Begin silent install/uninstall for Windows

A silent installation on Windows started by running setup.exe through a command line. This should be done as administrator. Use the following command line from the directory where setup.exe is.

setup --mode=silent --deploymentFile="path to installer file"

Replace path to installer file with the full path to the custom install.xml or uninstall.xml that you created.

Silent install/uninstall for Mac OS

A silent installation on Macintosh started by running the setup executable as super user through a command line. Use the following command line from the directory where setup is.

sudo Setup.app/Contents/MacOS/Setup --mode=silent --deploymentFile="path to installer file"

Replace path to installer file with the full path to the custom install.xml or uninstall.xml file that you created.

Complete deployment information

Complete information on configuring a silent installation for network deployment can be found in the Enterprise Deployment Options for Adobe Creative Suite 3 Editions and Components white paper at www.adobe.com/support/deployment/cs3_deployment.pdf.

This paper covers silent installation of Adobe Creative Suite 3, as well as individually-purchased Creative Suite 3 applications, by command line or using deployment tools such as Apple Remote Desktop (ARD) and Microsoft Systems Management Server (SMS). Also included are detailed instructions on modifying the XML installer files listed above.

Troubleshooting silent installations

Use one or more of the following steps to troubleshoot silent installations:

1. Inspect the application.xml.override file

Many Creative Suite 3 deployments fail because of typos, formatting issues or other issues with the application.xml.override file. Follow the example below:

<?xml version="1.0" encoding="utf-8"?> <Configuration> <Payload> <Data key="Serial" protected="0">000000000000000000000000</Data> <Data key="Registration">Suppress</Data> <Data key="EULA">Suppress</Data> <Data key="Updates">Suppress</Data> </Payload> </Configuration>

Common mistakes include:

  1. Misspelled words
  2. Case sensitive words being all lower case, or all upper case (all strings, and tags in XML are case sensitive)
  3. Not using the Format > Make Plain Text option in TextEdit (Mac only - by default TextEdit saves as RTF format)
  4. Make sure that the file is called application.xml.override and has no extensions (use get info, or file properties to verify)
  5. application.xml.override file not located in the proper location (check the Setup.xml file in the Payloads folder to find the location of the driver folder)
  6. Incorrect shell commands

2. Find specific error messages in the log files.

Most errors that occur during a silent installation will appear in the installation logs. For details on how to find and read these files, see, "Find and read installation logs for Creative Suite 3" (TechNote kb400593). These error messages might indicate what you need to do to solve the issue, or you can search on these errors in the Adobe knowledgebase at www.adobe.com/support/.

3. Attempt a standard installation.

If a standard (non-silent) installation does not produce an issue, then there may be an issue with one of the custom installer files. Make sure the installer files have no typos and that the information in the tags (such as serial number) are correct.

If the error does occur in a standard installation, the error messages given may have additional information, or you can search for those error messages in Adobe's knowledge base.

4. Close conflicting processes/applications.

Various applications and processes can conflict with the installation of Creative Suite 3. While a standard installation will display a list of conflicting processes during the installation process, a silent install will fail and put an error message in the installation log.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy