Software Deployment Question
FileMaker Pro 16 for Mac fails to deploy with original ESD with K1000 agent v7.1.62
06/06/2017 859 views
It seems the K1000 v7.1.62 agent, while carrying out a managed installation, will prioritise a ".app" over a ".pkg" if the two types of Mac file system object appears at the root level of the disk image volume.
FileMaker, Inc. has placed a hidden "Registration.app" at the root level of the ESD (electronic software download) disk image downloaded by [volume license] customers. There is also the installer package "FileMaker Pro 16.pkg". The Mac managed installation process looks for either a ".pkg", ".mpkg" or ".app" as part of an automated Mac software deployment. Usually, software developers only have one of these at the root level of their install source. With FileMaker placing two there, it means that the agent must pick between them. It would seem it prefers the ".app" file. This results in the Registration.app being copied to the /Applications directory instead of the FileMaker Pro 16 install going ahead as expected.
To workaround this problem, you can create a read/write image of the ESD and delete the Registration.app. Then make a new image of that which is back to read-only compressed format.
I have logged a support ticket for this as I think KACE engineering needs to review its decision to prefer ".app" over ".pkg". Additionally, formal guidance could warn others of this possibility and the need to workaround it.
It is possible this issue existed in previous versions of FileMaker Pro, as I have not carried out any investigation to confirm or deny this.
Be the first to answer this question