Acrobat Reader Auto-Update Not Updating Consistently Across Domain

[AOP5E90]

AFAIK, Adobe Reader automatically downloads and installs updates in a truly seamless manner - In theory, a zero-touch approach for administrators. It does this by creating a Windows scheduled task upon installation, called "Adobe Acrobat Update Task". It runs the task under the user's context (INTERACTIVE), and executes "C:\Program Files (x86)\Common Files\Adobe\ARM\1.0\AdobeARM.exe" at user logon, and at 7am each day if the device is connected to AC Power.

For the largest part of our devices it does nothing, we now have different Versions in our Domain.
23.001.20064 - latest verion
22.003.20322

How can I ensure that the Adobe Reader update is updated via the Adobe ARM service?

Even if i delete the tLastReader Registry Keys and start the task manually, Adobe Reader doesn't update.

Thank you for your help.

[S. S]

Hi @AOP5E90,

Hope you are doing well. Sorry for your experience with updating Acrobat Reader.

What I'd suggest is to install Adobe Remote Update Manager. Once you have deployed the Adobe apps on client machines, you want the subsequent updates for the packages to be available on the client machines. You can create and deploy an update package manually on the client machines.

Instead of deploying the updates manually, you can use RUM. It polls the Adobe Update server or the local Adobe Update Server if set up using the Adobe Update Server Setup Tool (AUSST). RUM deploys the latest updates available on the update server to each client machine it runs. You need not manually push updates to the client machines.

When creating a package from the Admin Console, the default setting is to have the Adobe updates turned off. Most enterprise environments do not provide their end users with admin privileges. With the updates turned off, the end users will not see the availability of updates; nor could they apply them if downloaded. RUM can apply those updates remotely even if updates have been disabled through the Options screen in the package creation workflow.

Once you have installed RUM on each client machine, you can run it remotely through the command line or remote management tools.

You can learn more: Use Adobe Remote Update Manager

Hope this helps.

-Souvik

[AOP5E90]

For my understanding and what i was reading in the adobe documentation is that Adobe Remote Update Manger isn't capable to do upgrades.

So 22.1 --> 22.2 yes and but not 22.1 --> 23.1

From the site you linked: "Remote Update Manager only detects updates but not upgrades"

[LeoUpdaterX]

One way to find out why some of the products are not updated is to provide Updater verbose log file.

To enable Updater verbose logging-

Set iLogLevel REG_DWORD value to 1 in the registry below

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Adobe\Adobe ARM\1.0\ARM on 64 bit OS

HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe ARM\1.0\ARM on 32 bit OS

Repeat "delete the tLastT_Reader Registry value in HKCU and start the task manually" on the system where Reader is not updated.

Collect and send me in the private message AdobeARM.log file from current User Temp folder.

[AOP5E90]

Thank you, will try this on Monday.

[AOP5E90]

Just sent you the PM with the logfile.

Thank you.

[peter29183489l8ym]

We had the same experience with exactly these versions. The version released on the 22nd March started to kick in finally slowly and I have a hope that next week most machines that remained on the February release will step up to the latest version. I can try to make a verbose logging on some machines on Monday but until, were there any results worth sharing for the above case? Mainly I see the 120300 message stating that the last check has not expired, but that sounds weird for a month.

Thanks!

[LeoUpdaterX]

Peter, latest updates were initially released to approximately 35% of the available users and currently enabled for all 100% of the available users, but check for updates is on 3 days interval. Wait a few days and you should see all systems updated.

[peter29183489l8ym]

Hi!

This is great information, many thanks for that.

Is this a generic practice or specific to this update? Is there maybe a documentation about this phased deployment?

Were there any administrative reasons for why the 23.001.2006x from the beginning of March was barely installed on top of our 22.003.20314 February versions (eg. Not applicable) or thats something to understand from the logs?

Many thanks!

[S. S]

Hi @peter29183489l8ym,

For this specific update, it was rolled out first at 35 % and now is rolled out to the entire user base.

We might want to check if the update is available for your system.

-Souvik

[peter29183489l8ym]

Hi!

This is great information, many thanks for that.
Is this a generic practice or specific to this update? Is there maybe a
documentation about this phased deployment?

Were there any administrative reasons for why the 23.001.2006x from the
beginning of March was barely installed on top of our 22.003.20314 February
versions (eg. Not applicable) or thats something to understand from the
logs?

Many thanks!

[AOP5E90]

Thank you, Adobe Reader is now updating on the clients. Looking fine now and the amount of updated clients growing every day.

[S. S]

@peter29183489l8ym Let me check this internally, and I will get back to you.

-Souvik

[S. S]

@peter29183489l8ym Our team will be working on getting indications about phased roll-outs in place on the helpx sites for better visibility from future updates.

Meanwhile, here are a few pointers shared:

1. Some releases with release type “Continuous” (details) have an extended update cycle and are rolled out to the eligible population gradually.
2. Users could always go to “Help -> Check for Updates” in the application to get to the latest version.
3. We will work on adding some indication on the release notes page for such releases.

Hope this helps.

-Souvik