Hi Everyone, Im having an issue with installing acrobat 10.1.3 update on my client machines. This is what I have noticed:
1) If Acrobat is the base version 10.0.0 i can update to 10.1.3 without any other patches installed.
2) If Acrobat is any other version (eg: 10.1.0 or 10.1.1) it will update to 10.1.2 but will not update to 10.1.3. (windows reports as no updates needed) and WSUS reports and not applicable.
Has anyone else had this issue or can someone point me in the right direction? Please be aware I have just started using the patch manager software...so far so good!
As has been the case since Reader v9.4, Adobe Reader updates are applicable only to the current version. The Reader 10.1.3 update applies only to Reader 10.1.x systems.
We have not yet observed the behavior that you describe in #2, but that's certainly possible. The Adode Reader 10.1.3 update package from the Adobe Systems Inc, Packages node is a product of Adobe, and issues with the behavior of that package should be brought to the attention of Adobe. There were similar defects in the Reader 10.1.2 package, so I'm not particularly surprised by this.
It may also be that the 10.1.3 package is purely incremental and will only install to a 10.1.2 system. What is the status of the 10.1.3 update package on machines with 10.1.2 installed?
As an alternative, you can use the Adobe Reader 10.1.3 Full Installation package available in the SolarWinds catalog. You'll find this in the Adobe Packages node of your console. In addition to working properly (we have tested it), it can also be used to upgrade any of your Reader X installations.
Hi Lawrenc,
Thank your for your speedy reply! Apologies I did not make it clear that I was talking about adobe Acrobat X Pro...not Reader. However im assuming what you said above can be applied to Acrobat Pro as well?
I tried updating Acrobat Pro from 10.1.2 to 10.1.3 but the update was stated as not applicable. I was only able to get version 10.0.0 to update to 10.1.3 ...any other version of Acrobat Pro will not update to 10.1.3.
Please note that I am using the packages found in the Adobe Systems inc node.
Thank you for the clarification Matthew.
For Adobe Acrobat X updates, that content is exclusively Adobe's, and any (mis)behaviors in that content should be discussed directly with Adobe. Patch Manager is merely the "messenger" with respect to that content (as well as HP or Dell content).
Hi Lawrence,
Thanks for your help. ill get in contact with Adobe.
On another Adobe related pronlem im having. I have published the latest version of Flash...but it keeps showing up as an avaliable update even after installing it. Wsus/Patch manager reports it as installe on that particualr machine. Any ideas?
Is this a Flash update from the SolarWinds catalog? If so, specifically which package?
Yes it is.
package: 11.2.202.233 Plugin MSI (32bit)
I have tried removing flash from the target machine then updating via wsus. It still produces the same behaviour.
I will investigate with our internal packaging and testing resources. Please give me 12 hours to get you some feedback as it is now 9pm in the U.S.
No problem at all.
Thank you very much for your prompt replies!
We are not able to reproduce any undesirable behaviors with that package.
Please note that both the x64 and x86 packages will report as applicable and installable on an x64 system, and, of course, there are also ActiveX and Plugin updates, so four potential updates would report as available for an x64 system.
Also, sometimes this behavior is the result of an installation failure. Reviewing entries in Programs and Features and/or enabling MSI logging to confirm the installation was successful can sometimes shed light. There is a disconnect, though, between an update "showing up as an available update", and being reported as "Installed" in the WSUS console.
If the above is not helpful in identifying the nature of the issue, I would suggest opening a support case via the SolarWinds Customer Portal.
Thank you very much for your time. It seems that my issues with Acrobat Pro have been solved after I synced the packages.
