© 2017 Adobe Systems, Inc. All rights reserved.

Updated Feb 12, 2018.

Macintosh Deployments

Changes across releases

What’s new for DC

The following changes appear in the DC release:

  • The method for suppressing updates.
  • Enhanced updater mode controls.
  • Automatic updates which are more silent that previous versions.
  • Updates to the Customization Wizard for Macintosh.
  • January, 2016: New deployment tools and video.

Installation scenarios

The Acrobat installer for Apple platforms can leverage either the command-line (CLI) or graphical (GUI) interfaces provided by the Apple installer. Support for Apple’s installer format and conventions allow customers install the product to managed systems via their preferred methods, including:

  • CLI: Supports any custom installation solutions required in the enterprise. Acrobat products support the Apple Remote Desktop (ARD) which provides built-in support for pushing Apple installer packages to groups of machines. For ARD details, see http://www.apple.com/remotedesktop/.
  • GUI: User interface installations manage the install on a per user basis. These are seldom used in enterprise settings.

Chained installs (DC and later)

The script and examples here leverage the new installer packaging tools that Apple currently uses. Note that the tools used in the Acrobat 10.x and 11.x videos are now deprecated. One of our resident experts, Steve Cordero, has kindly created a new video using the latest tools to install Acrobat DC. See https://youtu.be/Cb7ImCqfcIA.

Build cmd line

For more information, see the Apple manpage.

The build script uses the following properties:

  • --root: Path to folder containing full/patch installer zip files
  • --scripts: Path to the folder containing postinstall script
  • --identifier: com.adobe.acrobat.chainedInstaller
  • --install-location: /private/tmp/chained installer package path
pkgbuild --root /Users/labuser/Desktop/ZIPInstallers/ --scripts
/Users/labuser/Desktop/shellscript/ --identifier com.adobe.acrobat.chainedInstaller
--install-location /private/tmp/ /Users/labuser/Desktop/NewInstaller/WinterRelease2016Installer.pkg


Note that the following shell script is slightly different than those provided previously (and from those in previous videos).

function unzipPkg
        rm -rf "/private/tmp/Acrobat DC Installer.pkg"
        unzip "/private/tmp/Acrobat DC Installer.pkg.zip" -d "/private/tmp";
        rm -f "/private/tmp/Acrobat DC Installer.pkg.zip"

        rm -rf "/private/tmp/AcrobatDCUpd1501020056.pkg"
        unzip "/private/tmp/AcrobatDCUpd1501020056.pkg.zip" -d "/private/tmp";
        rm -f "/private/tmp/AcrobatDCUpd1501020056.pkg.zip"

function installAcrobat
        installer -pkg "/private/tmp/Acrobat DC Installer.pkg" -target /
        if (test $? = 0) then
                echo "Acrobat DC installed."
                rm -rf "/private/tmp/Acrobat DC Installer.pkg"
                echo "ERROR: Acrobat DC installation failed."
                rm -rf "/private/tmp/Acrobat DC Installer.pkg"
                exit 1

function installAcrobatUpd
        installer -pkg "/private/tmp/AcrobatDCUpd1501020056.pkg" -target /
        if (test $? = 0) then
                echo "Acrobat Version 2015.010.20056  installed."
                rm -rf "/private/tmp/AcrobatDCUpd1501020056.pkg"
                echo "ERROR: Acrobat Version 2015.010.20056 installation failed."
                rm -rf "/private/tmp/AcrobatDCUpd1501020056.pkg"
                exit 1


Chained installs

As shown in the video tutorial, the Macintosh chained installation process has been greatly simplified. The Adobe Customization Wizard manages licensing, offline exception activation, EULA acceptance, and registration.

After using the Wizard:

  1. Add the zipped Acrobat custom pkg file, the zipped updater file and the PostInstallShellScript.sh file to PackageMaker.
  2. Set the /private/tmp/ location.
  3. Reference the PostInstallShellScript.sh file.
  4. Build.


The new script is equally simple in that it just copies zipped installer pkg to /private/tmp/, unzips the pkg installer pkg, and runs the install.

Installing Acrobat with a quarterly update


