Adobe Acrobat Reader Setup Exe

• Acrobat Reader is the classic Adobe software that allows you to read and to print documents in PDF format. PDF files are ideal for several types of projects guarantees the protection of information of the source file, including text, drawings, image colour, photos, etc.
• Adobe Reader is used for viewing, printing, signing, sharing, and annotating PDFs. This article will serve as an informative guide and give you a clear understanding of how to perform a silent installation of Adobe Reader DC from the command line using both EXE & MSI installers.
• Command Line installation switches. I need to find command line swich installation options for Adobe Reader XI. I have tried the customization wizard, but I am not sure how to proceed with the MST file that is created.
• Adobe Reader Setup free download - Adobe Flash Player, Adobe Photoshop, Foxit Reader, and many more programs.

• Adobe Acrobat Reader Setup Exe Windows 10
• Adobe Acrobat Reader Setup Exe Installer

If your organization has purchased an Acrobat DC license via an ETLA (Enterprise Term License Agreement) or VIP program, you can download the installers from this page. To download the Acrobat installer, click the appropriate download link below. After the download is complete, follow the installation instructions below to begin the installation.

Work with Acrobat.com (beta) From Reader 9, you can go directly into Acrobat.com (beta), an exciting new set of online services from Adobe, to perform common tasks, such as:-Create up to five Adobe PDF files -Share and store documents on the web -Create and collaborate on a document in Adobe Buzzword-Easily share your screen using Adobe ConnectNow.

Note:

If you have already installed Acrobat, choose Help > Check For Updates, to update to the latest version. For more information, see Manually update Adobe Acrobat installation.

MSI support¶

Adobe Acrobat and Adobe Reader installers are developed using standard Windows Installer technology and Microsoft Installer (MSI) commands were developed by Microsoft.

The required MSI version for DC is 3.1 or higher.

MSI best practices¶

• When installing over an existing product, remove the old product first in a separate action.

• When scripting MSI actions, do not use RemoveExistingProducts after InstallFinalize. Doing so results in the installer updating files before removing the old application, and in the event of application removal failure, the installation may be incomplete.

• Do not use REINSTALLMODE=amus which forces all files to be reinstalled regardless of checksum or version. Such usage could result in a mixture of files from the old and new products. The recommended properties are vomus.

• Use TARGETDIR on the command line or the AIP user interface to specify an install location other than C: when creating an AIP.

MSI usage¶

Adobe has tested and supports the installation of Acrobat products using the command line. You can use command line methods to install software in many ways, such as typing commands at a command prompt or in a batch script. When using the bootstrapper, command line parameters can be sent to msiexec from within the Setup.ini as well as on the cmd line.

The syntax for msiexec is as follows:

• Windows Installer command-line options are not case-sensitive.

• Brackets ([]): Optional items

• Braces ({}); Set of choices separated by a | from which the user must choose only one. For example: {black|white}:

MSI switches¶

For Microsoft documentation, see http://msdn.microsoft.com/en-us/library/Aa367988.

MSI properties¶

You can specify MSI properties at install time; for example, to set a company name or suppress rebooting. For a complete list, refer to Microsoft documentation.

Supported MSI properties¶

Unsupported MSI properties¶

• SHORTFILENAMES is no longer supported. Microsoft has removed this property from the Windows 7 Logo Requirements.

Troubleshooting msiexec¶

When using msiexec, if you receive an 'Incorrect command line parameters' error message, verify that:

• Your syntax is correct.

• There is a space before the log file name if you use the syntax for writing a log file.

• You have not placed a /qn switch between the /i switch and the name of the MSI file.

Note

For more information about msiexec options, refer to http://technet.microsoft.com/en-us/library/cc759262(WS.10).aspx#BKMK_Install.

Bootstrapper installation¶

The bootstrapper Setup.exe file uses setup.ini as its configuration file. As you customize the installer with the Wizard, the Setup.ini file automatically updates. The Setup.exe file uses Setup.ini as it's configuration file. Before deployment, open Setup.ini, verify it contains all the properties you need, and edit it as neccessary.

Setup.ini contains two sections:

• [Startup]: Setup.exe first executes the Adobe flags for CmdLine. Do not place Adobe properties or MSI switches here; for example, you can use /sAll but not /qb!+ in this section.

• [Product] Setup.exe then reads the [Product] section. There may be multiple [Product] sections depending what the EXE should invoke (other MSI's or EXE's). The CmdLine should only contain values supported by the item the EXE invokes. For example, when invoking an MSI (msi=AcroPro.msi), you can only use space-separated Adobe properties (flag/value pairs connected by an = sign) and MSI switches; for example, you can use /qb!+ but not /sAll in this section.

