The obvious one to try is the system default preferences folder at /Library/Preferences. The documentation doesn’t say at all where this plist is, but we can take a good guess.

And in fact, it does seem to be using the same FeatureLockDown subsystem to disable the plugin, except it’s writing the bUpdater boolean value in a plist. This sounds familiar to that FeatureLockdown no-line-break mess we’re still trying to forget we were ever desperate enough to try in the first place. Option 15.6.1: Disabling and locking the Updater In this case, we can assume the writer meant to use the correct path to the plist file, and not one that doesn’t normally exist on an OS X system. We can skip this – this is what we’re already having to do, set per-user preferences with MCX, a Profile or script. “The update mode is set on a per user basis as follows: (…)” Option 15.6.2: Set the update mode to manual

Because Adobe so rarely follows system conventions in these implementations, I didn’t feel like could easily gloss over an error and assume the writer meant to write something else. It’s clear that we’ve reached a less read-over section of the guide, as there are ambiguous terms and incorrect filenames/paths in nearly every written line of this section. However, we would need to make a point of doing this every time we run an updater pkg for Acrobat. This option is looking pretty good at this point, which is to remove the Updater plugin entirely to prevent it from checking for updates. Option 15.6.3: Remove the Updater plugin itself We’ll examine these in reverse order, because up until recently this would have been my order of preference (given that the first option was broken until very recently.) You might also come across the topic of updates in the Enterprise Administration Guide for Acrobat, and see a few options there (Section 15.6, page 139). I did not find this method to work reliably.

app bundle at Contents/MacOS/Preferences/FeatureLockDown and change this 822-character line: > ] It says to just modify a file inside the Acrobat Pro X. The AAMEE Technical Note on “Installing and Configuring Exception Payloads” suggests you can configure the FeatureLockdown system. There is no such functionality anywhere in the adobe_prtk binary on OS X. The Adobe Provisioning Tool would have you believe, going by its usage statement, that there is a -M option to suppress updates. at login time with a LaunchAgent).Īdobe has alluded to built-in functionality for disabling updates in Pro X in the past, so we’ll summarize what’s been presented to date: Things are much better now, but configuring a common setting such as disabling update checks for all users has remained unnecessarily complicated, for despite Adobe using a property list to store these parameters, they were per-user only, requiring these to be managed either using MCX/Profiles or a manual script to apply the appropriate preference in every user’s Library folder (ie.

Update acrobat reader mac