rm -rf "/private/tmp/Adobe Acrobat (version) Pro Installer.pkg"
unzip "/private/tmp/AcroPro(version).pkg.zip" -d "/private/tmp";

rm -rf "/private/tmp/AcrobatUpd(version).pkg"
unzip "/private/tmp/AcrobatUpd(version).pkg.zip" -d "/private/tmp";

installer -pkg "/private/tmp/Adobe Acrobat (version) Pro Installer.pkg" -target /
if (test $? = 0) then
echo "Acrobat (version) installed."
rm -rf "/private/tmp/Adobe Acrobat (version) Pro Installer.pkg"
echo "ERROR: Acrobat (version) installation failed."
rm -rf "/private/tmp/Adobe Acrobat (version) Pro Installer.pkg"
exit 1

installer -pkg "/private/tmp/AcrobatUpd(version).pkg" -target /
if (test $? = 0) then
echo "Acrobat (version) installed."
rm -rf "/private/tmp/AcrobatUpd(version).pkg"
echo "ERROR: Acrobat (version) installation failed."
rm -rf "/private/tmp/AcrobatUpd(version).pkg"
exit 1


Installing Reader 11.0 with a quarterly


rm -rf "/private/tmp/Adobe Reader (version) Installer.pkg"
unzip "/private/tmp/Adobe Reader (version) Installer.pkg.zip" -d "/private/tmp";

rm -rf "/private/tmp/AdbeRdrUpd(version).pkg"
unzip "/private/tmp/AdbeRdrUpd(version).pkg.zip" -d "/private/tmp";


installer -pkg "/private/tmp/Adobe Reader (version) Installer.pkg" -target /
if (test $? = 0) then
echo "Adobe Reader (version) installed."
rm -rf "/private/tmp/Adobe Reader (version) Installer.pkg"
echo "ERROR: Adobe Reader (version) installation failed."
rm -rf "/private/tmp/Adobe Reader (version) Installer.pkg"
exit 1

installer -pkg "/private/tmp/AcrobatUpd11001.pkg" -target /
if (test $? = 0) then
echo "Adobe Reader 11.0.09 installed."
rm -rf "/private/tmp/AdbeRdrUpd(version).pkg"
echo "ERROR: Adobe Reader 11.0.09 installation failed."
rm -rf "/private/tmp/AdbeRdrUpd(version).pkg"
exit 1


Standalone products vs CS bundles

Installation workflows vary depending on whether you are installing Acrobat as a standalone application or as part of a Create Suite (CS) bundle. Standalone Acrobat deployments use a standard installer and should adhere to the instructions in this document.

Acrobat bundled and standalone products support the Adobe Application Manager Enterprise Edition (AAMEE) for the customization and packaging of the Creative Suite applications. CS-style deployment support means that admins can use the Adobe Provisioning Toolkit Enterprise Edition (APTEE) command line tool. This tool is provided as part of the AAMEE download. It is particularly useful for configuring installs as well as the serialization of Adobe products. Download the tools and documentation from http://www.adobe.com/devnet/creativesuite/enterprisedeployment.html.


As noted in the troubleshooting section, it is not possible to grant an offline exception to activation for Acrobat in conjunction with an imaged OS deployment method.

Installer details

Installer behavior for existing installations

When installing the application on a system where it already exists in the installation location, several factors may affect the installation workflow:

  • Installing over an earlier version (Reader only): When an earlier version already exists in the target install location, then:

    • For GUI installations, a prompt informs the user that the product already exists and asks whether the installation should proceed. If YES, the existing <application>.app is moved to Trash and the new Reader is installed. If NO, then the existing Reader is not touched and the installer returns with an error.
    • For CLI installations, then the installer silently moves application.app to Trash and installs the newer one without further input. The old application is moved to Trash so that if installation fails then the user can restore old application.
  • Installing over the same base version: If the existing application has the same base version as the new one, then both GUI and CLI installations proceed as normal upgrades.

  • Installing over a new version: If the existing application has a higher version than the installing one, then the installation fails.

    • For GUI installations, an alert informs the user that a new version is already present.
    • For CLI installations, a log entry in the system’s installer log (/var/log/install.log) indicates that a new version is already present.

