Acrobat 10.1.0

[Juanca]

Hello everyone!

I seem to be having troubles applying updates to Acrobat X.
So far, neither 10.0.1, 2, 3, nor 10.1.0 are being recognized when
clients check for updates (so I don't really have any useful log info
from the clients log file).
I feel I might be missing something very simple, but can't seem to get
what it is.

As a side note, in this case, Acrobat X is being installed as part of
CS5.5 Design or Master, from a DeployStudio workflow.

It is being installed as a <key>managed_updates</key> item. Other
managed_install items, such as Office 2011 updates, work fine.

Here's my pkginfo for 10.1.0, for instance:

http://pastie.textmate.org/2381555

Any ideas/suggestions will be very much so appreciated! :)

[Nate]

Try adding something like this:

<key>installs</key>

<array>

<dict>

<key>CFBundleShortVersionString</key>

<string>10.1.0</string>

<key>path</key>

<string>/Applications/Adobe Acrobat X Pro/Adobe Acrobat Pro.app/Contents/Info.plist</string>

<key>type</key>

<string>plist</string>

</dict>

</array>

This would give munki something more specific to look for.

Nate

[Greg Neagle]

Basic questions:

1) Did you run makecatalogs?

2) you've marked this AcrobatUpd as:
<key>update_for</key>
<array>
<string>Adobe Acrobat X Pro Installer</string>
<string>AdobeCS55MasterCollection_Install</string>
<string>CreativeSuite5DesignPremium</string>
</array>

On the clients you expect to get this update, do they have any of the above items in their managed_installs or managed_updates list(s)?

3) Any clues when running /usr/local/munki/managedsoftwareupdate -vvv on a client you expect to get this update?

-Greg

[Juanca]

Greg:

1) I did it with munkiimport, with the .dmg straight from Adobe
2) I have it for the case where yes, computers have it as managed
installs, and cases where I have verified those installs are
successful.
3) That command might have the answer, this is what it shows:

* Processing manifest item AcrobatUpd for update
Looking for detail for: AcrobatUpd, version latest...
Considering 4 items with name AcrobatUpd from catalog production
Considering item AcrobatUpd, version 10.1.0 with minimum os version
required 10.4.0
Our OS version is 10.6.8
Found AcrobatUpd, version 10.1.0 in catalog production
Looking for package com.adobe.acrobat.a10.AcrobatUpd1010, version
10.1.0
This package is not currently installed.
AcrobatUpd does not appear to be installed, so no managed updates...

Even though the clients with this issue do have 10.0.0 installed. I
tried Nate's suggestion, but no dice :(

[Anurag Mohanty]

Have you tried lining up the Acrobat updates? e.g. for 10.0.2
<key>requires</key>
<array>
<string>AcrobatUpd-10.0.1</string>
</array>

[Greg Neagle]

Remove AdobeUpd from the managed_updates section of the manifest.

Sent from my iPhone

[Greg Neagle]

To clarify:

By putting "AcrobatUpd" in managed_updates, you are saying "update this item if it is already installed"
Since there's no receipt for com.adobe.acrobat.a10.AcrobatUpd1010, it's not already installed, so no updates to "AcrobatUpd" will be applied.

What you really want is to update "Adobe Acrobat X Pro Installer", "AdobeCS55MasterCollection_Install", or "CreativeSuite5DesignPremium".

Since AcrobatUpd is marked as an "update_for" those items, you do not need to explicitly add AcrobatUpd to any manifest.

Instead, AcrobatUpd will be found and installed if any of "Adobe Acrobat X Pro Installer", "AdobeCS55MasterCollection_Install", or "CreativeSuite5DesignPremium" are in the machines' managed_installs or managed_updates list.

-Greg

[Juanca]

Anurag: Thanks very much for your input. I'll give that a shot, hadn't
tried that since I understood 10.1.0 didn't require any previous
update

Greg: I don't have AdobeUpd on my manifest. I've tried making a new
manifest to which I'm having some affected clients point to, and with
only AcrobatUpd as a managed_update, and get the same results. I think
I'm missing something really basic, maybe I just need to step away and
take another crack at it tomorrow, with a fresher mind!

Thanks for all your info guys, you're awesome!...I'll post my results
tomorrow! :)

On Aug 16, 4:24 pm, Greg Neagle <gregnea...@mac.com> wrote:
> Remove AdobeUpd from the managed_updates section of the manifest.
>
> Sent from my iPhone
>

[Juanca]

Greg: Just saw your second reply. That makes a lot of sense. I'll give
that a try tomorrow. Thanks so much!!! :)

[Juanca]

Greg:

Out of curiosity and for better practice on my end in the future, does
that mean that this update will only install on the clients that got
Adobe Acrobat X installed via munki by any of those "managed_install"
items? (them being "Adobe Acrobat X Pro Installer",
"AdobeCS55MasterCollection_Install", or "CreativeSuite5DesignPremium")
If yes, is there a better way to configure the pkginfo, so that munki
will deploy the Adobe Acrobat X 10.1 update for instance, to any
computer that has 10.0, regardless of how that got installed on that
computer? (DeployStudio, ARD, manually, etc)

[Greg Neagle]

On Aug 16, 2011, at 7:29 PM, Juanca wrote:

> Greg:
>
> Out of curiosity and for better practice on my end in the future, does
> that mean that this update will only install on the clients that got
> Adobe Acrobat X installed via munki by any of those "managed_install"
> items? (them being "Adobe Acrobat X Pro Installer",
> "AdobeCS55MasterCollection_Install", or "CreativeSuite5DesignPremium")

No. If munki can determine that any of those are installed by checking for the items in the "installs" list or receipts in the "receipts" list, it considers them installed. Munki doesn't keep track of what it did in the past -- every run it checks the items in managed_installs so see if they need to be installed or updated, the items in managed_updates to see if they need to be updated, and the items in managed_uninstalls to see if they've been removed.

So if you want AcrobatUpd to update any of ("Adobe Acrobat X Pro Installer", "AdobeCS55MasterCollection_Install", or "CreativeSuite5DesignPremium") Munki must be able to tell if any of those are installed.

[Juanca]

GOOOOOTCHA!!!!
Thanks very much for the explanation, that most definitely gets me on
the right track!!! :)

[Juanca]

Brilliant!!!!...that did it (removing AdobeUpd and a couple of minor
add ons to pkginfo as far as which items to be an update for), thanks
Greg!!

On Aug 17, 12:19 am, Greg Neagle <gregnea...@mac.com> wrote: