Adobe Reader and Acrobat Pro updates for 11.0.10 being pushed out through SolarWinds Patch Manager are not being recognized as applicable.

Report · Dec 12, 2014

I am trying to update our Adobe Reader and Acrobat Pro to 11.0.10 using the default MSP packages with SolarWinds Patch Manager. All of the systems keep reporting as 'NOT APPLICABLE'. All of the workstations have Reader11.0.09, with about 10% still on 11.0.08 (due to the fact that the reader 11.0.09 package only patched about 2/3 of the systems). All systems that have Acrobat Pro are 11.0.09.

In SolarWinds I am using the "Adobe Systems, Inc. Packages" node.

Adobe Systems Acrobat 11 Catalog
Adobe Systems Reader 11 Catalog

and the SW Patch Manager downloads the msp's straight from Adobe.

I have checked the msp's manually and they will update at least back to 11.0.07 in Reader, and 11.0.0 in Acrobat Pro. (I had an old stand alone system that still had Reader 11.0.07, and I did a new install of Pro and went straight to update 11.0.10)

The SolarWinds Tech said, "Okay. That content is produced by Adobe. Any questions concerning applicability logic or diagnosing why a package reports as NotApplicable when that's not expected would need to be directed to Adobe, as they are solely responsible for that content and its behavior".
I am new to SolarWinds Patch Manager, and any help or advice would be greatly appreciated.

Report · Dec 14, 2014

Moved to Enterprise Deployment (Acrobat and Reader)

Report · Dec 15, 2014

It sounds like you are attempting to use the SCUP catalogs outside of the MS solution. I can almost guarantee you that Adobe didn't test it if it's not referenced in the ETK: 11 SCCM-SCUP — Enterprise Administration Guide

That being said there "should" be logging available in any deployment solution. Since I am not familiar with Solar-Winds particular solution I can't say if it logs errors and how verbose those logs might be. If you have logs then post the output and the forum members "might" be able to assist you.

Report · Dec 15, 2014

It is not showing any errors. It is just not seeing that there is anything to update. SolarWinds and Adobe have an agreement. The "Adobe Systems, Inc. Packages" node is a set of catalogs, for Reader and Acrobat STD & Pro, that are distributed to SolarWinds Patch Manager straight from Adobe. SW PM then uses WSUS to push them out to the Enterprise.

Report · Dec 15, 2014

Your deployment method is not supported. However, as Sabian mentions, that doesn't mean it might not work. Follow his suggestion and post verbose logs.

Ben

Report · Feb 11, 2015

I am having the same problem. However I am using System Center Updates Publisher 2011 (version 5.00.1727.0000). When I publish the update into WSUS it is successful however the update appears in WSUS with a Status = Failed. I can clear this up using PowerShell to ResumeDownload() on the update. After that the status changes to Ready but none of my systems detect the update as required. I suspect that there is something wrong with the update in "WSUS Generated MSP Installable Rule".