#ADOBE ACROBAT PRO 9 UPDATES INSTALL#
#ADOBE ACROBAT PRO 9 UPDATES UPDATE#
#ADOBE ACROBAT PRO 9 UPDATES MANUAL#

Library/Application Support/Adobe/Acrobat/AcroENUPro90SelfHeal.xml Library/Application Support/Adobe/Acrobat/AcroENUDist90SelfHeal.xml You also need to disable the self-heal feature, I believe these are the files that you need to edit:

Then run:Дefaults read ~/Library/Preferences/.90.sh You can get this date by updating Acrobat on a system, launch Acrobat, and enter an admin username/password when prompted. usr/bin/sudo /usr/bin/defaults write /Library/Preferences/.90.sh NoViewerSelfHealNeeded -bool TRUE There is some more about this topic here: This causes the script to look in /Applications/Adobe Acrobat 9 Pro/ first, and only consult System Profiler if the app isnвЂ™t in its default location. # use system_profiler to search for the app Pathname = os.path.join('/Applications/Adobe Acrobat 9 Pro', appname) Not item.get('path','').startswith('/Volumes')] If item.get('path','').endswith('/' + appname) and Change this:Д¬andidates = [item for item in getAppData() You can work around this problem by editing the script and changing some code in the updateAcrobatPro function. This happens when System Profiler has no record of Acrobat Pro - if you look in the list of applications that System Profiler generates, youвЂ™ll probably see Acrobat Pro missing. IвЂ™ve updated the link to the Python script.

#ADOBE ACROBAT PRO 9 UPDATES MANUAL#

Manual uninstalls using the uninstaller in /Applications/Utilities/Adobe Installers still work, though.

#ADOBE ACROBAT PRO 9 UPDATES INSTALL#

If you do install Acrobat Pro 9 updates, unattended uninstalls using the methods from the Adobe Enterprise Deployment Toolkit now fail, because Adobe Setup no longer thinks Acrobat Pro 9 is installed and gets very confused. Patching Acrobat Uninstaller.app complete. Updater log at /var/root/Library/Logs/Adobe/Acrobat/Acrobat 9 Pro Patch2.log Updater log at /var/root/Library/Logs/Adobe/Acrobat/Acrobat 9 Pro Patch1.log Updater log at /var/root/Library/Logs/Adobe/Acrobat/Acrobat 9 Pro Patch0.log Getting info on currently installed applications. Mounting disk image AcroProUpd910_all.dmg updateAcrobatNine.py AcroProUpd910_all.dmg HereвЂ™s some output from an install session: updateAcrobatNine.py /path/to/AcroProUpd920_all.dmg updateAcrobatNine.py /path/to/AcroProUpd913_all.dmg updateAcrobatNine.py /path/to/AcroProUpd912_all.dmg updateAcrobatNine.py /path/to/AcroProUpd911_all.dmg

updateAcrobatNine.py /path/to/AcroProUpd910_all.dmg

#ADOBE ACROBAT PRO 9 UPDATES UPDATE#

Install each update in order, something like this: Copy the needed disk images to the target machine. Install the script itself somewhere on the target machine. You could use this script via SSH or ARD to install the updates: This script skips all of the process checking done by the original patching app, so itвЂ™s best to run it when no-one is logged in. The result: a Python script you can use to silently install all of the (so far) released updates to Acrobat Pro 9. I started tearing apart the patching app on one of the update disk images and discovered it was running some shell and Python scripts to do the actual patching. However, there are some officially supported methods to do silent installs of CS3/CS4 apps, and even to install updates to those apps.Д«ut updates to Acrobat Pro 9 are in a completely different format than all other Adobe installers/updaters and canвЂ™t be silently installed with any of the supported methods. Silent installs of Adobe products are a bane of an OS X administratorвЂ™s existence.

Adobe acrobat pro 9 updates