Issue with deploying Adobe Reader/Pro

[SMR1]

We deploy our updates monthly and use autopkgr or installomator to install the updates. It seems we always have issues with Adobe Products updating. There is always a handful of devices that it fails to install on. I was using a script to check it was open and then close it and that seemed to help a little. These devices are getting other 3rd party updates just fine.  When I go to the policy log, it shows the below.

Executing Policy Update Adobe Acrobat


Downloading Adobe Acrobat DC-24.005.20320.pkg...

Downloading 
https://xxx.jamfcloud.com/jcds/downloads/Adobe%20Acrobat%20DC-24.005.20320.pkg...


Verifying package integrity...

Installing Adobe Acrobat DC-24.005.20320.pkg...

Installation failed. The installer reported: installer: Package name is Adobe Acrobat (24.005.20320)
installer: Upgrading at base path / installer: The upgrade failed. (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance. An error occurred while running scripts from the package “Adobe Acrobat DC-24.005.20320.pkg”.)

[kylie575]

Hello,

It seems you're experiencing issues with updating Adobe products via autopkgr or Installomator on a small subset of devices. The fact that other third-party updates install without issue points to Adobe-specific factors, such as:

Application Running: If the Adobe app is running during the update, it can cause the installation to fail.
Corrupted Installations: Pre-existing issues with Adobe installations on some devices may cause updates to fail.
Permissions or File Locking: Some files or folders used by Adobe apps might be locked or have restrictive permissions.
Framework Dependencies: Adobe updates often require specific system libraries or frameworks, which might not be fully compatible or present.
Suggestions for Troubleshooting & Resolution:
1. Verify Policy Log Errors
Please share the specific error details from the policy log. Common errors (e.g., "file locked," "install failed," etc.) can help pinpoint the problem. Without specific logs, here are general fixes:

Best Regards