Having read in the Acrobat Deployment Guide that as of Acrobat 10.1.1, there's support for placing a FeatureLockdown-like key in a plist in /Library/Preferences. This is detailed on page 142-143:
I'm specifically concentrating on Acrobat Pro X (10.1.1) in this case, and am testing on Snow Leopard 10.6.8. I've placed a plist at that path:
sh-3.2# defaults read /Library/Preferences/com.adobe.Acrobat.Pro
{
10 = {
FeatureLockdown = {
bUpdater = 0;
};
};
}
Or, if you want the full XML plist contents:
<?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>10</key>
<dict>
<key>FeatureLockdown</key>
<dict>
<key>bUpdater</key>
<false/>
</dict>
</dict>
</dict>
</plist>
It doesn't seem to take effect. I've tried restarting, logging in and out the user, convert to and from XML to binary plist format, nothing. I notice that Acrobat Pro X's updater plugin also knows something about a plist at /etc/defaults/AdobeARMOverrides.plist. Is this of any use?
Also, the proposed workaround at 15.6.3 is wrong:
"15.6.3 Preventing any updates
To disable the application’s ability to update altogether, use a post install script to move, rename, or
delete the Updater.acroplugin file from the <root>/Contents/Plug-ins/Updater.acropluginplug_ins
directory."
This should read "<root>/Contents/Built-in/Updater.acroplugin". I'm quite able to resort to this method instead, but I'd rather use the plist method so I don't need to remove the Updater with every minor update.