- Adobe acrobat 9 for mac pdf#
- Adobe acrobat 9 for mac install#
- Adobe acrobat 9 for mac pro#
- Adobe acrobat 9 for mac code#
It’s almost shut the hell up, but the Adobe Updater might decide to pop-up and urge your user to call you up to run updates, so shut it up you got to jump through some hoops, its an “XML” file Adobe style so defaults won’t work on it, nor will plistbuddy, that and it’s a per user setting, so they must run it once to make the file, then you can change it:Ĭat ~/Library/Application\ Support/Adobe/Updater6/AdobeUpdaterPrefs.dat | sed 's/1\/0\/' > ~/Library/Application\ Support/Adobe/Updater6/AdobeUpdaterPrefs.new mv ~/Library/Application\ Support/Adobe/Updater6/AdobeUpdaterPrefs.new ~/Library/Application\ Support/Adobe/Updater6/AdobeUpdaterPrefs.dat usr/libexec/PlistBuddy -c "set :0:IsInstalledKey NO" /Library/Application\ Support/Adobe/Acrobat/istįor Tiger users the path is: /Library/Receipts/iTunesX.pkg/Contents/Resources/PlistBuddy
Adobe acrobat 9 for mac pdf#
Lpadmin -p AdobePDF9 -E -P /Library/Printers/PPDs/Contents/Resources/en.lproj/ADPDF9.PPD -v pdf900://distiller/ -D "Adobe PDF 9.0"Įven if you’ve copied in the PPD, the PDE plugin, the cups backend, and setup the printer, it’ll still think its damaged because you don’t have the PPD in Korean, Japanese, and two type of Chinese! So, must use PlistBuddy to correct this (because defaults is tricky to use when a dictionary is nested in an array – WHY Adobe?!) Applications/Adobe\ Acrobat\ 9\ Pro/Adobe\ Acrobat\ Pro.app/Contents/MacOS/SelfHealFiles/AdobePDFPrinter/
Adobe acrobat 9 for mac install#
They are all found in: /Applications/Adobe Acrobat 9 Pro/Adobe Acrobat Pro.app/Contents/MacOS/SelfHealFiles/AdobePDFPrinter/Īfter you’ve copied them to their places, you can run Adobe install script: Library/Printers/PPDs/Contents/Resources/en.lproj/ADPDF9.PPD Now is the truly ridiculous part: if those files and keys aren’t found Acrobat ask for an administrator password and then proceed to write them in current users ~/Library/Preferences! What your users don’t know is they can click Cancel a couple times and it will still write them out, but your they’ve already called you to remote in and authenticate them – you lose! Why Adobe?! WHY!?! Asking for an admin password when you’ll just write it to ~/Library/Preferences? These next keys really make it complain if it can’t find them, and yes even if you don’t use the plugin it looks for WebBrowserUsePath, so make sure it’s there, and NoViewerSelfHealNeeded gets a new date put after it for every release! Wow neato, a fun easter egg hunt, thanks Adobe!ĭefaults write /Library/Preferences/.90.sh "NoViewerSelfHealNeeded Dec 21 2009" -bool TRUEĭefaults write /Library/Preferences/ WebBrowserUsePath -string "file://localhost/Applications/Adobe%20Acrobat%209%20Pro/Adobe%20Acrobat%20Pro.app/"ĭefaults write /Library/Preferences/ AdobePDFDriver -string "file://localhost/Applications/Adobe%20Acrobat%209%20Pro/Adobe%20Acrobat%20Pro.app/" Rm -rf "/Library/Internet Plug-Ins/ugin" Ĭp -R "/Applications/Adobe Acrobat 9 Pro/Adobe Acrobat Pro.app/Contents/MacOS/SelfHealFiles/Library/Internet Plug-Ins/ugin" "/Library/Internet Plug-Ins/" Make sure you copy in the new Acrobat Internet-Plugin if the user is using that:
Adobe acrobat 9 for mac code#
Then you find your “standard” users without admin privileges are getting bothered by Adobe’s SelfHeal BS.įew things going on here that I’ll try and explain, the code formatting should be copy paste-able check it in a text editor, but all line breaks should be preserved.
So you figure out all the files with loggen, Tracker, fseventer, or whatever your tool, then build your own package with Iceberg.
Adobe acrobat 9 for mac pro#
So, if you deploy Acrobat Pro to a corporate environment you already know what an aggravating experience it is to try and deploy updates to Adobe products.
0 kommentar(er)
