Administrative installations via administrative install points (AIPs) create an uncompressed source so the application can be installed from a network location. AIPs allow you to create a canonical set of pre-configured files in one location that can be distributed across your organization from one location.
Updates and patches also often leverage administrative installations because they require uncompressed images of the installed product versions in order to compute file differences. These points also act as an archive of what you installed. Note that when an MSI is released for Reader, it is usually not accompanied by an MSP, so you should start over with a new AIP.
The following recommendations will help you successfully deploy updates and patches:
Do not create the AIP directly on the root drive (e.g. C:). Use TARGETDIR on the command line or the AIP user interface to specify a different install location.
If you previously deployed using an AIP, then you must apply the successive patches using an AIP.
Know when you can reuse AIPs and when you have to create a new one. For example, Acrobat 10.x and later quarterlies are cumulative and cannot be installed on top of each other.
11.x and later products do not require uninstalling existing products that were installed via an AIP. Update the product as described at http://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/gpo.html.
Verify that no one else is using the network share.
Copy and archive your AIPs both for future use and troubleshooting.
Always apply patches one-at-a-time.
Adhere to the required patching order.
- For Adobe Reader 10.x and later, quarterly updates are cumulative to the latest MSI (e.g. 10.1 replaces the base release of 10.0) and security patches are cumulative to the last quarterly. Thus, 10.0 > 10.1 is valid. 10.0 > 10.0.3 > 10.1 isn’t.
- MUI updates are different from localized Reader updates. A localized Reader AIP for 10.1.3 would follow require a patch order of 10.1.0 > 10.1.3 since 10.1.0 is the base release (last MSI) for a localized Reader) A MUI Reader AIP for 10.1.3 would require a patch order of 10.0.0 > 10.1.3 since 10.0.0 was the base release for MUI Reader.
When you have an existing product install that prevents an AIP update due to the order constraints, uninstall if first. For example, you could use
msiexec.exe /x <guid> <switches>. It must be a clean uninstall.
For Adobe Reader 8.x and 9.x, create a new AIP when the release provided only an MSI. While the MSI may uninstall the existing product, creating and deploying a new AIP does not ensure uninstallation of the existing product. Therefore, manual uninstallation and unlinking of the prior AIP is necessary.
The patterns below list the acceptable AIP patch patterns for Windows.
Acrobat pattern formula: Base release + latest quarterly + latest out of cycle patch)
Reader pattern formula: Last MSI + latest quarterly + latest out of cycle patch)
For earlier versions, see the following:
Administrative installation Points (AIP) lay out the installer according to the directory table in the MSI database. Because the Customization Wizard allows users to customize which files are installed, you should verify that any files that were included with the transform are laid out properly in the AIP directory structure.
To create and update an AIP:
Download the requisite installer. You’ll need to know the following:
- Language and locale IDs.
- Whether the installer is providing a quarterly update or an out-of-cycle patch.
- What is already installed on the target machines.
- A license number if installing Acrobat.
Backup the installer files (both the MSI and any needed MSP files) to a location where you will store the original downloads. For example,
Create a distribution point folder where machines can install the uncompressed program files (e.g.
\\<server>\Reader\AIP<version>\). The network share must provide authenticated users and Domain Computers with read access. This example calls the path
<AIP distribution point dir path>.
Copy the installer files you downloaded to <AIP distribution point dir path>.
Verify no one is using the share. If a file is in use, the new file version will not copied to the AIP.
Change directories to the AIP directory and run the commands from there.
At a command prompt, run:
msiexec /a <AIP distribution point dir path>\<ProductName>.msi TARGETDIR="<AIP distribution point dir path>"
msiexec /a <AIP distribution point dir path>\<ProductName>.msi
msiexec: Welcome screen
Do not install the AIP at the root directory such as C:or D:as that often results in errors. You can use the AIP UI to specify a different location. Alternatively, when using the command line with the
/qn switches, use the TARGETDIR property.
msiexec: Choose network location screen
AIP expanded server image
msiexec /a <AIP dir path>\<ProductName>11000.msi /p <AIP dir path>\<ProductName>11001.msp /p <AIP dir path>\<ProductName>11002.msp
/iswitch rather than
msiexec /i <AIP dir path>\<ProductName>.msi TRANSFORMS=<AIP dir path>\<ProductName>.mst
Quarterlies are cumulative to the last MSI (for MUI and non-MUI installers this is different), and patches are cumulative to the last quarterly. Use
msiexec.exe /x <product GUID> <switches> to uninstall versions which impair your ability to adhere to the installation. For a list of 7x, 8.x, and 9.x installers and acceptable patch orders, see http://helpx.adobe.com/acrobat/kb/update-patch-acrobat-reader-7.html.
Creating an AIP for any version should not be more than two steps process except when there is also an out of cycle (security) patch.
msiexec /a <Path to 10.0 AcroPro.msi> TARGETDIR="AIP_dir"
msiexec /a <AIP_dir\AcroPro.msi> /p <Path to Acrobat 10.x.x patch>
msiexec /a <Path to 10.0 AcroStd.msi> TARGETDIR="AIP_dir"
msiexec /a <AIP_dir\AcroStd.msi> /p <Path to Acrobat 10.x.x patch>
msiexec /a <AIP_dir\AcroStd.msi> /p <Path to Acrobat 10.x.y patch>
For Reader create an AIP from the latest available MSI. For example, as of September 13, 2011, you can start with 10.1 (a full MSI installer) rather than the 10.0 MSI.
msiexec /a <Path to 10.1 MSI> TARGETDIR="AIP_dir"
msiexec /a <AIP_dir\AcroRead.msi> /p <Path to Reader 10.1.1 patch>
MUI updates are different from localized Reader updates since the last released MSI is 10.0. Thus, a MUI Reader AIP for 10.1.3 would follow the path 10.0.0 > 10.1.3 since 10.0.0 was the base release for MUI Reader.
msiexec /a <Path to 10.0 MSI> TARGETDIR="AIP_dir"
msiexec /a <AIP_dir\AcroRead.msi> /p <Path to Reader 10.1.1 patch>
This information only applies to 9.x products and earlier and does not apply to 10.x and later products. Ideally, you will update in the required order and uninstall intermediate updates and patches as required to adhere to that order with
msiexec.exe /x <guid> <switches>.
When you can’t create a new AIP and start over and the last update was an out of cycle patch, you can update user machines with the following:
msiexec /i <path to the AIP's msi> REINSTALL=ALL REINSTALLMODE=vomus
The above command line updates user machines, not the AIP itself. At this point you’ve abandoned the use of AIPs for deployments. Future AIP usage will require uninstalling the product and starting over with a new AIP.
When you patch an AIP image, the Windows Installer performs a re-cache and reinstallation of the original product version, thereby replacing the previously cached MSI file and overwriting any old files with the newer version. By installing complete files the administrative update can correctly replace any modified files on the server.
Verify the following:
D:\as that often results in errors. You can use the AIP UI to specify a different location. Alternatively, when using the command line with the
/qnswitches, use the
Why does my AIP install result in an “Upgrade can’t be applied error”?
Patching of AIP is failing because you are trying to apply a quarterly update over an out of cycle security patch. To fix the problem:
Windows installer error
Why do I get an ``<license number>.error`` when installing Acrobat from my AIP?
Patching of AIP is failing because you may be trying to apply a quarterly update over an out of cycle security patch.
Why do I see a “another version is already installed” error?
Verify no previous product has been installed. If it has uninstall it. If you’ve already uninstalled, try Microsoft’s or Adobe’s cleaner tool.
This error can also appear if you are patching an AIP in an unsupported order.
Some related information might be found here: http://forums.adobe.com/message/4329735#4329735.
Can I cache installer files?
No. You cannot use the Wizard’s “Enable Caching of installer files” option or other methods to cache installer files for AIP installs. Actions like product repair, updates, etc. require AIP source files on the network and not the installer files.