Install locations

For command line installations, the default locations are configurable. Default GUI installations of Acrobat and Reader options are as follows:

  • Reader: Reader is always installed in /Applications of the root volume. The location is not customizable.
  • Acrobat: Acrobat can be installed to any custom folder on 10.6 and later.


Customization is not supported in OSX 10.5 and the application installs in the default location at /Applications/Adobe Acrobat <version> Pro.


Adobe’s Mac installer is a flat package installer. The .pkg can be expanded using the system’s pkgutil command so that you can see distribution file and its constituent components.


The Application check box that allows selection of specific components does not appear in 10.5 due to an Apple bug.

Acrobat distribution file
Component Description
acropreinstall Required: Validates if the installation should proceed or not.
aam Required: Installs Adobe’s licensing module in the Users/<user name>/Library/Application Support/Adobe/OOBE folder.
coreapp Required: Installs Acrobat.app and Distiller.app. The default location is /Applications/Adobe Acrobat (version) Pro/.
appsupport Required: Installs various support files in the Users/<user name>/Library/Application Support/Adobe/ folder.
prefs Required: Installs files in the Users/<user name>/Library/Preferences area.
browserplugin Optional: Installs the Internet plug-in which integrates Acrobat with Safari.
Reader distribution file
Component Description
coreapp Required: Installs Acrobat.app and Distiller.app. The default location is /Applications/Adobe Acrobat (version) Pro.app/Adobe Acrobat Pro.app and /Applications/Adobe Reader.app
browserplugin Optional: Installs the Internet plug-in which integrates Acrobat with Safari.
appsupport Required: Installs various support files in the Users/<user name>/Library/Application Support/Adobe/ folder.


Language is determined by the system OS language.

Adobe ships strings, a Read Me, custom installer plugins, and related resources in all locales with the installer. The installer GUI itself is provided by the built-in Mac OS X system installer, with the application localized by Apple and using the current system language. For Adobe files like ReadMes, the Mac OS X system installer simply offers the user to view the Read Me in the system language.

Installer customization

Adobe installers can be deployed over the network using standard deployment tools. As described below, some installation and application customization is available by creating and configuring com.adobe.Acrobat.InstallerOverrides.plist.


The Customization Wizard for Macintosh also provides a method for configuring commonly changed preferences.

Install location

The default install location for Acrobat products is:

  • Acrobat: /Applications/Adobe Acrobat (version) Pro/Adobe Acrobat Pro.app
  • Reader: /Applications/Adobe Reader.app

The default location can be customized by choosing a custom location during a GUI install or modifying the installer package manually. The standard 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/<user name>/Library/Application Support/Adobe/<product>/(version)/. For example, the Acrobat (version) path would be Users/<user name>/Library/Application Support/Adobe/Acrobat/(version)/.
  2. Create a file called com.adobe.<Acrobat | Reader>.InstallerOverrides.plist if it doesn’t exist.
  3. Add a key called ReaderAppPath or AcrobatAppPath.


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

  1. Set the key value to the application’s path. For example, for Reader it could be /Applications/MyCustomFolder/Adobe Reader.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. The default installation path is:

    • Acrobat: /Applications/Adobe Acrobat Pro/Adobe Acrobat (version) Pro.app
    • Reader: /Applications/Adobe Reader.app
  • 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:

installer -package <path/Acrobat (version) installer.pkg> -showChoicesXML -target / | grep -A 1 choiceIdentifier


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.

choices XML

Verifying what will be installed

To verify which components will be installed, run:

installer -package <path/Acrobat product installer.pkg> -target
/ -showChoicesAfterApplyingChangesXML <path/choices.xml>

Applying choices.xml

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

installer -package "path to Adobe Reader (version) Installer.pkg"  -target / -applyChoiceChangesXML  <path/choices.xml>

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 --expand pkg-path dir-path. For example:
--expand <path/Acrobat product installer.pkg>
<target install folder>


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

  1. Open the distribution file in a text editor.
  2. Navigate to choices-outline and note the list of choices (From the tables above).
  3. Add a start_selected attribute to each choice node and set it to true or false as desired:
  1. Save the distribution file.
  2. Flatten the expanded package:
