offbyone 10 Posted June 22, 2020 Share Posted June 22, 2020 Is it possible to install esmc server component via script on Windows? I just took a look on the PROPERTIES of the MSI file but it seems that they cannot be passed via MST or command line. Thanks for any suggestions. Link to comment Share on other sites More sharing options...
ESET Staff MartinK 378 Posted June 23, 2020 ESET Staff Share Posted June 23, 2020 7 hours ago, offbyone said: Is it possible to install esmc server component via script on Windows? I just took a look on the PROPERTIES of the MSI file but it seems that they cannot be passed via MST or command line. Thanks for any suggestions. From technical perspective it is possible to install ESMC Server component silently (not sure about other dependencies, for example SQLServer/MySQL database), but it is not documented. It should be possible to pass all required parameters via properties. Could you possibly describe reason why would you want to install ESMC silently from command line? Asking because even on Windows "core" operating systems, graphical all-in-one installer should work. I have not verified, but maybe this set of parameter with proper values will be enough for simplest deployment scenario: P_CERT_HOSTNAME='*' P_DB_TYPE="MS SQL Server" P_DB_DRIVER="ODBC Driver 17 for SQL Server" P_DB_HOSTNAME=mydbhostname P_DB_ADMIN_PASSWORD=sa P_DB_ADMIN_USERNAME=mysapassword P_DB_NAME="era_db" P_DB_PORT=1433 P_DB_CREATE_USER=1 P_SERVER_ROOT_PASSWORD=myconsoleadminpassword Link to comment Share on other sites More sharing options...
offbyone 10 Posted June 23, 2020 Author Share Posted June 23, 2020 Hello Martin. Thanks for you answer. The reason is that we heavily use automation for deploying solutions to our customers. And it would be nice if could also roll out ESET to our customers unattended. The properties you mentioned are the ones we also found from the MSI file. For testing we began with the first dialog page of the setup wizzard, which is "Participate in improvement program". The related property seems to be "P_ENABLE_TELEMETRY" however from our testing it seems that initializing it with "0" simply does not work, so we stopped testing. Maybe you have a hint how to disable "Participate in improvement program" in an unattended way? Cheers. Link to comment Share on other sites More sharing options...
ESET Staff MartinK 378 Posted June 23, 2020 ESET Staff Share Posted June 23, 2020 I would expect it to work even without explicitly disabling it (btw. value 0 should be correct). Just for verification, are you using /qn or /q command line parameters to initiate silent installation using msiexec? Link to comment Share on other sites More sharing options...
offbyone 10 Posted June 23, 2020 Author Share Posted June 23, 2020 Normally we use /qn, but to check if settings apply we use interactive mode. However possibly in silent mode settings will apply whereas they do not in interactive mode. I will give it a try and report back. Thanks again for your input. Link to comment Share on other sites More sharing options...
offbyone 10 Posted June 23, 2020 Author Share Posted June 23, 2020 Our first attempt failed with "P_DB_CONNECTION_STATUS = 3" We tried the following interactively which works: Database: MS SQL Server ODBC driver: SQL Server Database name: era Hostname: 10.10.10.10\ESET Use Named Instance: checked Port: 1433 Username: era Password: ***** The Database era already exists on the named instance ESET on the SQL server and the user era which also exists is DBO. Following properties were specified for silent install which failed: P_DB_TYPE="MS SQL Server" P_DB_DRIVER="SQL Server" P_DB_NAME="era" P_DB_HOSTNAME="10.10.10.10\ESET" P_DB_USE_NAMED_INSTANCE=1 P_DB_CREATE_USER=0 P_DB_USER_USERNAME="era" P_DB_USER_PASSWORD="*****" Any idea why this failed? Thanks and Cheers Link to comment Share on other sites More sharing options...
offbyone 10 Posted June 24, 2020 Author Share Posted June 24, 2020 I think we are one step further. If everything is verified I will post an update. Link to comment Share on other sites More sharing options...
offbyone 10 Posted June 24, 2020 Author Share Posted June 24, 2020 (edited) So we have it now working to our needs with the following unattended setup: msiexec /i setup.msi /qn P_DB_TYPE="MS SQL Server" ^ P_DB_DRIVER="SQL Server" ^ P_DB_NAME="era" ^ P_DB_HOSTNAME="mssql\eset" ^ P_DB_PORT=0 ^ P_DB_CREATE_USER=0 ^ P_DB_USER_USERNAME="era" ^ P_DB_USER_PASSWORD="*************" ^ P_SERVER_ROOT_PASSWORD="*************" ^ P_LICENSE_ACCEPTED=1 ^ P_ACTIVATE_WITH_LICENSE_NOW=0 ^ P_ENABLE_TELEMETRY=0 ^ P_SG_SYNC_TYPE=OFF ^ P_SERVER_CERTIFICATES_OPTION=LOAD ^ P_SERVER_CERT_PATH="c:\server.pfx" ^ P_SERVER_CERT_PROVIDED_PASSWORD="*************" Edited June 25, 2020 by offbyone There was a problem with a domain account previously Link to comment Share on other sites More sharing options...
Recommended Posts