Adobe Acrobat X Pro update

[Jason Hatman]

I have a managed_update for Acrobat X Pro.  I also have one for Acrobat 9 Pro.  The X Pro update package is trying to install on systems that only have 9 Pro installed. The output of managedsoftwareupdate shows that it's looking in the 9 Pro folder instead of the X Pro folder like the installs array tells it to. False positive.

relevent part of managedsoftwareupdate output:

* Processing manifest item AdobeAcrobatProX_Update for update

    Looking for detail for: AdobeAcrobatProX_Update, version latest...

    Considering 1 items with name AdobeAcrobatProX_Update from catalog stable

    Considering item AdobeAcrobatProX_Update, version 10.1.12 with minimum os version required 10.5.0

    Our OS version is 10.9.5

    Found AdobeAcrobatProX_Update, version 10.1.12 in catalog stable

    Looking for application Acrobat with bundleid: com.adobe.Acrobat.Pro, version 10.1.2...

    Getting info on currently installed applications...

    Skipped app PrinterProxy with path /Users/bheff0/Library/Printers/CSNorth-CLJ4700-2.app

    Skipped app PrinterProxy with path /Users/bheff0/Library/Printers/CSNorth-RIC6000-1.app

    Skipped app Default bepbmhgboaologfdajaanbcjmnhjmhfn with path /Users/bheff0/Library/Application Support/Google/Chrome/Default/Web Applications/_crx_bepbmhgboaologfdajaanbcjmnhjmhfn/Default bepbmhgboaologfdajaanbcjmnhjmhfn.app

    Skipped app ad-auth with path /Users/bheff0/Documents/ad-auth.app

    Skipped app Default aohghmighlieiainnegkcijnfilokake with path /Users/bheff0/Library/Application Support/Google/Chrome/Default/Web Applications/_crx_aohghmighlieiainnegkcijnfilokake/Default aohghmighlieiainnegkcijnfilokake.app

    Skipped app PrinterProxy with path /Users/bheff0/Library/Printers/CSNorth-CLJ4700-1.app

    Name: Acrobat

    Path: /Applications/Adobe Acrobat 9 Pro/Adobe Acrobat Pro.app

    CFBundleIdentifier: com.adobe.Acrobat.Pro

    Version: 9.5.5

    An older version of this application is present.

    * Processing manifest item AdobeAcrobatProX_Update for install

    Looking for detail for: AdobeAcrobatProX_Update, version latest...

    Considering 1 items with name AdobeAcrobatProX_Update from catalog stable

    Considering item AdobeAcrobatProX_Update, version 10.1.12 with minimum os version required 10.5.0

    Our OS version is 10.9.5

    Found AdobeAcrobatProX_Update, version 10.1.12 in catalog stable

    Looking for application Acrobat with bundleid: com.adobe.Acrobat.Pro, version 10.1.2...

    Skipped app PrinterProxy with path /Users/bheff0/Library/Printers/CSNorth-CLJ4700-2.app

    Skipped app PrinterProxy with path /Users/bheff0/Library/Printers/CSNorth-RIC6000-1.app

    Skipped app Default bepbmhgboaologfdajaanbcjmnhjmhfn with path /Users/bheff0/Library/Application Support/Google/Chrome/Default/Web Applications/_crx_bepbmhgboaologfdajaanbcjmnhjmhfn/Default bepbmhgboaologfdajaanbcjmnhjmhfn.app

    Skipped app ad-auth with path /Users/bheff0/Documents/ad-auth.app

    Skipped app Default aohghmighlieiainnegkcijnfilokake with path /Users/bheff0/Library/Application Support/Google/Chrome/Default/Web Applications/_crx_aohghmighlieiainnegkcijnfilokake/Default aohghmighlieiainnegkcijnfilokake.app

    Skipped app PrinterProxy with path /Users/bheff0/Library/Printers/CSNorth-CLJ4700-1.app

    Name: Acrobat

    Path: /Applications/Adobe Acrobat 9 Pro/Adobe Acrobat Pro.app

    CFBundleIdentifier: com.adobe.Acrobat.Pro

    Version: 9.5.5

    An older version of this application is present.

    Need to install AdobeAcrobatProX_Update

    Download base URL is: http://munkiserver1.orchard.fruit.com/munki_repo/pkgs/

    Package name is: AcrobatUpd10112-10.1.12.pkg

    Download URL is: http://munkiserver1.orchard.fruit.com/munki_repo/pkgs/apps/Adobe/CS_Updates/AcrobatUpd10112-10.1.12.pkg

    Downloading to: /Library/Managed Installs/Cache/AcrobatUpd10112-10.1.12.pkg

    Downloading AcrobatUpd10112-10.1.12.pkg from apps/Adobe/CS_Updates/AcrobatUpd10112-10.1.12.pkg

    Looking for updates for: AdobeAcrobatProX_Update

    Looking for updates for: AdobeAcrobatProX_Update-10.1.12

    Looking for updates for: AdobeAcrobatProX_Update--10.1.12

Acrobat X Pro update plist

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>_metadata</key>

<dict>

<key>created_by</key>

<string>jenkins</string>

<key>creation_date</key>

<date>2014-10-08T21:07:28Z</date>

<key>munki_version</key>

<string>2.0.0.2229</string>

<key>os_version</key>

<string>10.9.5</string>

</dict>

<key>autoremove</key>

<false/>

<key>blocking_applications</key>

<array>

