Customizing Installation

Installation ››
GeoCrew

Like the compiled .msi file, setup.exe can accept a number of command-line parameters. Using these parameters, data, such as the language in which the setup should run and whether to launch Setup.exe silently, can be included on the command-line. Parameters can also be passed through the setup.exe directly to the underlying .msi file. These arguments may be divided into the following categories:



License Type


The FDF_LICENSETYPE setup property defines type of the license. It can be either SL for single-user licensing, or NL for network licensing. In case of network licensing you also need to define licensing server IP address. For example:


setup.exe /v"FDF_LICENSETYPE=SL"

setup.exe /v"FDF_LICENSETYPE=NL FDF_LICENSESERVER=127.0.0.1"


License Server IP Address


The FDF_LICENSESERVER setup property defines IP address of the server where Sentinel Protection Server license manager is installed. In this particular case you also need to set the appropriate licensing type, that is - network licensing. For example:


setup.exe /v"FDF_LICENSETYPE=NL FDF_LICENSESERVER=127.0.0.1"


User Settings Location


The FDF_LOCATION_INI setup property defines location of organization-wise shared settings file. Please keep in mind that if shared settings file is used - common users won't be able to change settings locally. That is, settings become read-only since it's shared among multiple users in a network. For example:


setup.exe /v" FDF_LOCATION_INI=\"\\Server\SharedFolder\settings.ini\""


Windows Firewall Exceptions


The FDF_FIREWALL setup property defines whether setup changes Windows Firewall rules for specific application. This option can be also checked/unchecked via setup UI. Property value can be either 1 (Firewall rules will be changed) or 0 (Firewall rules will not be affected). For example:


setup.exe /v"FDF_FIREWALL=0"


Error Logging To File


The FDF_DEBUG_LOGFILE boolean setup property defines whether errors will get logged to an ASCII file or not. For more details please see Logging to a File. For example:


setup.exe /v"FDF_DEBUG_LOGFILE=1"


Error Logging To Event Log


The FDF_DEBUG_EVENTLOG boolean setup property defines whether errors will get logged to system event log. For more details please see Logging to Event Log. For example:


setup.exe /v"FDF_DEBUG_EVENTLOG=1"


Error Logging To E-mail


The FDF_DEBUG_SMTP boolean setup property defines whether errors will get logged to e-mail using SMTP client. Besides general on/off switch, there's also other available SMTP parameters. For more details please see Logging to E-mail. For example:


setup.exe /v"FDF_DEBUG_SMTP=1 FDF_DEBUG_SMTPHOST=smtp.gmail.com FDF_DEBUG_SMTPPORT=587 FDF_DEBUG_SMTPSSL=1  FDF_DEBUG_SMTPADDRESS=recipient@gmail.com FDF_DEBUG_SMTPUSERNAME=MyUsername FDF_DEBUG_SMTPPASSWORD=MyEncryptedPassword"

setup.exe /v"FDF_DEBUG_SMTP=1 FDF_DEBUG_SMTPPATH=\"\\Server\SharedFolder\""


Max. Number of Cores


The FDF_MAXCORES integer setup property defines maximum number of CPU cores to be used for running parallel computation algorithms. If this variable is set to 0 or to any value larger than available number of processor cores, then maximum number of cores will be used. For example, to constrain number of cores to a single one use:


setup.exe /v"FDF_MAXCORES=1"


To enable utilizing all available cores, use:


setup.exe /v"FDF_MAXCORES=0"


Max. Number of Errors


The FDF_MAXERRORS integer setup property defines maximum allowed number of run-time errors, warnings and informational messages to be fetched within the single application block. Since run-time errors get stored in memory, it's suggested that you keep this number to a reasonable value, like 100.000 errors. If this variable is set to 0, system will automatically scale this value. For example, to constrain number of run-time errors to 1000 use:


setup.exe /v"FDF_MAXERRORS=1000"


To enable system scale this value automatically, use:


setup.exe /v"FDF_MAXERRORS=0"