Silent install of Deep Security Manager

Applies to on-premise Deep Security software installations only

Run a silent install readiness check

You can run the installer in readiness check mode to make sure your environment is ready for the Deep Security installation. Nothing will be installed but the installer will create reports about your installation environment, which you can use to fix any issues before actually installing Deep Security Manager.

To initiate a silent readiness check on Windows, open a command prompt in the same directory as the install package and run:

Manager-Windows-<Version>.x64.exe -q -console -Dinstall4j.language=<ISO code>-varfile <PropertiesFile> -t

To initiate a silent readiness check on Linux, use the command line to go to the same directory as the install package and run:

Manager-Linux-<Version>.x64.sh [-q] [-console] -t [-Dinstall4j.language=<ISO code>] [-varfile <PropertiesFile>]

Run a silent install on Windows

To initiate a silent install on Windows, open a command prompt in the same directory as the install package and run:

Manager-Windows-<Version>.x64.exe -q -console -Dinstall4j.language=<ISO code> -varfile <PropertiesFile>

Run a silent install on Linux

Before executing this command, grant execution permission to the installation package.

To initiate a silent install on Linux, use the command line to go to the same directory as the install package and run:

Manager-Linux-<Version>.x64.sh [-q] [-console] [-Dinstall4j.language=<ISO code>] [-varfile <PropertiesFile>]

Parameters

-q forces the installer to execute in unattended (silent) mode.

-console forces messages to appear in the console (stdout).

-Dinstall4j.language=<ISO code> lets you override the default installation language (English) if other languages are available. Specify a language using standard ISO language identifiers:

  • Japanese: ja
  • Simplified Chinese: zh_CN

-varfile <PropertiesFile> , where <PropertiesFile> is the full path to standard Java properties file with entries for the various settings you can apply during a Deep Security Manager install. Each property is identified by its equivalent GUI screen and setting in the Windows Deep Security Manager installation. For example, the Deep Security Manager address on the "Address and Ports" screen is specified as:

AddressAndPortsScreen.ManagerAddress=

Most of the properties in this file have acceptable defaults and may be omitted.

For a complete description of available settings, see Deep Security Manager settings properties file.

-t runs an installer readiness check rather than a regular install.

Sample properties file

This is an example of the content of a typical properties file:

AddressAndPortsScreen.ManagerAddress=10.xxx.xxx.xxx
AddressAndPortsScreen.NewNode=True
UpgradeVerificationScreen.Overwrite=False
LicenseScreen.License.-1=XY-ABCD-ABCDE-ABCDE-ABCDE-ABCDE-ABCDE
DatabaseScreen.DatabaseType=Microsoft SQL Server
DatabaseScreen.Hostname=10.xxx.xxx.xxx
DatabaseScreen.Transport=TCP
DatabaseScreen.DatabaseName=XE
DatabaseScreen.Username=DSM
DatabaseScreen.Password=xxxxxxx
AddressAndPortsScreen.ManagerPort=4119
AddressAndPortsScreen.HeartbeatPort=4120
CredentialsScreen.Administrator.Username=masteradmin
CredentialsScreen.Administrator.Password=xxxxxxxx
CredentialsScreen.UseStrongPasswords=False
SecurityUpdateScreen.UpdateComponents=True
SecurityUpdateScreen.Proxy=False
SecurityUpdateScreen.ProxyType=""
SecurityUpdateScreen.ProxyAddress=""
SecurityUpdateScreen.ProxyPort=""
SecurityUpdateScreen.ProxyAuthentication="False"
SecurityUpdateScreen.ProxyUsername=""
SecurityUpdateScreen.ProxyPassword=""
SoftwareUpdateScreen.UpdateSoftware=True
SoftwareUpdateScreen.Proxy=False
SoftwareUpdateScreen.ProxyType=""
SoftwareUpdateScreen.ProxyAddress=""
SoftwareUpdateScreen.ProxyPort=""
SoftwareUpdateScreen.ProxyAuthentication="False"
SoftwareUpdateScreen.ProxyUsername=""
SoftwareUpdateScreen.ProxyPassword=""
SoftwareUpdateScreen.ProxyAuthentication="False"
RelayScreen.Install=True
SmartProtectionNetworkScreen.EnableFeedback=False