Adobe Acrobat Reader 9 5 Offline Installer

• Adobe Acrobat 9.5.5 Download
• Adobe Acrobat 9.5 Free Download

MSI support¶

This method presents a way to install Adobe Acrobat 9.5.1 straight through GPO. First we need to create a few folders on our local computer as we will be running some CMD prompt commands therefore; it is easier installing on the root of C. Adobe Reader 9 software is the global standard for electronic document sharing. It is the only PDF file viewer that can open and interact with all PDF documents. Use Adobe Reader to view, search, digitally sign, verify, print, and collaborate on Adobe PDF files.

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). The APTEE is a platform-specific executable file:

Adobe Acrobat 9.5.5 Download

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:

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

This method presents a way to install Adobe Acrobat 9.5.1 straight through GPO.

First we need to create a few folders on our local computer as we will be running some CMD prompt commands therefore; it is easier installing on the root of C:

(you can use less folders I'm just keeping it easy to follow)

C:AIP (Our Administrative Install point)

C:Acrobat (Copy of CD D:Acrobat9 folder)

C:AcrobatDownloads (Downloads folder)

C:AcrobatTransform (our finalised server version)

Secondly, we need to download all the Patches and the Adobe Acrobat 9 Customisation Wizard which enables us to add the serial, suppress EULA's and so forth.

Download all patches and place them in 'C:AcrobatDownloads'

Adobe Acrobat 9 Customisation Wizard (4.5MB)

Download and install (Don't worry about this until later)

9.1 (119.7MB) – Choose your language/Version

Acrobat Pro Extended Multiple Languages (122.5MB) - AcroProExUpd910_all_incr.msp

Acrobat T1T2 (103MB) - AcroProStdUpd910_T1T2_incr.msp

This is a multilingual update for Brazilian Portuguese, Danish, Dutch, English, Finnish, French, German, Italian, Japanese, Norwegian, Spanish, and Swedish

Acrobat T3T4 (126.7MB) – AcroProStdUpd910_T3T4_incr.msp

This is a multilingual update for Bulgarian, Chinese Simplified, Chinese Traditional, Croatian, Czech, Estonian, Hungarian, Korean, Latvian, Lithuanian, Polish, Romanian, Russian, Slovak, Slovenian, Turkish, and Ukrainian

9.1.2 (35.45MB) - AcrobatUpd912_all_incr.msp

9.2 (161.48MB) - AcrobatUpd920_all_incr.msp

9.3 (174MB) - AcrobatUpd930_all_incr.msp

9.3.2 (88.5MB) - AcrobatUpd932_all_incr.msp

9.3.3 (89.48MB) - AcrobatUpd933_all_incr.msp

9.4 (91.69MB) - AcrobatUpd940_all_incr.msp

9.4.2 (80.5MB) - AcrobatUpd942_all_incr.msp

9.4.5 (66.9MB) - AcrobatUpd945_all_incr.msp

9.4.6 (52.5MB) - AcrobatUpd946_all_incr.msp

9.5 (205MB) - AcrobatUpd950_all_incr.msp

9.5.1 (92.4MB) - AcrobatUpd951_all_incr.msp

Creating the Administrative Install Point

1. Copy the contents of the folder from 'DVD drive:Acrobat9' to 'C:Acrobat'

2. Strip out any patches that are in the folder 'C:Acrobat' just in case of issues later (anything ending in *.msp)

3. Create 'aip.bat' file and put all your patches in. You can take the pauses out; I wanted a more hands on installation. Save the ‘aip.bat' file to 'C:Acrobat'

msiexec /a C:AcrobatacroPro.msi
pause
msiexec /a C:AIPacroPro.msi /p C:AcrobatDownloadsWhichever 910 You Use.msp
pause
msiexec /a C:AIPacroPro.msi /p C:AcrobatDownloadsAcrobatUpd912_all_incr.msp
pause
msiexec /a C:AIPacroPro.msi /p C:AcrobatDownloadsAcrobatUpd920_all_incr.msp
pause
msiexec /a C:AIPacroPro.msi /p C:AcrobatDownloadsAcrobatUpd930_all_incr.msp
pause
msiexec /a C:AIPacroPro.msi /p C:AcrobatDownloadsAcrobatUpd932_all_incr.msp
pause
msiexec /a C:AIPacroPro.msi /p C:AcrobatDownloadsAcrobatUpd933_all_incr.msp
pause
msiexec /a C:AIPacroPro.msi /p C:AcrobatDownloadsAcrobatUpd940_all_incr.msp
pause
msiexec /a C:AIPacroPro.msi /p C:AcrobatDownloadsAcrobatUpd942_all_incr.msp
pause
msiexec /a C:AIPacroPro.msi /p C:AcrobatDownloadsAcrobatUpd945_all_incr.msp
pause
msiexec /a C:AIPacroPro.msi /p C:AcrobatDownloadsAcrobatUpd946_all_incr.msp
pause
msiexec /a C:AIPacroPro.msi /p C:AcrobatDownloadsAcrobatUpd950_all_incr.msp
pause
msiexec /a C:AIPacroPro.msi /p C:AcrobatDownloadsAcrobatUpd951_all_incr.msp
pause

4. Run the ‘aip.bat' file with administrative rights, follow the dialogues, installing Acrobat and successive patches to 'C:AIP'. This patches the actual ‘AcroPro.msi' creating a new one with each new patch applied, sadly, you do end up with having four folders and an .msi. It's just how it is.

5. After this has completed either copy ‘setup.ini' from ‘C:Acrobat' to ‘C:AIP' and strip out the line under the heading [Product] 'PATCH=….'

OR create a text file and save in C:AIP as ‘setup.ini':

[Startup]
RequireOS=Windows XP
RequireMSI=3.0
RequireIE=6.0.2600.0

[Product]
msi=AcroPro.msi
Languages=1033;1031;1036
1033=English (United States)
1031=German (Germany)
1036=French (France)

[Windows XP]
PlatformID=2
MajorVersion=5
MinorVersion=1
ServicePackMajor=2

[MSI Updater]
Path=WindowsInstaller-KB893803-v2-x86.exe

6. Open Adobe Customisation Wizard 9

7. File – Copy Package

8. In the pop up dialogue

The existing source package is located at: ‘C:AIPacropro.msi'

Specify a Name for your package I went with ‘AcroPro'

Where it is to be copied to: C:AcrobatTransform

Adobe Acrobat 9.5 Free Download

9. Click OK and wait for it to copy.

10. Go through the Left hand panel enter in the personalisation you want including serial number, whether you want to disable looking for updates, silent installation and suppressed rebooting, EULA e.t.c

11. Once done Click File – Save Package.

This will have generated AcroPro.mst and updated your setup.ini file to enable silent install and more if selected. Close the Customisation Wizard. You can come back to your package at any time by opening up ‘AcroPro.msi' under C:AcrobatTransformyourNameOfPackage make your edits and save again.

12. Copy the ‘yourNameOfPackage' folder from C:AcrobatTransform to your server share

13. Open up Group Policy Management MMC

14. Go to the Organisational Unit that you are wanting to apply software to

15. Right click on the OU and select ‘Create a GPO in this Domain, and link it here…'

16. Write your GPO name mine was 'Software – Acrobat 9.5.1' Click OK

17. Right Click on GPO, Click Edit

18. Drill down 'Computer Configuration – Policies – Software Settings – Software Installations'

19. Right click 'Software Installations'

20. Click ‘New – Package'

21. Browse to your server share of ‘yourNameOfPackage' Click Open

22. Select Deployment Method: Advanced Restart mac with keyboard.

> Under General Tab - Change the name if you want to

> Under Deployment Tab – Change whether you want the application to uninstall off computers when you remove the GPO

> Under Upgrades Tab - You can choose GPO's which this can upgrade over. For example older versions of Acrobat and also gives you the ability to either uninstall then install the new product or just do an upgrade.

23. Click Modifications Tab

24. Click Add…

25. Browse to your ‘yourNameOfPackage' folder on the server share and select your ‘yourNameOf.MST' file.

26. Click Open

27. Click Ok

28. Exit out of Group Policy Management, restart the computers and enjoy!