Anyone else with this issue? Called the support twice and their answer were: try technet.
In the Mac install disk image, there is a file called "Assisted Install.txt". The disk image is Read-Only, but you can use Disk Utility to make a Read/Write copy of it. Once it's in a writeable state, edit the Assisted Install.txt to include your Volume License key/details. While you're there, check out the various flags - you may find some of them useful. Save the changes and use that disk image as your distribution medium - just run the installer.
In the Windows downloaded installer, it decompresses the download file before running the actual installer (Setup.exe) from the decompressed directory. In the decompressed folder, there is a directory called "Files". The Assisted Install.txt file is in that directory. Same applies as above - enter your license details and edit the flags as you see fit. Use the decompressed folder to distribute, and just run Setup.exe on each target machine.
Thx for replying, but "Assisted install" is not what I'm asking about. I've seen it but never tried it cause it seems to be a, to be honest, a really clunky way of distributing an application.
I can't imagine that I'm the only one to have run into trouble regarding this issue. Something has changed for the worse in FMP13 in terms of installation.
>...a really clunky way of distributing an application.
1 .- Shared folder.
2 .- Set "Assisted install" to be "silent" (AI_SKIPDIALOG = 1)
3 .- Send the user to link to setup.exe (email) (not the app.)
4 .- User run link, star install
I still think that this is insufficient. Especially when developers are external to the organization. (maintenance contracts - periodic install)
1. Copy the FileMaker Pro folder from my application folder to another computer with ARD and it's done.
We also use DeployStudio for all our new Macs. That's going to be another problem with assisted install.