How to Deploy Acrobat DC MSP Updates Without the AcroPro.msi Prompt
Question details
The user needs to silently deploy customized Adobe Acrobat DC Pro updates (MSP) via tools like KACE without the installer pausing to ask for the original AcroPro.msi file.
- Product
- Adobe Acrobat DC Pro
- Device & OS
- Windows
- Scenario
- Using enterprise software deployment tools (such as KACE) to silently push software patches to multiple client computers.
- Observed behavior
- The MSP update installer pauses during deployment and prompts the end user to provide the directory path to the original AcroPro.msi installation file, preventing silent automation.
Ensure you have the exact AcroPro.msi file used for the initial installation and the latest applicable MSP update file stored in the same local deployment directory before configuring your deployment tool.
Use Windows Installer with a Cached MSI Package
Bundle the original MSI and the new MSP file in your deployment package to provide the required source automatically, allowing the update to complete silently.
When applying an MSP patch, the Windows Installer service often needs to read the original MSI file to verify existing components. By including the MSI in your deployment package alongside the update, you satisfy this requirement without relying on network shares.
Create a deployment package in your management tool (like KACE) that contains both the original Acrobat installation source (AcroPro.msi) and the applicable MSP update file.
Set your deployment script to execute the update using the Windows Installer command line. Use the syntax: msiexec /p [Path_To_MSP] /a [Path_To_MSI] to reference the original MSI as the cached installation source.
Append the /quiet or /qn parameters to your command string to ensure the update installs completely silently without showing any UI or prompts to the end user.
Run the exact command locally on a single test machine using a command prompt with administrative privileges. Once verified, deploy the package through KACE.
Create and Deploy an Administrative Installation Point (AIP)
Pre-patch the installation source on a network location or package it locally, then deploy the already-updated software.
Switch to WPS Office for Simplified IT Deployment and PDF Management
Struggling with complex software updates, missing MSI prompts, and heavy deployments? WPS Office offers a lightweight, all-in-one productivity suite featuring a powerful built-in PDF editor. It streamlines enterprise deployment with smaller package sizes and straightforward installation processes, all while maintaining excellent compatibility with major document formats.
Frequently Asked Questions
Why does my Acrobat deployment fail and prompt for AcroPro.msi?
The Windows Installer requires the original installation source (AcroPro.msi) to verify previously installed components before applying a patch (MSP). If the original source is no longer cached locally on the machine, the installer halts and prompts the user to locate it.
How do I perform a completely silent Adobe MSP installation?
You can perform a silent installation by utilizing standard Windows Installer switches. Add the '/qn' or '/quiet' parameter to your msiexec command line to suppress all user interfaces and prompts during the update.
Is it possible to deploy Acrobat updates without using a centralized network share?
Yes. By using deployment tools like KACE, you can bundle both the original AcroPro.msi and the MSP update file together in a local package. The deployment script will then execute the files directly from the local machine's cache rather than relying on an active network drive.
