Hi All.. I'm hoping someone can shed some light please, as I seem to be able to use the revised AppleRemoteDesktopDeployment.sh script and also tried the zip upload to jamf self service all with success on the install. The only problem is i'm getting this error each time I open the application and I can't work out what it is relating to? Is the fmcert not loading or incorrect? If i change the Assisted Install.txt to 0, instead of 1 i get cant find "0".

Our organization was having the same issue, we were able to get it working by placing the cert file into a .pkg (repackaged), essentially using @michaelprice's method. However we were still having issues on our windows side.

Just to share for anyone else who is having a similar issue with the Windows installer; the fix is essentially the same, the key (hah) ended up being to set the "AI_LicenseKey" property to "LicenseCert.fmcert" as mentioned above for the mac version. On the windows side I edit the .msi installer and modify the properties directly so that I don't need to include the assisted install file. So in addition I have the following properties set which worked:
- AI_LICENSEKEY=LicenseCert.fmcert
- AI_LICENSE_ACCEPTED=1
- AI_REGISTRATION=0
- AI_SKIPDIALOG=1
- AI_TRIALORLICENSEKEYORCERTIFICATE=CERTIFICATE

Then I just install with "msiexec.exe /i installername.msi /qn /norestart" and it's working like a charm.

Has anyone had any luck auto provisioning hosts with the FileMaker Pro 18 installer? Right now users have to manually enter in the host, and would prefer having this included with the install.

What worked for me was to do the normal ARD package process with the main FileMaker application, then put the .fmcert file from /Users/Shared/FileMaker/FileMaker Pro Advanced/18.0/LicenseCert.fmcert in its own package using Composer. Then I added the ARD pkg and the fmcert pkg to the same policy. Only one extra step.

@michaelprice Your way does install the app, and I believe it sees the license cert, but it doesn't appear to see the AssistedInstall file. The user is prompted to accept the license, which is exactly what we don't want. I know I had issues with FMP17 but we got them resolved. I can't remember how though. Has anyone had any luck getting the license to be accepted?

I just packaged up filemaker pro 19 using the script, assisted.txt, license.fmcert file and the app all in one folder. did the chmod to the script as the instructions say. edited the assisted.txt (nothing entered in license information line), suppressing dialogs, company name, kept the updates to inform the user that updates are available, but turned off the option to not notify of new versions

ran the script, uploaded the pkg, tested and the package installed. I run the application --> about filemaker pro and the license key information is displayed

I was looking for some information on how to deploy Filemaker 19 and saw tcandela's response above (that it worked for him) and couldn't figure out why the script wasn't working for me. Apparently, the script is different than the one posted by hepvd. Here is the link to the correct instructions for anyone that's looking https://help.claris.com/en/pro-network-install-setup-guide/#install-filemaker-pro-macos . The script in the link (there's a link within that page to download it) searches for the .app instead of .pkg and then creates the correct .pkg file. The instructions are pretty much the same except the script needs to be specific to FileMaker 19.

@jmbwell's method worked for us with FMPA 18.

@aco1010 Thank you, it worked very well for the FileMaker 19 version for us

AI_LICENSEKEY=LicenseCert.fmcert

This worked great & is very simple. No scripting or post-install process required.

Thank you.

I am a noob... how does the policy know run the pkg after unpacking the zip? Does any pkg archived within a zip get run by default on unpacking?