11/01/2016 1049 views
I have an MI for FileMakerPro 15. The program comes from the publisher as an EXE which unpacks install files. The install files includes an MSI, and another setup.exe. I configured the MSI to inject the license info, but unfortunately the other suppression options for a silent install are only available in conjunction with the setup.exe. So, I zipped the install files, msi, and setup exe and associated this zip file with the MI deployment. I chose to overwrite the default installation and run the command 

setup.exe /s /qb+ 


as pictured in the attachment, per this document. What I am finding is that the package downloads and unzips in the Kace downloads folder, but the setup command either does not run, or is not successful (there is no feedback for me to confirm which). I can manually run the command from the command line on the target client, and the program installs as expected. So, I feel that the deployment files are getting deployed to the target OK, but the setup command does not appear to be running as expected, possibly due to a syntax or permissions issue? I did notice that running the setup command manually there was a UAC prompt, but I would expect that this would still happen if setup.exe was run by the deployment, and I did not see this.

Is there a way to verify what/how this command is being run, or a method of running it differently for anyone who has had success deploying this program? Thanks in advance!
Answer Summary:
0 Comments   [ + ] Show comments


Answer Chosen by the Author

According to the vendor you should be able to use the MSI - this guide here advises of the command line options.

Msiexec has its own command line options, where you can specify silent install switches.

You mentioned that you've configured the MSI to inject the licence info, this goes against best practice to modify a vendor MSI and a transforms customisation file (MST) should be used instead. If you don't have a MSI packaging tool at your disposal, then you can download a copy of Microsoft Orca that will help with this simple transforms creation.

Any of command line options in the first link that are public properties, (CAPITAL LETTERS) can be added to the Property Table of the MST to customise your installation and then the MST called on your installation command line.

Hope that helps,
Answered 11/01/2016 by: dunnpy
Red Belt

  • Hi Dunpy,

    Thank you for the reply! The guide you linked is the same one I followed for the installation. You're correct that it offers use of the msi, but not the command line options - those, unfortunately, appear to only be used with the setup executable. Configuration options are called with the setup.exe from an assistedinstall.txt file. Editing the MSI appears to be a supported solution in the guide for at least those three license configuration items, but it specifically mentioned not editing the others - and it doesn't work to edit them anyhow. (pg 8 in the guide "Saving the license key in the .msi installer walks through downloading Orca and editing the MSI.)

    Filemaker's method of performing a silent install appears to be a combination of configuring the assistedinstall.txt and running the setup.exe with options. Again, this method appears to work fine when run manually on the client with the package deployed from KACE. The challenge appears to be with how the setup.exe is being run by Kace.

    Could you point me towards documentation on troubleshooting through the logs? I'd like to see what KACE believes it is doing when it runs the setup.exe command as specifified in the install command line of the MI.

All Answers

This turned out to be an issue with where the application was calling the setup.exe file; support basically extracted everything and dumped it into one parent folder and the application deployed with the setup listed above. Man it would be cool if there was a way to get some feedback on deployment status and detailed information about a failure!!!
Answered 03/14/2017 by: fcoetech
Senior White Belt