pkgutil --flatten <path/expanded folder>
<path/Acrobat product installer.pkg>

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

Installing special fonts

Acrobat products ship with a number of fonts. However, you may need to install certain fonts manually or customize the installer to perform that task. For example, non-Japanese Reader installers do not come with Japanese fonts, but such fonts can be included at installation time.


The font packs and spelling dictionary only need to be installed with Reader as they are already present in Acrobat. Download the single font packs separately.

To enable the application to render non-default fonts do the following (this example uses the Japanese font pack):

  1. Install the application.
  2. Download the requisite font pack installers. For example, the Japanese package identifier is com.adobe.Reader.fontpack.10.ja_JP.pkg.
  3. Run the installer via the GUI or command line:
sudo installer -pkg <installer filename>.pkg -target /

Locking settings

Admins can set and lock any Mac setting that is lockable on Windows. For a list of lockable settings, see the Preference Reference.


While preference names for unlocked settings do not use Hungarian notation, all locked settings (with the exception of attachment settings) DO use Hungarian notation. That is, you must prepend the preference name with its data type (“b” for boolean, “i” for integer, and so on). On Mac, the locked incarnation of a setting uses the same name as if it resides on Windows.


The method for locking attachment-related settings is described in Locking attachment settings.

A feature lockdown file is a system-level plist file for a root account. This files does not exist by default, but you may create one as follows:

  1. Navigate to <machine root>/Library/Preferences.

  2. Create a new file called com.adobe.(Acrobat.Pro | Reader).plist This file does not exist by default.

  3. Open the plist with an editor.

  4. Set the version value in the key. For DC, this is either DC for the Continuous track or 2015|2017 for the Classic track.

  5. Add entries as shown below in the following examples. Note the following:

    • Always prepend the data type to the preference name (use the same name as on Windows).
    • Verify the path contains the correct product version.
  1. Save and close the plist.

Future product updates won’t affect this file.

Lockdown file construction

The plist format varies with the type of editor/viewer you use. The examples here are XML.

Like Windows, prepend the data type to the preference name. Version and section nodes do not have a data type. Also, the Mac preference hierarchy mirrors the Windows registry path. Thus, a Windows path looks like:

[HKLM root\<version>\FeatureLockDown]bUpdater

On Mac, an XML representation looks like:


Mac locked setting examples

Blacklisting the Javascript API app.alert

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">

Disabling showing Adobe messages at startup

The following example is not XML, but is constructed relatively similarly:

>> ] /IPM [ /c << /bShowMsgAtLaunch [ /b false] >> ] >>

When using this format, verify there are spaces between >> and ]. The ending should be ] >> ] >> ] >> not ]>> ]>> ] >>.

Disabling the Updater


Controlling updates

Beginning with version 10.1.1, you can disable and lock the Updater settings so that users can’t change the setting. As shown above, set bUpdater to 0.

Set the update mode (DC)

To override the default update settings:

  1. Create a FeatureLockDown file as described above.
  2. Create bUpdater at the root of the file and set the value to false/0. See the example above. Doing so overrides UpdateMode.

Note the following:

  • DC Continuous track web and desktop updates are released in tandem to ensure cloud and desktop features remain synchronized and compatible. Failure to update desktop components while leaving services enabled may lead to an unsupported configuration.
  • Updater preferences in the UI have been changed to only show the “Auto” and “Off” options. The Continuous track of Reader does not provide any UI options and the default is “Auto”.

Removing the Updater.acroplugin

To disable the application’s ability to update altogether, use a post install script to move, rename, or delete the Updater.acroplugin file from <root>/Contents/Built-in/Plug-ins/Updater.acroplugin.

Locking attachment settings

Attachment settings are locked differently than other settings as follows:

  • Settings exist in a FeatureLockDown cabinet file by default. It is not a plist file.
  • The file is located at /Library/Application Support/Adobe/Acrobat/DC|2015|2017/Preferences/.
  • This implementation originated with DC product versions.
  • Do not use Hungarian notation.
  • If you edit the file, future updates won’t overwrite your custom settings.
  • To modify the file, simply open and edit as needed.
<</FileAttachmentPerms [/i 1] /DefaultLaunchAttachmentPerms [ /c << /UnlistedAttachmentTypePerm [/i 2]  … ] >> ]
Lockdown file syntax
Field Description
<< Begin XML element
>> Close XML element
<< >> Container of the element components
/ Entry name designator
[ Open bracket
] Closed bracket
[] Container for an entry name value
c Mac data type
i Mac data type
t Mac data type
b Mac data type
: Separates value names from value integers

Delimits multiple value names in a list
( Begins a list
) Ends a list
( ) A list container

Apple Remote Desktop

Administrators can remotely deploy Acrobat/Reader to multiple Macintosh systems running Mac OS 10.5 or later (10.x) and 10.6 or later across their network. Using Apple Remote Desktop 3 (commonly referred to as ARD), an administrator can install Acrobat/Reader automatically, without user intervention, to one or more remote computers. ARD copies the package to the computers selected for installation, runs the installer with no visible window or user interaction required, and then erases the installer files on completion.

The Acrobat Macintosh installer will perform initialization work such as the Adobe Application Manager installation as well as components needed for the serialization of the application. While serialization happens at launch time by default, enterprises can preserialize with APTEE (Adobe provisioning tool enterprise edition) or the Customization Wizard for Mac.

The locale of the launched installation depends upon the current locale set on the user’s machine. The Installer application picks up strings from within our installation package in the order of locales specified in the system locale preference panel.

Installing with Remote Desktop

These instructions provide only an overview. If you are not familiar with Apple Remote Desktop, refer to Apple’s documentation http://www.apple.com/remotedesktop/.

To deploy the product via ARD:

  1. Open ARD.
  2. Verify Remote Management and Sharing is enabled for every target computer.
  3. Select one or more Macintosh computers on which you want to install Acrobat or Reader.
  4. Choose Install on the top of the Remote Desktop window.
  5. When the Install Packages window appears, choose the + button at the top left of the Install Packages window.
  6. Locate and select the Acrobat or Reader .pkg file.
  7. Choose Open to add it to the Install Packages List.
  8. Choose Install to perform a complete installation of Acrobat or Reader on the selected machines.


Apple Remote Desktop shows a progress bar and task status of the installation for each of the machines selected for the installation.

Deploy the Adobe Provisioning Tool

10.x and later.

The APT is only for Acrobat deployments and does not work with Reader. The tool streamlines enterprise deployment by enabling control of installation workflows such as:

  • Configuring licenses for 1-N users (pre-serializes the keys).
  • Suppressing the end user license agreement (EULA).
  • Suppressing the Adobe ID dialog.

To use the provisioning tool:

  1. Download the <provisioning tool.
  2. Open ARD.
  3. Select one or more Macintosh computers on which you want to configure Acrobat products.
  4. Choose Copy.
  5. In the Copy Items screen’s Place Items drop down list, choose Applications Folder.
  6. Verify the Set Item ownership drop down list is selected to Inherit from destination folder.
  7. In the Items To Copy list, navigate to the .dmg that you downloaded.
  8. Select the Adobe provisioning tool.
  9. Choose Copy.


Once the Adobe provisioning tool is copied to the client machines, use a UNIX command to configure licensing and to suppress EULA and Adobe ID dialog.

Customizing installs with APT

The APT is not for use with Adobe Reader. Acrobat installs can be customized with the APT as follows.

  1. Open ARD.
  2. Select one or more Macintosh computers on which you want to license an Acrobat product.
  3. Choose Manage > Send UNIX Command.
  4. Type the desired command or run the command from a script as follows:
sudo "<path>/adobe_provisioning_tool.app/Contents/MacOS/adobe_provisioning_tool"
<1 or more APT command line(s)>
  1. Run the command as the user “root.”
  2. Choose Send.
