Creating a PKG with Composer of Filemaker Pro 14.x.
Requires a License of course, and FMP provides a Assisted Install.txt file that has the License Key info, Organization, etc. The FMP installer I am sure references this file when installing.
Did all this in Composer in which Composer did capture the license info, then built the PKG and deployed onto another Mac, and the license info was gibberish characters.
Any experiences / thoughts on this. Much thx in advance, John
Does FileMaker require this license file to be next to the installer during installation? And does FileMaker come as a PKG? You could use this method This Method. Basically, you create a composer package to install FMP and the license file into /tmp/FMPTemp/ And then have a postinstall script to execute "installer -pkg /tmp/FMPTemp/FileMakerInstaller.pkg -target /" and off it goes...
What I did was use Composer to capture me placing the Assisted Install.txt, FileMaker 14v4 Updates.pkg, and FileMaker Pro 14.pkg files in a place of my choosing(/Library/Application Support/FileMaker). Then, I added a postinstall script that looks like this:
#!/bin/sh ## postinstall pathToScript= pathToPackage= targetLocation= targetVolume= sudo installer -pkg /Library/Application Support/FileMaker/FileMaker Pro 14.pkg -target / sudo installer -pkg /Library/Application Support/FileMaker/FileMaker 14v4 Updates.pkg -target / sudo rm -rf /Library/Application Support/FileMaker exit 0 ## Success exit 1 ## Failure
This basically temporarily stores the installer, runs it, activates it, and then deletes the temporary files. It automatically applies the Assisted Install.txt file if it's in the same directory as the installer pkgs. These three lines just streamline things a bit.
I had fm14 packaged with success.
I followed the instructions, "Installing FileMakerPro using a networked volume (OS X) "
of course with AssistedInstall.txt
then an installation recording with composer and distributed as pkg
and in the same policy,
I have the new FM release packet 14.0.4 distributed without recording as pkg
I hope its work
Hey @raven.dover which licensing model does your organization use? I know FileMaker has two (concurrent and perpetual). I use concurrent and typically make a snapshot package which then picks up the registrations/serial I input during the install with no issues. I can tell you (from experience) that if you do not format your Company Name (registered to) EXACTLY as it is written on your ETLA...even as far as where there are capital letters and where there are not then it can some times not work.