Adobe RUM Exit code 0

[ahsen_EUC]

Hi Members, 

I am using RUM to update all Adobe applications on the client machines.

A package is created and deployed onto the client machines to run RUM with --action=install argument, which returns the exit code 0, indicating that all apps are up to date; however, when I check the version of the apps, they are still on older versions. 

Any guidance would be much appreciated. thank you 

[Meenakshi Negi]

Hi ahsen_EUC,

Thank you for reaching out.

Please let us know the version number that is currently installed. Also, let us know if all the Adobe applications are installed with the old version or just the Acrobat.

Share more information so we can check.

Thanks,

Meenakshi  

[LeoUpdaterX]

RUM launches ARM to perform update related tasks. To get help with this issue you will have to provide verbose ARM files.

1. enable verbose logging - set iLogLevel DWORD value to 1 in HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Adobe\Adobe ARM\1.0\ARM

2. Run RUM

3. Collect AdobeARM.log files from User Temp and Windows Temp folders

4. Upload these files somewhere so I can take a look

[AnandSri]

Hello!

I hope you are doing well.

As highlighted by our community expert, please share the Verbose Logging and share it with us. Meanwhile you may try the following suggestions, and let us know how it goes:

Ensure Latest Updates Are Available on the Update Server: RUM only installs updates that are available through the Adobe Update Server or your internal Adobe Update Server Setup (AUSST), if you're using it. Make sure: The update packages are already downloaded and available. If using AUSST, sync it with Adobe’s servers regularly: https://adobe.ly/43XogKX

Check if Apps Were Installed via Packages That Disable Updates: If the applications were deployed using packages with updates disabled, RUM won't apply updates. Recheck the package settings in the Admin Console to ensure the apps: Allow updates via RUM. Were installed from packages that support managed updates.

Use the Correct RUM Syntax: Make sure you're calling RUM with the full path and correct syntax. Example: RemoteUpdateManager --action=install

Also, run RUM with administrator privileges to ensure it can perform installations.

Verify the RUM Log File: Check the log file generated by RUM, located at: C:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp\RUM\RemoteUpdateManager.log

It provides detailed information about which updates were attempted or skipped, and why.

For more information, you can see these articles: Use the Adobe Remote Update Manager (RUM)

Packaging apps via the Admin Console

I hope this helps. I will also move the conversation to the Enterprise support team so that the experts can add and share more information on this.

Thanks,

Anand Sri.