How to Deploy Adobe Acrobat Reader Through SCCM Using MSI
Question details
The user needs to successfully deploy Adobe Acrobat Reader through Microsoft SCCM using an MSI installer and resolve potential deployment failures.

- Product
- Adobe Acrobat Reader, Microsoft SCCM
- Device & OS
- Windows
- Scenario
- Enterprise software deployment and endpoint management
- Observed behavior
- Deployments frequently fail due to incorrect MSI command-line parameters, lack of administrative permissions, faulty detection rules, or missing transforms.
Ensure you have downloaded the official Adobe Reader Enterprise installer and possess administrative privileges within your Microsoft SCCM environment.
Configure SCCM for Adobe Acrobat Reader MSI Deployment
Verify your deployment packages, installation commands, and system parameters to ensure a successful, silent MSI rollout.
Deploying Adobe Reader in an enterprise environment requires careful configuration of the MSI package. Using the correct command switches and transform files (.mst) ensures the installation proceeds silently without user interruption.
Download the enterprise installer from Adobe. If it is an EXE, extract the contents to obtain the base MSI file (e.g., AcroRead.msi) and the associated setup files.
Use the Adobe Customization Wizard to tailor the installation. Disable the EULA prompt, set default PDF handlers, and save the configuration as a .mst file.
In the SCCM Console, create a new application and specify the extracted MSI file. Allow SCCM to import the standard MSI deployment parameters automatically.
Edit the deployment type programs. Ensure the installation command uses silent switches and includes your transform file, for example: msiexec /i "AcroRead.msi" TRANSFORMS="custom.mst" /qn.
Define an accurate detection method in SCCM, such as verifying the Windows Registry Product Code for the specific Adobe Reader version, to confirm the software installed correctly.
Distribute the package to a small test collection of representative client machines. Monitor the deployment logs (AppEnforce.log) to ensure it installs successfully before a broader rollout.

Deploy WPS Office as a Lightweight Enterprise Alternative
Struggling with complex deployments and high subscription costs? WPS Office offers a powerful, lightweight alternative with an integrated PDF reader and editor. It provides straightforward enterprise deployment capabilities via MSI while maintaining seamless compatibility with all Microsoft Office and standard PDF formats.
- 1. Download the Enterprise Installer: Obtain the lightweight MSI installer package for WPS Office from the official enterprise portal.
- 2. Add to SCCM: Create a new application in SCCM using the WPS Office MSI. The standard properties and detection rules are easily configured.
- 3. Deploy Silently: Use standard MSI silent install switches (e.g., /qn) to rapidly deploy the office and PDF suite across your organization's endpoints.

Frequently Asked Questions
Why does my Adobe Reader SCCM deployment fail with error 1603?
Error 1603 is a generic MSI fatal error. In SCCM deployments, it usually indicates insufficient administrative permissions, conflicts with an older installation that failed to uninstall, or a corrupted MSI/MST package. Checking the client's AppEnforce.log will provide more details.
How do I suppress the Adobe EULA prompt during SCCM deployment?
To suppress the EULA, you must use the Adobe Customization Wizard to create a transform (.mst) file. Within the wizard, select the option to silently accept the EULA on behalf of the user, then include this transform file in your SCCM installation command.
What is the best detection method for Adobe Reader updates in SCCM?
Instead of relying solely on MSI product codes which can change with minor patches, it is highly recommended to use a File System detection rule checking the version of the AcroRd32.exe or Acrobat.exe file in the installation directory.




