Please be advised that silent installation of server components is not officially supported. Further to that, we had a method, although not officially supported, it was known to work in versions 5.0 and older, however with version 5.1 we have changed installer technology and silent installation was not tested by our QA teams. Our server components installers were not designed to be deployed silently as we have assumed server components such as database, application server and console would be installed sporadically, manually at the setup stage.
If you would like to proceed with silent install tests of 5.1 database component, you could attempt to use below method:
Silent SX DB install:
Db.exe /qn NAMED_INSTANCE="SILENTINSTANCE" /L*v %TMP%\setupdb_silent.log
NAMED_INSTANCE can be skipped if installing to default instance.
As an alternative to the above method you can also use instructions from KB below:
Manual Installation or Updating of the Lumension Endpoint Security SX Database
Thanks for the prompt response. Unfortunately when I run the Db.exe with the flags you mentioned, the .msi help window is opened.
I can confirm that I am using DeviceAndApplicationControl 5.1.0, and when I run either the Db.exe or Db.msi with /? that the flag NAMED_INSTANCE is not present.
We use Advanced Installer in 5.1 and to completely hide the UI during installation (install silently) you would need to use Advanced Installer's switch /exenoui, which is listed when you start the bootstrapper with /? switch. The NAMED_INSTANCE is an MSI property and it is listed in MSI log for example, so if you wanted a list of all properties you can attempt single manual install (does not even have to be successful) and review the MSI log, towards its end.
When installing with Advanced Installer silently, you start the bootstrapper, then provide /exenoui switch and then, what follows, is the list of MSI properties and switches passed by bootstrapper to MSIEXEC, for example:
Db.exe /exenoui /qn NAMED_INSTANCE="SILENTINSTANCE" /L*v %TMP%\setupdb_silent.log
That was indeed the problem, and it does now install silently.
Considering I am intending to install the entire product silently/automatically, could you please provide me with any fixes for similar issues I will and am facings? Such as the the keygen silent install, sxs silent install and smc silent install?
Can the smc be installed silently using a configuration file to pass in policies for endpoint protection? Can the client deployment be automated through the app, or clients otherwise installed remotely using a deployment framework?
I am stuck again with the silent install. I see under the .msi command line flag help there is a section called Setting Public Properties [PROPERTY=PropertyValue]. This gives absolutely no indication as to what the properties in each installer are, and leaves me constantly attempting to guess what they are. What I would truly appreciate is a list for each installer of all the possible public properties, and what their defaults are when not specified.
Also, there appears to be no way to retrieve the command line flags for the keygen program, so that I may pass it the directory and the seed via the command line. Can you please indicate whether this is possible, and if so, what the steps to do so are?
As I mentioned in my initial answer, we do not support silent deployment of server components. If you would like to proceed with this, you could raise a support ticket using https://support.heatsoftware.com and we could discuss this further and provide some examples of commands that were known to work in earlier versions. There is no guarantee that silent install of server components will work, as this has not been tested by our QA teams with 5.1 release.
Indeed the process would look similar to this:
- attempt a silent install,
- analyse at which point the install failed,
- resolve the issue by providing relevant MSI property at command line
You could raise a feature request using Ideas page on our current Ivanti Community portal. Also, it seems keygen is not a command line tool and would need to be run manually.