MST usage in Setup.ini

Command line examples¶

These examples demonstrate different ways to install Acrobat products using the command line. Keep in mind the following:

• The examples use specific products and versions. Modify the command line to suit your environment, changing paths and file names as appropriate.

• It is possible to apply patches during an initial installation.

• For multilingual installers, use the selected language transform in the command line (for example, 1036.mst for the French language).

• Transforms in the installer media directory do not require fully qualified paths in the command.

• Patches do require fully qualified paths.

Note

As of July 2010, Reader update installers on the Reader Download Center for Tier 1 are chained by default. If you are downloading the product from the RDC rather than the download site, just download the latest file and you'll get all patches in one file.

Listing installed updates¶

Occasionally, certain bugs or features may be impacted by a specific OS version. You can use a Windows utility to list installed Windows udpates.

After installing the utility, run the following:

Installing Acrobat 2019 with logging¶

The silent install below creates an install log. Note that IGNOREVCRT64 can only be used when the C++ x64 Runtime is not required.

Language selection¶

You can use the LANG_LIST property to specify languages. Specify both the language code and the language-specific MST:

For details, see Adobe Properties

Creating an AIP¶

To create an administrative installation for a customized installer, use /a and TRANSFORMS. For example, the following installs Acrobat Pro with an MST file created with the Customization Wizard:

To create an administrative installation for a major release installer and a patch, use /a and /p. For example, the following installs Acrobat Pro 10.0 with the 10.1.0 patch:

Note

It's always a good idea to keep the files in the same directory and cd to that directory so that you can run the commands from there.

TRANSFORMS and .mst¶

Installer modifications created in the Customization Wizard are saved to an MST file. The MST must be referenced in the .ini file or on the command line. This example installs a customized version of Acrobat Professional, displays a basic user interface, and enables verbose logging.

Installing with an MST

LEIDs and post-install prtk usage¶

Once an ETLA serial is provided, the LEID changes for unserialized commands. For both tracks, it becomes V7{}AcrobatETLA-12-Win-GM (on Windows) and V7{}AcrobatETLA-12-Mac-GM (on Macintosh). For example, you would use the 'ESR' LEID version to initially serialize, and you would use the 'ETLA' version to deactivate or perform any other action with the prtk utility.

Silent uninstalls¶

A silent removal runs without any dialog boxes to show the user that the removal is running. All products use the same command line and the same installer file for silent updates:

Note

You must include the braces in the command line. An MSI package name (e.g. AcroRead.msi) can be substituted for the Product Code. For Acrobat products, the Product Code is the GUID.

Browser integration¶

Pass either ReaderBrowserIntegration or AcrobatBrowserIntegration to REMOVE when a product is already deployed and a subsequent deployment requires disabling browser integration. For example:

To re-enable Browser Integration, use ADDLOCAL:

Removing product features¶

Because Acrobat products support MSI technology, it is possible to the use the REMOVE property to uninstall any component as described in the Microsoft documentation: 'The value of the REMOVE property is a list of features delimited by commas that are to be removed. The features must be present in the Feature column of the Feature table. Note that if you use REMOVE=ALL on the command line, the installer removes all features having an install level greater than 0. In this case, the installer does not remove features having an install level of 0. For more information about the install level of features see http://msdn.microsoft.com/en-us/library/windows/desktop/aa371194%28v=vs.85%29.aspx.'

Removing any feature via REMOVE that is not specifically identified as a unique component in the user interface during a custom install is not supported. Moreover, some components have subcomponents which don't appear in the UI, and admins are advised to inspect the installer tables and test their installs prior to deployment.

The command line is in the form of:

Where is either the full path to the original MSI file or the ProductCode of this product.

APTEE example for DC products¶

For standalone Acrobat deployments which not part of a Creative Cloud packager install, download the Adobe Provisioning Toolkit Enterprise Edition (APTEE). Operation flashpoint red river crack only old. The APTEE is a platform-specific executable file:

DC Consumer track¶

For more details, refer to the PRTK documentation.

Note

As of July 2010, Reader update installers on the Reader Download Center for Tier 1 are chained by default. If you are downloading the product from the RDC rather than the download site, just download the latest file and you'll get all patches in one file.

Listing installed updates¶

