Adobe Reader and SCUP

[powerful_Zephyr6C29]

I am in process of implementing SCUP into our SCCM 2012 R2 SP1 environment.  Currently, I have Adobe Reader updates imported and deploying, etc., however, I am seeing some weird behavior in which updates machines are reporting under required, not required, etc.

Our current base install version of reader is 11.0.10, which we have patched to 11.0.11 currently.  In my reader updates deployment, I have 11.0.2 through 11.0.14 (the latter being the goal version to get the enterprise onto), however machines only report 11.0.2, 11.0.05, and 11.0.08 as required updates, which will install and appear to roll back our current 11.0.11 versions.  I have a case open with Microsoft, and the engineer I am working with did note that they have limited information on the Adobe content, however, they do have notes that show that 11.0.02, 11.0.05, and 11.0.08 are considered "out of band" from normal quarterly updates.  All other updates, including the 11.0.14 update are showing as "not required" for 98% of our enterprise - I am wondering if anyone can clue me in as to why.

Thanks,

Sean Huggans

[EnterpriseHelp]

You only need the latest planned update as updates are cumulative. List is here: http://www.adobe.com/devnet-docs/acrobatetk/tools/ReleaseNotes/index.html.

11.0.14 is the latest. What is saying it is not required? Can you send a screenshot?

Ben

[powerful_Zephyr6C29]

I am curious about the evaluation logic that is occurring - as most machines fall into the "not required" category here - however, all machines in the "not required" category have reader 11.0.11 installed, however updates 11.0.02, 11.0.05, and 11.0.08 are the only ones that show up as required for the majority of our enterprise, yet these are older than version 11.0.11 which is what we have on the machines where they show as required?

[MaceUK]

Im experiencing the same issue....

Our estate is mainly 11.0.10, yet i get the details below...

I even sync'd today to get 11.0.15 and although shows up in SCCM updates, doesnt really deploy. The same with all of those listed. In my software center i have nothing available for me. The advertisement has been setup and data on all DP's.

[powerful_Zephyr6C29]

I have a response in a PM from an Adobe employee who is having an engineer look into this. I will keep you posted.

[MaceUK]

thanks, really appreciated

[m2cv]

It looks like the update was not published to the ftp site until just a few minutes ago. I hope this means the download link in SCUP will be functional soon too.

EDIT: Download in SCUP works for me now! Thanks Adobe staff!

[powerful_Zephyr6C29]

I think you are referring to a separate issue - We are able to see all the updates in the catalog and import them into sccm updates.  The issue is whatever evaluation logic that determines the applicability of these updates for whatever reason is not working.

Issue still present.

[MaceUK]

Spot on huggans.sean. We still have the issue.

[MohdKashif · Accepted solution]

We looked at the scripts shared to us privately by Sean and it seems that Reader was deployed via a patched AIP in his organization.

Please refer to MS documentation at https://msdn.microsoft.com/en-us/library/windows/desktop/bb204770(v=vs.85).aspx.

Under section “Avoid patching administrative installations.” Where it says:

“Many binary patches target the RTM image of the application and require a previous file version. The local instance of an application installed from an updated administrative installation may not work with other updates. Many binary patch applications can fail.”

Quarterly Patches for Adobe Reader XI target RTM and hence they won’t install on a machine where deployment has been done via patched AIP . You can also refer to the “Best Practices” section at https://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/aip.html where it says “If you previously deployed using an AIP, then you must apply the successive patches using an AIP”.

Due to the above cited reasons SCUP catalogs won’t be able to update these machines that have patched AIP deployments.

Our recommendation is that you deploy via SCCM and then you can patch it via SCUP. Or if there is a strong enough reason to go with AIP deployments then you must push all further patched through AIP only.