You can centrally install application components in non-interactive (silent) mode, which means without the interactive input of installation settings. For non-interactive centralized installation, you must use special settings when you run the application components centralized installation script kics4net-deploy-<application version number>.bundle.sh.
You must prepare an installation settings file for non-interactive centralized installation. You can prepare an installation settings file by using the script kics4net-deploy-<application version number>.bundle.sh.
To prepare a centralized installation settings file using the script:
The installation settings file named inventory.json is saved in the /home/<user>/.config/kaspersky/kics4net-deploy/ folder (the application components will not be installed).
After preparing the centralized installation settings file, you can centrally install the application components in non-interactive mode.
During centralized installation of application components in non-interactive mode, there is no validation of the checksums of packages in the folder containing the saved files from the distribution kit. You can verify the checksums of packages by completing steps 1–4 of the installation procedure prior to starting centralized installation of components in non-interactive mode.
To centrally install application components in non-interactive mode:
bash kics4net-deploy-<
application version
>.bundle.sh --silent-mode
silent-mode
enables non-interactive installation mode (mandatory parameter).
In addition to the mandatory parameter, you may also add the following parameters for running the installation script:
-i <
path to the installation settings file
>
indicates the full path and name of the centralized installation settings file. If the setting is not defined, the inventory.json file located in the /home/<user>/.config/kaspersky/kics4net-deploy/ folder is used.--enable-debug-grpc-server
– installs a debug gRPC server. This gRPC server is used for testing purposes and is not required for normal use of the application.If the script is run with the --enable-debug-grpc-server
parameter, the application will lose its certified state.
After you enter a script run command, the screen will prompt you to enter the password of the user running the centralized installation.
SSH password
prompt and then in the BECOME password
prompt.The centralized installation script will begin the installation of components. During installation, the screen will display service messages regarding operations being completed.
Wait for completion of the script kics4net-deploy-<application version number>.bundle.sh.
Page top