I would like to be able to distribute a BESClient MSI with all the client settings baked in. If I edit the MSI or repackage an MSI will that affect the IBM code signing? If i create a MST first can I bake an MST into the MSI? Just wondering what everyone here is doing for custom configured MSIs particularly with the BESClient.
I’m not aware of anyway to do it directly from the MSI but you can use the setup.exe version of the installer (it will be in the Client folder of the BES Installers folder created on the IEM server complete with your masthead) and you can then add a clientsettings.cfg file that will be processed when the setup runs. Examples on http://www-01.ibm.com/support/docview.wss?uid=swg21506065
You can tweak the following task to include whatever settings you would normally put in your clientsettings.cfg file, put it in the master action site, and take it as an open policy action from a master operator:
You can edit an MSI and have it set registry values yourself but its not a simple process. Microsoft provides a tool to do it but we don’t directly support someone doing this. The cfg file as @jgstew mentioned is our way around this but if you want to “pre-populate” registry values you can.