What’s more, you can compare fonts and check out detailed information about them, such as name, library, family, and type, and keep fonts organized with the aid of libraries and sets. The text can be tweaked in terms of size, color, and background color, as well as printed. Plus, you are allowed to preview each font by displaying preset or custom text messages. If you have multiple fonts installed on your system and scattered around different places, FontAgent Pro helps you unite all available fonts into a single panel. A help manual is also available in case you have any questions about the setup process. However, rookies may need to invest extra time into decoding the feature package. It is pretty easy to get used to configuring FontAgent Pro’s settings if you have previously worked with a font manager. You are welcomed by a clean feature skeleton that reveals a list with all fonts detected on your system. They just seemed to care more about their product and providing a good experience.FontAgent Pro is a font manager that allows you to view, compare, and export the fonts deployed on your system. I always preferred their solution to the Extensis offerings myself. Good news is, I think there is a separate pkg in the download for just the plug-ins that I was able to push via ARD at the time that would fix that. I had made the mistake once or thrice of doing the installs in the reverse order. (Hmm, was it a burger?)Īs for the CS plug-ins, I can say that FontAgent Pro has always been pretty good at recognizing the installed applications and injecting the plug-ins into the proper locations, as long as Adobe CS and/or QXP are installed before the FAP Client of course. I'm lucky I remember what I ate for lunch yesterday. Unfortunately, actual memories of what I did are very fuzzy. Not sure about the server credentials and AD link. I seem to recall that I was able to bake a registered version into my crude imaging setup at the time, so I would say its probably possible to deploy a license file as part of your package. This was version 3 I believe and I touched a little on version 4. I worked with FontAgent Pro Client and Server some years ago, but it was before my Casper Suite using days, so no real automated deployment. Is this something the users will need to handle (oy, I hope not as not all users are admins).

How is the serial number handled for client/server environments.or is it one of those 'don't worry about it, the server is the only thing that needs to be licensed' jobbies?Īlso, is the Client for FAP Server.pkg intelligent enough to look for existing Creative Suite and QuarkXPress applications so it can install the required Plug-In or Xtension? The preupgrade/preinstall/postinstall/postupgrade scripts in Client for FAP Server.pkg only seem to shut down the running process and remove old versions. I'm fairly certain they'll ask us to package/deploy preconfigured to point to the FAP Server so I'm hoping someone here can enlighten us on what files (or commands?) need to be put into our wrapper so when we deploy it the users will not be prompted for the FAP Server address (FQDN). Pushed to logged off computer without a problem.

A quick peek at the Client for FAP Server.pkg raises no flags, it's actually a pretty clean package. A few of the groups we support use FontAgent Pro 5 (server/client), so we're looking at packaging it for distribution.

Fontagent competitive upgrade