Occasionally, certain bugs or features may be impacted by a specific OS version. You can use a Windows utility to list installed Windows udpates.

After installing the utility, run the following:

Installing Acrobat 2019 with logging¶

The silent install below creates an install log. Note that IGNOREVCRT64 can only be used when the C++ x64 Runtime is not required.

Language selection¶

You can use the LANG_LIST property to specify languages. Specify both the language code and the language-specific MST:

For details, see Adobe Properties

Creating an AIP¶

To create an administrative installation for a customized installer, use /a and TRANSFORMS. For example, the following installs Acrobat Pro with an MST file created with the Customization Wizard:

To create an administrative installation for a major release installer and a patch, use /a and /p. For example, the following installs Acrobat Pro 10.0 with the 10.1.0 patch:

Note

It's always a good idea to keep the files in the same directory and cd to that directory so that you can run the commands from there.

TRANSFORMS and .mst¶

Installer modifications created in the Customization Wizard are saved to an MST file. The MST must be referenced in the .ini file or on the command line. This example installs a customized version of Acrobat Professional, displays a basic user interface, and enables verbose logging.

Installing with an MST

LEIDs and post-install prtk usage¶

Once an ETLA serial is provided, the LEID changes for unserialized commands. For both tracks, it becomes V7{}AcrobatETLA-12-Win-GM (on Windows) and V7{}AcrobatETLA-12-Mac-GM (on Macintosh). For example, you would use the 'ESR' LEID version to initially serialize, and you would use the 'ETLA' version to deactivate or perform any other action with the prtk utility.

Silent uninstalls¶

A silent removal runs without any dialog boxes to show the user that the removal is running. All products use the same command line and the same installer file for silent updates:

Note

You must include the braces in the command line. An MSI package name (e.g. AcroRead.msi) can be substituted for the Product Code. For Acrobat products, the Product Code is the GUID.

Browser integration¶

Pass either ReaderBrowserIntegration or AcrobatBrowserIntegration to REMOVE when a product is already deployed and a subsequent deployment requires disabling browser integration. For example:

To re-enable Browser Integration, use ADDLOCAL:

Removing product features¶

Because Acrobat products support MSI technology, it is possible to the use the REMOVE property to uninstall any component as described in the Microsoft documentation: 'The value of the REMOVE property is a list of features delimited by commas that are to be removed. The features must be present in the Feature column of the Feature table. Note that if you use REMOVE=ALL on the command line, the installer removes all features having an install level greater than 0. In this case, the installer does not remove features having an install level of 0. For more information about the install level of features see http://msdn.microsoft.com/en-us/library/windows/desktop/aa371194%28v=vs.85%29.aspx.'

Removing any feature via REMOVE that is not specifically identified as a unique component in the user interface during a custom install is not supported. Moreover, some components have subcomponents which don't appear in the UI, and admins are advised to inspect the installer tables and test their installs prior to deployment.

The command line is in the form of:

Where is either the full path to the original MSI file or the ProductCode of this product.

APTEE example for DC products¶

For standalone Acrobat deployments which not part of a Creative Cloud packager install, download the Adobe Provisioning Toolkit Enterprise Edition (APTEE). Operation flashpoint red river crack only old. The APTEE is a platform-specific executable file:

DC Consumer track¶

For more details, refer to the PRTK documentation.

Serialization; machine online¶

Use following PRTK command to serialize Acrobat with ETLA serial number:

Un-serialization; ETLA serial license; machine online¶

Note

Once an ETLA serial is provided, the LEID changes for unserialized commands. For both tracks, it becomes V7{}AcrobatETLA-12-Win-GM (on Windows) and V7{}AcrobatETLA-12-Mac-GM (on Macintosh). For example, you would use the 'ESR' LEID version to initially serialize, and you would use the 'ETLA' version to deactivate or perform any other action with the prtk utility.

Type 1 Exception; machine offline¶

The command to generate request code for both Windows and Mac is:

Type1 Exception; machine offline¶

The command to get an accept request code for both Windows and Mac is:

Adobe Acrobat Reader Setup Exe Windows 10

Type 2 Exception; machine offline¶

On Windows and Mac, serialize Acrobat using the prov.xml as follows:

DC Classic track¶

Serialization; machine online¶

Use following PRTK command to serialize Acrobat with ETLA/Perpetual serial number:

Type 1 Exception; ; machine offline¶

Generate a request code with the following (both Win and Mac):

Type1 Exception; machine offline¶

Command to accept request code

Adobe Acrobat Reader Setup Exe Installer