A version of Reader is not available for this configuration. About: Adobe Acrobat Reader DC software is the free global standard for reliably viewing, printing, and commenting on PDF documents. And now, it's connected to the Adobe Document Cloud − making it easier than.

Installer customization¶

Adobe installers can be deployed over the network using standard deployment tools. As described elsewhere, you can modify the installer via the Wizard and/or manual plist configuration.

Install location¶

Customize the install location by choosing a custom location during a GUI install or by modifying the installer package manually. The Updater normally determines the application location on its own. If for some reason that search fails, the Updater looks at the AppPath preferences described below. When the Updater is disabled and/or non-default install locations are needed, set the AppPath preferences as follows:

1. Navigate (or create) to Users/<username>/Library/ApplicationSupport/Adobe/<product>/(version)/. For example, the Acrobat (version) path would be Users/<username>/Library/ApplicationSupport/Adobe/Acrobat/(version)/.
2. Create a file called com.adobe.<AcrobatReader>.InstallerOverrides.plist if it doesn’t exist.
3. Add a key called ReaderAppPath or AcrobatAppPath.

Note

Standalone installers consume only the ReaderAppPath. Updates and patches consume both ReaderAppPath and AcrobatAppPath.

4. Set the key value to the application’s path. For example, for Reader it could be /Applications/MyCustomFolder/AdobeReader.app (note the missing trailing /).

Location determination for Acrobat and Reader

• Updater workflow: When invoked by Help > Check for Updates , the Updater checks its own files for an ID, version, and the application’s absolute path.
• Installer workflow: The Updater is typically not used in enterprise settings so that IT can manage what versions are installed. When updates are invoked by using the installer command from the command line the installer looks for InstallerOverrides.plist to see if it exists (see above):

If the file is absent:

• The machine is searched for all valid applications by OS calls.
• The first valid application found is patched.
• If no valid application is found the patch installation fails giving appropriate message.

If the file is present:

• The installer checks for the presence of an AcrobatAppPath or ReaderAppPath key.
• If no valid path is found, the Updater looks for key BreakIfAppPathInvalid.
• If BreakIfAppPathInvalid is TRUE, the Updater stops.
• If FALSE, it again tries to sniff the application path from the OS.
• If no valid path can be found, the installation fails with an error.

Choosing components to install¶

Using the installer command¶

The installer command allows you to perform a number of installer-related actions. For example, you can select particular components for install during a command line installation via a choices file. To view a list of what can be installed, run:

Note

Every choiceIdentifier maps to one of the choices in the installer. The installer choices for Acrobat products are listed in the distribution file tables above.

Controlling what’s installed

The choices XML file is an array of choiceIdentifiers that toggles the installer to behave the opposite of its default. For example, since everything is installed by default, including any component de-selects that component for install. For example, to avoid installing the optional Acrobat components, include the two optional components browserplugin and printerworkflow and set their selected attribute to 0. Install os x on windows.

Verifying what will be installed

To verify which components will be installed, run:

Applying choices.xml

To apply the choices.xml file during installation, run:

Modifying the distribution file¶

The Acrobat product installer pkg contains a customizable distribution file you can use to permanently update the installer. To do so:

1. Expand the flat package distribution file at pkg-path into a new directory specified by dir-path with --expandpkg-pathdir-path. For example:

Note

The target install directory can’t exist on the machine (even in Trash).

2. Open the distribution file in a text editor.
3. Navigate to choices-outline and note the list of choices (From the tables above).
4. Add a start_selected attribute to each choice node and set it to true or false as desired:

Note

For additional distribution file details, see http://developer.apple.com/library/mac/documentation/DeveloperTools/Reference/DistributionDefinitionRef/DistributionDefinitionRef.pdf.

5. Save the distribution file.
6. Flatten the expanded package:

You can now deploy the new package via your preferred method.