<string>Adobe Acrobat Pro.app</string>

</array>

<key>catalogs</key>

<array>

<string>stable</string>

</array>

<key>description</key>

<string></string>

<key>display_name</key>

<string>Adobe Acrobat Pro Update</string>

<key>installed_size</key>

<integer>139060</integer>

<key>installer_item_hash</key>

<string>5b95da51e337b277f6869f70a3c612d0a4864469b890fb65152f6214e322b9db</string>

<key>installer_item_location</key>

<string>apps/Adobe/CS_Updates/AcrobatUpd10112-10.1.12.pkg</string>

<key>installer_item_size</key>

<integer>141211</integer>

<key>installs</key>

<array>

<dict>

<key>CFBundleIdentifier</key>

<string>com.adobe.Acrobat.Pro</string>

<key>CFBundleName</key>

<string>Acrobat</string>

<key>CFBundleShortVersionString</key>

<string>10.1.2</string>

<key>CFBundleVersion</key>

<string>10.1.2</string>

<key>minosversion</key>

<string>10.4.3</string>

<key>path</key>

<string>/Applications/Adobe Acrobat X Pro/Adobe Acrobat Pro.app</string>

<key>type</key>

<string>application</string>

<key>version_comparison_key</key>

<string>CFBundleShortVersionString</string>

</dict>

</array>

<key>minimum_os_version</key>

<string>10.5.0</string>

<key>name</key>

<string>AdobeAcrobatProX_Update</string>

<key>receipts</key>

<array>

<dict>

<key>installed_size</key>

<integer>139060</integer>

<key>packageid</key>

<string>com.adobe.acrobat.a10.AcrobatUpd10112</string>

<key>version</key>

<string>10.1.12</string>

</dict>

</array>

<key>unattended_install</key>

<false/>

<key>uninstall_method</key>

<string>removepackages</string>

<key>uninstallable</key>

<true/>

<key>version</key>

<string>10.1.12</string>

</dict>

</plist>

[Gregory Neagle]

Don't add the update pkg(s) to any manifests. Instead mark it as an update_for the appropriate item. This way it is only (and automatically) considered for install if the "main" item is installed.

But I can still think of some scenarios where you might see the behavior you describe, and that would be triggered if both apps (Acrobat 9 and Acrobat 10) share the same bundle identifier, namely: "com.adobe.Acrobat.Pro". There are ways around that, but let's take that step only if needed.

-Greg

--
You received this message because you are subscribed to the Google Groups "munki-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to munki-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Timothy Sutton]

The recommended way to do updates is to not put the update (AdobeAcrobatProX_Update) directly in the manifest, but instead use the 'update_for' key and put in the base item for which it's an update.

It seems that instead, you've put AdobeAcrobatProX_Update in the manifest for a machine that has Pro 9 installed. Munki sees that there is a registered bundle 'com.adobe.Acrobat.Pro' of version 9.5.5 (even though it's at a different path), and considers it an older version. It's unfortunate that Adobe uses the same bundle ID for different major (licensed) versions of their app.

You should still adjust your manifest so that you are just listing installs like "AdobeAcrobatPro9" and "AdobeAcrobatProX", and letting Munki figure out where updates are needed, but to work around the issue of Pro X being seen as a newer version of Pro 9, you could remove the CFBundleIdentifier (and possibly the CFBundleName, I'm not sure) and just leave the paths. In that case Munki will only know about an app bundle at a specific path, and only consider upgrading an app that's located there, rather than by a registered bundle.


You can also look at AutoPkg, which has Acrobat Pro recipes. It happens to lazily avoid this issue by not actually using an installs key at all, and instead only relies on pkg receipts. That's not necessarily the one and only approach, but it's one I use and which has worked well enough for my use.


Tim

[Jason Hatman]

The main Acrobat x Pro installer isn't in Munki since it's part of the suite, so wouldn't I _have_ to put it as a managed_update?

[Timothy Sutton]

If these updates apply to a suite, you could make this an update_for the suite. If you don't install the suite using Munki, then yes, you could instead put it in managed_updates, but you would still want to have some base pkginfo that describes what the suite installs. (Even if the installer pkg doesn't actually exist in your repo, the pkginfo could still be there so that the updates know about what they're updating).

Tim

[Gregory Neagle]

On Oct 9, 2014, at 6:25 AM, Jason Hatman <jason....@gmail.com> wrote:

The main Acrobat x Pro installer isn't in Munki since it's part of the suite, so wouldn't I _have_ to put it as a managed_update?

Is that what you are doing? You didn't say, so we had to guess.

You'll need to fall back to Tim's other suggestion, and the one I was implying, which was to not have Munki use the bundle identifier.

Easiest is to change the type of each installs item from "application" to "bundle": https://github.com/munki/munki/wiki/Pkginfo-Files#installs-array-item-bundle

(Compare the described behavior to that of the "application" type: https://github.com/munki/munki/wiki/Pkginfo-Files#installs-array-item-application)

-Greg

[Jason Hatman]

Thanks for the help guys. Sorry for the lack of info.

[Timothy Sutton]

Acrobat Updates are one of those updates where enough advanced behaviour of Munki needs to be understood, that I think it's worth considering instead using AutoPkg.

Tim

[Jason Hatman]

I do use AutoPkg and I love it. I ended up just adding the appropriate installs array to the Recipe override file. All works fine now.  I removed the CFBundleIdentifier and CFBundleName and changed the type to bundle instead of application.