Acrobat provisioning tool commands
Feature Command
Configure enterprise licensing -C -a "Users/<user name>/Library/Application Support/Adobe/Acrobat 10 AMT/AMT" -s <serial number>
Suppress the end user license agreement (EULA) -S  -a "Users/<user name>/Library/Application Support/Adobe/Acrobat 10 AMT/AMT"
Suppress the Adobe ID (registration) dialog -R  -a "Users/<user name>/Library/Application Support/Adobe/Acrobat 10 AMT/AMT"

One step ARD deployments

Cmd line uninstalls

Product installs also provide an uninstaller along with the application at Applications/<product name>. For example, the path might be Applications/Adobe Acrobat (version) Pro. End users will uninstall the product via the user interface. However, it’s also possible to uninstall via the command line.

To uninstall from the Terminal in Mac OS X:

  1. Close any running Acrobat products.
  2. Invoke the uninstaller as follows:
$ sudo "/Applications/Adobe Acrobat (version) Pro/Adobe Acrobat Pro.app/Contents/Support/Acrobat
Uninstaller.app/Contents/MacOS/RemoverTool" "/Applications/Adobe Acrobat (version) Pro/Adobe Acrobat
Pro.app/Contents/Support/Acrobat Uninstaller.app/Contents/MacOS/RemoverTool"
"/Applications/Adobe Acrobat (version) Pro/Adobe Acrobat Pro.app"


The uninstaller application is located inside the Acrobat App.

Successful uninstalls should remove product files, licensing information (including the serial number, EULA acceptance status, and so on.

Macintosh troubleshooting

Why don’t my plist preferences take effect?

After you’ve modified setting in a plist, restart the machine or run killall cfprefsd.


There are two primary logs: one for the installer application and one for the Updater which is responsible for detecting and downloading updates as well as invoking the installer.

Install log

Apple’s Installer.app creates an install log that should contain all basic success and failure details. The file is located at /private/var/log/install.log created by Apple’s Installer.app.

By default, the installer logs only necessary information in installer log. However, it is possible to configure the log to provide debug output for 10.x and later products.

To set this preference, do the following:

  1. Go to Users/<user name>/Library/Application Support/Adobe/Acrobat/(version), or create it if it doesn’t exist.
  2. Open com.adobe.acrobat.InstallerOverrides.plist, or create it if it doesn’t exist.
  3. Create following key-value pair: AcroPatchLogLevel:debug

debug logging

  1. Save and close the file.

Updater log

The Updater creates a log at Users/<user name>/Library/Logs/Adobe/{application name} Updater.log. By default, it provides non-verbose output. To change the default:

  1. Go to Users/<user name>/Library/Preferences.
  2. Open to com.adobe.ARM.plist.


Create the file if it does not exist. The file will not exist unless the Updater has run at least once.

  1. Create a new key if it does not exist: LogLevel.

  2. Set LogLevel:

    • Brief: -int 0
    • Verbose: -int 1
  3. Save and close the file.

The log size limit is as follows: If an existing log is bigger than 1 MB, the Updater truncates the log. Old log files are backed up once as Adobe Acrobat/Reader Updater-old.log and overwrites any existing old.log.

Installation failures

Conflicting processes running

Installs should take place on machines where there are no instances of an Acrobat product or plugin running.

Licensing problems

Why does my serial number not validate?

If validation occurs through an authenticating proxy, the Adobe Provisioning Tool may fail to validate a serial number.

Plist settings issues

It’s always good to remember the following:

  • Plist files are binary files. Different editors display plist contents in different ways such as XML, structured text, etc.
  • Different editors may handle preference values in odd ways. For example, the 3rd party Preference Setter application will set Integer 0, Boolean False, but Number 0, Boolean No may not work. In XCode, the latter works fine.
  • Plist files are cached during the current session. If you find your recently set preferences are disappearing, note that Acrobat reads the cached copy rather than the edited files and that it then writes out the plist file on exit, thereby overwriting your edits. To sync the cached plist copy with the newly edited plist, type the following in your terminal:
defaults read <path to your plist file>

EULA issues

Setting the EULA plist preference directly does not work. To accept the EULA on behalf of users, use the Mac Wizard or the PRTK tool.