FileMaker 12 and Casper Imaging

Hi,

Could it be an issue with the package? I normally use a Composer snapshot package for FileMaker. If you are ticking "Install on boot drive after imaging" then it shouldn't be any different to installing via a policy.

Packaging FileMaker is actually quite a task. When packaging FileMaker 13 (not the same version but maybe the same) I had to follow the instructions found on page 10 here:

https://fmhelp.filemaker.com/docs/13/en/fmp13_network_install_setup.pdf

You can also check out this thread:

https://jamfnation.jamfsoftware.com/discussion.html?id=11007

It was a huge pain because you have to dig into the installer and I think the application itself to find the pieces you need to compose a deployable pkg.

The message you are referencing above is the same message that I received when I hadn't packaged FM13 properly which makes me suspect that FM12 will require similar steps.

I have found that once the initial package is composed properly all subsequent versions of that FM package can be snapshot via Composer, it just requires these bits first:

*The FileMaker Pro 13.pkg or FileMaker Pro 13 Advanced.pkg installer application *The personalization file Assisted Install.txt
*The registration tool (Registration.app)

Hope that helps!

The instructions from FM do miss a few steps, you need to ShowHiddenFiles to be able to find the registraion.app

Other then that, the package building script works pretty well (using the ARD instructions)

Have you tried deploying that package as a standalone policy?

You'll also want to make sure that the licensing info, including the user name is EXACT, otherwise the product will appear unlicensed post install.

Hi all,

Where is this registration.app file? Which directory to look for it?

Check page 9 of this document to locate and reveal the hidden Registration.app: https://fmhelp.filemaker.com/docs/15/en/fmp15_network_install_setup.pdf