![]() ![]() Also, by that time, Extensis had acquired Font Reserve, ending the healthy competition between the two, and the steam seemed to go out of the development on both products. I then tried Extensis’s Suitcase and stayed with it happily for a year or so, but eventually it broke against Panther, and although a revised version was issued, I found it sluggish and undependable. For many years I was strongly attached to DiamondSoft’s Font Reserve, but it foundered somewhat on the breakers of Mac OS X initially it didn’t support many Mac OS X fonts, and Classic activation was never reliable. ![]() In past TidBITS articles, I’ve talked about what a problem font management on the Macintosh has always been, and what steps I’ve taken to alleviate it on my own machine. #1643: New Mac mini and MacBook Pro models, new second-gen HomePod, security-focused OS updates, industry layoffs.#1644: Explaining Mastodon and the Fediverse, HomePod Software 16.3 and tvOS 16.3, GoTo breach.#1645: AirPlay iPhone to Mac for remote video, Siri learns to restart iPhones, Apple's Q1 2023 financials.1646: Security-focused OS updates, Photos Workbench review, Mastodon client wishlist, Apple-related conferences.1647: Focus-caused notification issues, site-specific browser examples, virtualizing Windows on M-series Macs.They just seemed to care more about their product and providing a good experience. 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |