- Download Adobe Acrobat Reader DC. About: Adobe Acrobat Reader DC software is the free global standard for reliably viewing, printing, and commenting on PDF documents. It's the only PDF viewer that can open and interact with all types of PDF content, including forms and multimedia.
- How to deploy Acrobat Reader DC with SCCM using the application model. The installation will be unattended and silent as every good SCCM deployment should be. It also supersedes old versions of Adobe Acrobat Reader to make sure they get uninstalled before we install the new version. Step 1 – Download Acrobat Reader DC.
- The command line for the package created on 19 Dec 2017 is setup.exe -silent Adobe was not not able to provide a working silent install. The above command was guessed by reading pdapp.log.
- Following up on last week’s announcement of Adobe Acrobat and Acrobat Reader DC’s release, this article documents the silent install options for Reader.When it comes to deployment, you typically want a silent install so it is not hanging a computer waiting for somebody to click the ‘Next’ button.
- Adobe Acrobat X Silent Install
- Silent Install Switches
- Adobe Acrobat Xi Silent Install
- Adobe Acrobat Silent Install Switches
Serialized deployment¶
Apr 25, 2019 Re: Adobe Reader DC 15.023 silent install command brianh10261911 Jun 12, 2018 1:46 PM (in response to dustinn74320929) Also, the problem is that it's the wrong manual. The OP specifically asked about exe switches. This manual is for MSI switches.
Serial numbers are gradually being phased out in favor of named user licensing which is more flexible and easier to manage. By the end of 2019. …………..
Online requirement¶
Online product activation is required as described in the policy details at http://www.adobe.com/products/activation/. There is a 30 day grace period for online activation.
As described below, in settings where machines are permanently or temporarily offline, admins activate the installer prior to deployment and grant an offline exception to the activation requirement for subsequent installs. You can do this via the Wizard or APTEE.
Serializing an imaged OS¶
To image a machine with Acrobat, first generate a prov.xml file on an online machine and then create a permanent offline exception that is not machine specific. Note the following:
- This method can only be used with volume licenses.
- Acrobat need not be installed to run this command.
- The machine on which this command is run must be online.
- It is highly recommended to suppress registration.
Steps:
- Connect to the internet.
- Download the latest Adobe Provisioning Toolkit Enterprise Edition.
- Open an elevated prompt (run as administrator).
- Generate a prov.xml file on any machine connected to the internet using the following APTEE tool command line with the following options:
serial
: The serial numberregsuppress=ss
: Optional; suppresses registrationeulasuppress
: Optional; suppresses the EULA promptlocales
: Optional; specify from the limited list of locales in the formal xx_XX or ALLprovfile
: Optional; path of the folder where prov.xml is created. If this parameter is not specified, prov.xml is created in the folder in which APTEE resides.
- Install Acrobat on the master image.
- On the master image, copy the prov.xml file created above.
- Serialize and activate Acrobat using the following APTEE tool command line:
- Launch Acrobat once for about a minute and close.
Note
Granting an offline exception to activation using the Customization Wizard for an imaged OS deployment method is not supported.
Serializing via the Wizard¶
If you are using the Wizard to configure the application prior to deployment, enter the license information in the user interface as described in the user documentation. Doing so writes the serial number information to the abcpy.ini file. This file needs to be placed in the same directory as the MSI used at installation time.
Serializing via an .msi¶
Installations that use MSI files sometimes require that the Abcpy.ini file contain the serial number information for the application. If you have not used the Wizard, set this up manually as follows:
- Open Abcpy.ini in a text editor.
- Find ISX_SERIALNUMBER.
- Add the serial number.
- Save and close the file.
- Verify abcpy.ini is located in the same directory as the MSI prior to installation.
Serializing an .exe (bootstrapper)¶
Deployments that use EXE files require that the Setup.ini file contain the serial number information for the application. For example, during a bootstrapper Setup.exe deployment, the EXE file reads Setup.ini to get the needed information. You can set this up manually as follows:
Adobe Acrobat X Silent Install
- Open Setup.ini in a text editor.
- Find ISX_SERIALNUMBER.
- Add the serial number.
- Save and close the file.
- Verify Setup.exe located in the same directory as the EXE prior to installation.
Serializing via the command line¶
The license key can be entered on the command line during deployment by using the ISX_SERIALNUMBER property.
- To run the installer by using setup.exe, enter:
- To run the installer by using the msiexec program, enter:
Serialization via the APTEE¶
Acrobat products support the use the Adobe Provisioning Toolkit Enterprise Edition (APTEE) command line tool for both Windows and Macintosh. You can use it with both the standalone product and that bundled with the Creative Suite. Except for providing activation exceptions on an imaged OS, you can use the Wizard to do most of the things the APTEE tool does, and the Wizard is the preferred method for setting such features.
To get started:
- Download and install the latest APTEE (Available from the Licensing Web Site and also installed with the Wizard).
- Navigate to the APTEE folder.
- Open a command prompt and run the command below with administrator privileges.
Activation exceptions¶
Use activation exceptions when target machines do not have internet access.
Activation exception 1¶
This method is machine-specific and is typically used by end users. However, it can be used with both retail and volume licenses.
- Generate a request code:
- Go online from any machine to www.adobe.com/go/getactivated.
- Generate a response code.
- Validate the response code:
The product is now ready to use.
Activation exception 2¶
You can create an activated production package and serialize post deployment using APTEE. This method is used when user machines are not going to be online. To do so,
- Run APTEE on an online machine to generate the prov.xml file.
- Deploy the product on each machine.
- Run APTEE with the prov.xml file on each machine.
Migrating to a new license¶
If you need to re-serialize Acrobat with a different serial or change the product key, use the APTEE tool:
- Install Acrobat using a serial number.
- Run the following:
Activation behind proxys¶
For users behind an authenticating proxy, registering the product via the default HTML screens is not possible, thereby blocking trial and subscription workflows that require entering an Adobe ID. Customers who are installing trials or subscriptions should authenticate using Flex-based screens which must be enabled manually. The process involves creating an override file and using the Wizard to install it in a specific location.
To enable the Flex screen:
- Create a file named application.xml.override. The name must be exact and not have a .txt extension.
- Copy and paste the following lines in to the file:
- Download and install Adobe Customization Wizard.
- Download the Acrobat installer to a location which is writable by non-privileged users.
- Open the AcroPro.msi with the Wizard.
- In the left-hand pane, choose Files and Folders. The screen changes to a screen with a Modify and Summary tab.
- Choose Modify.
- In the lower left window for the Destination Computer, choose ProgramFileFolder > Adobe > (Acrobat Version) > Acrobat > AMT. The lower right rectangle will show three files: aul.xml, application.xml, and SlConfig.xml.
- Drag and drop the application.xml.override file into this rectangle.
- Choose Save.
- Exit the Wizard.
- Install Acrobat using the customized installer.
Once complete, the installer processes the override file and always displays the Flex screens when needed.
This article explains how to deploy Adobe® Acrobat® DC if you are using Adobe® Creative Cloud™ for teams or enterprise.
On macOS and Windows OS, Acrobat DC is included in the package file that is created using Creative Cloud Packager. Deploy Acrobat DC using the package Setup file through the command line or by double-clicking it (and not through the Exception deployer tool).
You can also use the Enterprise Toolkit (ETK) to deploy customized products across your organization, set up virtualized installs, and create enterprise PDF workflows. Acrobat ETK provides wide range of IT details about Adobe Acrobat Document Cloud configuration and deployment, also, about the earlier product versions.
Based on your business or organization requirement, you can choose Adobe subscription license, Adobe term license, or Adobe Acrobat perpetual license. To find best licensing program for your organization, see Compare licensing Programs.
Adobe Acrobat Licensing are associated with Continuous track. For more information on tracks, see Document Cloud Product Tracks. Once you have chosen a licensing program and the required product track, download the installer to proceed further in the deployment process.
If you no longer have the installation media for Acrobat DC (Non-subscription, serial number based), you can download the replacement installer from Download Acrobat DC | Non-subscription.
You can use Adobe Licensing Website (LWS) to find serial numbers, track orders, view purchase histories, check upgrade entitlements and points, change or add account contacts and information, merge accounts, and download software. For more information, see the documentation on Adobe Licensing Website (LWS).
The Adobe Security Notification Service is a free email notification service that Adobe uses to send information to customers about the security of Adobe products. For more information, see Adobe Security Notifications Registration.
Adobe provides a security model designed to help you protect your environment from security attacks. To explore the options for tuning applications for the desired security level, see Application Security Overview.
Adobe Customization Wizard DC (Windows and macOS) is available in ETK. The wizard streamlines the task of configuring (customizing) the installer before organization-wide deployment. For example, if you have a volume license, you do not need to register and personalize each copy of the product you install. You can customize the installer to skip the standard registration questions, accept the End User License Agreement, and fill in your organization name automatically.
The wizard DC can only be used to tune Acrobat DC products.
Use Customization Wizard to customize Acrobat packages
If you are an enterprise customer, you can use the Adobe Customization Wizard to further customize your package, using the following workflow.
To customize Acrobat DC from your downloaded package, you need the latest version of the Adobe Customization wizard, and the downloaded Acrobat Pro .msi (Windows) or .pkg (macOS) file.
Note:
The version of the wizard should be the same as the version of Acrobat in the package created by Creative Cloud Packager.
- Create a package using either of the following methods:
- Note:Do not enter your Creative Cloud Enterprise License key in to the configuration wizard if already specified in the Create Package workflow.
- From the File menu in the Customization Wizard, select Open Package.
- Browse to the package created in step 2, and open the Acrobat Pro .msi (Windows) or .pkg (mac OS) file in the following location:
AcrobatBuildSetupAPRO19.0Adobe Acrobat - In the Personalization Options section, enter the serial number of Creative Cloud for enterprise in the Serial Number field.Note:
- If you have more than one Acrobat DC Pro serial numbers, you can use the serial number for Creative Cloud for enterprise or Acrobat Pro.
- If you use the Customization Wizard for creating a custom package for named users, leave the serial field blank.
- Click the Allow standalone Acrobat deployment with CCE serial check box.
- Click Grant Offline Exception & Disable Registration.
- Save the package.Windows: Saving the package, generates a 'transformations' file (with the extension .mst) in the Acrobat directory. This file is used when installing Acrobat via the package. Deploy the output of the Customization Wizard to your clients as described in the Customization Wizard documentation.macOS: Overwrite the Acrobat PKG contained in the Creative Cloud Packager created package with the Customization wizard output.
- Proceed to deploy the Creative Cloud Packager created MSI (Windows) or PKG (macOS) file to the client.
For more information, see Adobe Customization Wizard documentation and MSI and Cmd-line examples.
Note:
For a Windows package, once the MST file (also known as the transformations file) is saved to the Acrobat subdirectory within the package, you can begin to deploy the software to the target systems. It is possible to install Acrobat using its own MSI (Windows) or PKG (macOS) file, but it does not install the licensing information and any dependencies with the package. It is recommended to use the 'setup.exe' in the 'Build' directory to install a package created with Creative Cloud Packager which contains Acrobat DC, to ensure these dependencies (such as Microsoft's Visual C++ Redistributables) are also installed. See below for further information in installation.
The MSI installer does not handle dependencies such as the Microsoft Visual C++ redistributables relevant to the version of Acrobat (like PDFMaker) being installed.
Caution:
If you are using hard disk cloning or a similar technology, the software should be installed after the operating system is imaged.
To install a package containing Acrobat DC, you can either run the setup.exe (in the 'Build' directory) using the command line or by double-clicking it.
The language in which the package is installed depends on three factors:
- If Match OS Language option is selected while creating the package.
- The language you specify in the command while deploying the package.
- The language in which you have created the package.
The following table details how each of these factors affects the language in which the package is installed.
Match OS language | Language explicitly specified while deploying a package using | The package is installed in... |
Selected | No | OS Language |
Selected | Yes | Language explicitly specified in command line while deploying a package |
Not Selected | ||
Not Selected | No | Language in which the package is created |
Selected | Yes, but the specified language is unavailable | Language in which the package is created |
Not Selected |
Note:
When the installer is run, it checks for the locale that is set at the system level and not at the user level. For more details on this setting, see Install Creative Cloud package with Match OS Language option.
Command line has additional required parameters, for which default values are taken if you run package Setup.exe by double-clicking.
In the command:
- [INSTALLDIR] is the installation directory where Acrobat is to be installed on the client machine.
- [installLanguage] is the locale in which Acrobat is to be installed. Acrobat might not be available in all languages, so you can only provide a locale that is supported by the Acrobat for that particular media. For example, to install Acrobat in the English (US) locale, specify en_US as the locale in the command. For a list of available locales for Acrobat in a particular suite, see Locales for different Acrobat configurations.
setup [--silent] [--ADOBEINSTALLDIR=] [--INSTALLLANGUAGE=]
Syntax example:
setup.exe --silent --ADOBEINSTALLDIR='C:InstallDir' --INSTALLLANGUAGE=fr_CA
Location of setup.exe:
The following table provides the value of the locale to be specified for the --installLanguage option.
Suite GEO | Suite locales | Acrobat DC locales | Acrobat bundle |
English | English (North America) | en_US | Acro LS1 |
English (International) | en_US | ||
German | de_DE | ||
French | fr_FR | ||
French Canadian | fr_FR | ||
Japanese | Japanese | ja_JP | Acro LS2 |
Americas / Europe (Central Europe) | English (North America) | en_US | Acro LS1 |
English (International) | en_US | ||
German | de_DE | ||
French | fr_FR | ||
French Canadian | fr_FR | ||
Spanish | es_ES | Acro LS6 | |
Spanish North America (es_MX) | es_ES | ||
Spanish Latin America (es_LA) | es_ES | ||
Italian | it_IT | ||
Dutch | nl_NL | ||
Portuguese (Brazil) | pt_BR | ||
Swedish | sv_SV | Acro LS7 | |
Danish | da_DK | ||
Finnish | fi_FI | ||
ASIA | Korean | ko_KR | Acro LS5 |
Chinese Simplified | zh_CN | Acro LS3 | |
Chinese Traditional | zh_TW | Acro LS4 | |
Eastern Europe | Russian | ru_RU | |
Turkish | tr_TR | ||
Ukrainian | uk_UA | ||
Czech | cs_CZ | Acro LS8 | |
Polish | pl_PL | ||
Hungarian | hu_HU | ||
North African French | fr_FR | Acro LS1 | |
Middle Eastern English Arabic | en_US | ||
Middle Eastern English Hebrew | en_US |
Once you have deployed Acrobat using the package, you can uninstall it using the usual process for uninstalling msi packages. There are two MSI packages that are necessary to uninstall in a stand-alone package.
One for the Acrobat Pro MSI package and the second MSI package that the Creative Cloud Packager creates for licensing.
The Acrobat Pro MSI package is at the following path for Acrobat DC:
[CCPPackage]BuildSetupAPRO18.0[locale-set]AdobeAcrobatAcroPro.msi
Note:
It is recommended to run the package MSI in uninstall mode to remove the Acrobat license. However, if you have installed other apps on the machine that you still require, do not run the package MSI to uninstall DC, as it removes the license for other apps as well.
Silent Install Switches
Here is the command line syntax for uninstalling Acrobat:
Syntax Example:
msiexec.exe /x <path to Acrobat msi file> /qn
Here is the command line syntax for uninstalling the Creative Cloud Packager licensing package:
Syntax Example:
msiexec.exe /uninstall <path to the CCP msi file> /quiet
Adobe Acrobat Xi Silent Install
On the macOS, Acrobat is displayed as part of the product list for Creative Cloud Packager. After you include Acrobat from the list, Acrobat is included in the package file that is created.
Adobe Acrobat Silent Install Switches
Twitter™ and Facebook posts are not covered under the terms of Creative Commons.
Legal Notices | Online Privacy Policy