Wrote up a handy script to clear all the font caches for the Mac OS, Adobe, MIcrosoft Office and Apple iWorks.
I am using this in Casper, so I have it running as root and having a reboot happen after. If you are going to run this on your own, you may want to put a root check in there and make sure to reboot after.
’till next time
## Author: C. Tangora
## Purpose: Remove Font Cache from Adobe, Microsoft, iWork and Mac OS.
## If run outside of Casper, be sure to be root & reboot after.
## Adobe Font Caches are stored in the User's Libraries, and will have "Fnt" in the name and end in ".lst".
echo "Removing Adobe Font Caches (Lists)"
find -x /Users -mindepth 5 -type f -iname *Fnt*.lst -delete
## Next it will remove the font caches from Microsoft Office.
echo "Removing Office Font Caches"
find -x /Users -mindepth 7 -type f -name *Office\ Font\ Cache* -delete
## iWorks is next on the chopping block
echo "Removing iWork Font Caches"
find -x /Users -type f -name com.apple.iwork.fonts -delete
## Next we will restart the Apple Type Server.
# This is the one we want to make sure we reboot (or at least logout) to restart.
echo "Removing OS Font Caches"
atsutil databases -remove
echo "Restarting Apple Type Service Server"
atsutil server -shutdown
atsutil server -ping
echo "Completed Font Clearing."
echo "Please restart ASAP."
Save the intro for later. Down to business.
Adobe has come a long way in the Mac installers for their products, the Adobe Application Manager Enterprise Edition (AAMEE). However deploying it is still a process that requires some finessing. JAMF’s Casper does a great job, but if you are not running Casper on a Mac server you are most likely going to run into issues getting it deployed without issue. Specifically if you have your repository served out via HTTP or SMB.
The issue is a known issue, and knowing Adobe they are not going to fix it. What I have done doesn’t fix it either, but it does get rid of the extensions so InDesign only loads 223 extensions and not 233. The ten I took out are all related to InCopy, so if you don’t know what InCopy is or you know what it is and you don’t use it, feel free to use this code to get your InDesign CS 5.5 deployed without users calling back asking why there are errors.
The first part is to use AAMEE to create the installer. This is documented well on JAMF’s site and Adobe’s. Just make sure you disable AIR and continue on errors.
The second part is simple, make a script that will run after the installation and just ‘rm’ those pesky extensions away. When InDesign launches it will register the remaining extensions and launch without issue. I’ve opted to nuke the whole lot InCopy extensions, but you could get selective if you like.
rm -fdr /Applications/Adobe\ InDesign\ CS5.5/Plug-Ins/InCopyWorkflow
Of course, I highly suggest you just type it out, but if you want to copy it, feel free.
Till next time.