![]() Most didn't want to go back to how it was before this was implemented, since it was such a mess.Īny font server would likely do as well, so if you really want to get serious about controlling this, I suggest testing them all out and seeing what fits best. The important thing was, having a consistent, clean and bug free set of fonts actually made their lives easier, so it wasn't hard to get everyone to stay in line. Savvy users knew how to drop fonts into ~/Library/Fonts/ but most of them just complied. In my particular setup, since no users were admins, those steps cut down on the large majority of rogue fonts, since they could only install from the FAP client. They seem to multiply and copy themselves from machine to machine until you have to take drastic measures! As anyone who has dealt with this knows, fonts are akin to viruses. FAP Server was a godsend when I worked in a creative environment. I also never hid the local Fonts folder in their home directory, but I did stop people from using FontBook. The exception being that I used FontAgent Pro Server in place of UTS. Īcdesigntech's method sounds good, and is similar to one I've used in the past. ![]() I've written an article about white/blacklisting apps here. It's left to our creative departments to police fonts used in artwork since this method does not stop artists from using fonts on their desktops or potentially figuring out how to get fonts into the hidden ~/L/F folder. This way we only have to worry about what fonts the company actually is licensed for since all other fonts get removed. Finally, we leverage UTS to provide only the fonts necessary to each department.I've written a short bash script to find any fonts other than in /System/Library/Fonts and remove them, then lay down a fresh package containing only fonts common to all departments in /Library/Fonts.We've made ~/Library/Fonts hidden so users cannot just drag fonts into this folder.We have a 3rd MCX to enable Family Controls (required to white/blacklist apps).We have a 2nd MCX to Blacklist /Applications/FontBook.app (since non-admin users can use it to install fonts in ~/Library/Fonts).We have an MCX to whitelist every application on /.We are currently testing out a hybrid MCX/hidden folder/manual deletion/UTS solution to this: Turn the Collect Inventory Policy back to something reasonable - like once a day.Add the fonts collected to the Suppress Fonts list.run sudo jamf recon on the "perfect" Mac.Turn the option to collect fonts back on.Remove fonts collected by the JSS (however you do that.).Set the Update Inventory policy to Disabled.Turn off the option to collect fonts until I'm ready.If I do manage to gouge the existing fonts collected by the JSS, I'll need to do the following: ![]() ![]() That's unfortunately what I did, and as far as I can tell, there's no way through the JSS interface to remove the whole list available for the Supress/Unsupress lists - and I don't much feel like hand adding appx 2k fonts by hand. Here's the problem- when you turn on collecting fonts as an inventory option you'll start getting fonts from any system that checks in, not just the "perfect" system, thus polluting the baseline. I need to get the names, amounts and install frequency of the "unknowns" to start to resolve licensing and, if need be, buy more or remove if unneeded. To set a "baseline"- then anything showing up in a font report is in the "unknown" category.
0 Comments
Leave a Reply. |