I'm not quite understanding why you are *creating* a package to update Adobe Reader? Patch Manager automatically synchronizes the Adobe Reader v11 catalog, and Adobe publishes ready-to-use Reader updates based on their MSP.

In addition, Adobe also publishes a FULL installer which is packaged and made available via the Patch Manager catalog. The 11.0.09 package was published this morning.

As for why an MSP-based package is Not Applicable, that has nothing at all to do with the package being created, that's based on the detection logic build into the MSP file by Adobe. If the MSP returns a "Not Applicable" via the Windows Update Agent, then the target machine cannot be patched with that MSP.

Regarding your April 2013 thread... I do not believe you can PATCH an existing installation with an MSI+MST package, which is likely why those scenarios did not work. MSI+MST can only be used for a FRESH installation.

Perhaps we can chat about what you're trying to achieve with the transform and/or not using the provided ready-to-use packages from either Adobe, or SolarWinds?

Initially I wanted to create the update package as Adobe themself seemed to be quite slow in releasing the MSP update packages to their catalog (I had noticed in the past that sometimes it needs some days for the new updates to appear). But in this case Adobe is innocent: somehow the subscription for the Reader 11 catalog became deselected and (correct behavior) I only got the update packages for Reader 10.

Now I've got a working update package which gets recognized as needed . And I'm more confused then before, as I cannot see major differences between the two packages.

Both packages use the same MSP file. If the MSP is responsible for creating the needed rules I do not understand why one of theese packages wants to get deployed to thousands of computers and the other one not.

Is there any possibility to take a look at the included rules of a MSP?

Regarding the SHA1 Digest in the update summary: digest of what? While experimenting yesterday I created a few packages, some by scratch (the above one) some by duplicating an existing package and mofifying it. All packages use the same content (AdbeRdrUpd11009.msp) which shows up in the content tab with the SHA1 Digest 2kpt8b4xzBtIPznibiFAoJBNyAQ= but not all packages show this digest in the summary.

Regarding the provided full installer: this package gets installed even if there was no existing installation before. As I just want to update existing installations and it cannot be installed on all clients I don't use this package.

Regarding my "MST/MSI" last year problem: I'm quite happy with the solution/workaround as I've got a quite standarized installation base today. Hopefully the next big update will be the problem of someone else as our company is just in the outsourcing process for workplace management.

That's the SHA1 digest of the CAB file attached to the package as published to WSUS.

Regarding the provided full installer: this package gets installed even if there was no existing installation before. As I just want to update existing installations and it cannot be installed on all clients I don't use this package.

Excellent. That would be the intended scenario. As such, though, we're merely the "messenger" of the Adobe-created MSP and Adobe-created catalog/package, so any issues with how the MSP behaves are really questions for Adobe.

Actions

More Like This

Retrieving data ...

SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining.

SolarWinds uses cookies on its websites to make your online experience easier and better. By using our website,
you consent to our use of cookies. For more information on cookies, see our cookie policy.