Start process

You can use the Start process task to remotely start processes and executable files on devices.

For example, you can run:

Processes stopped as a result of malicious activity on the device.
Processes stopped by you.
For example, you can remotely start a process that you have stopped using the Terminating a process task.
Scripts.
For example, you can run a script to collect data from the device to investigate a threat.
Utilities.
For example, you can run a utility that saves device configuration information to a file.
Applications.

If SELinux is installed in your operating system in Enforcing mode, starting the Start process task requires additional configuration of SELinux.

You can create and run a Start process task as well as change its settings in the Web Console or Kaspersky Security Center Cloud Console.

You cannot create, run, or configure the Start process task using the command line. Start process tasks created in the Web Console or Kaspersky Security Center Cloud Console cannot be viewed using the kesl-control --get-task-list command in the command line.

Start process task settings

Setting	Description
Executable command	Field for entering the command to start the process. For example, if you want to run the `klnagchk` tool, which checks the connection to the Administration Server, you need to enter the `/<directory name>/klnagchk` command and then fill in the other fields described in the table below. You can also enter the directory name in the Working directory path (optional) field. In that case, do not enter the directory name in the Executable command field.
Command line arguments (optional)	Field for entering command line arguments to pass additional input to the script, utility, or application at startup. For example, you can enter the `-logfile klnagchk.log` argument. This argument tells the tool to save the result to a file named `klnagchk.log`. If you need to pass multiple arguments, separate them with spaces. For example, you can enter `-logfile klnagchk.log -savecert certificate.cer` arguments. These arguments tell the tool to save the result to a file named `klnagchk.log`, and to save the certificate used to check access to the Administration Server in the `certificate.cer` file.
Working directory path (optional)	Field for entering the path to the working directory where the executable file of the script, utility, or application is located. For example, you can enter `/opt/kaspersky/klnagent64/bin/`. If you entered a directory name in the Executable command field, do not fill in the Working directory path (optional) field.

Setting

Description

Executable command

Field for entering the command to start the process.

For example, if you want to run the klnagchk tool, which checks the connection to the Administration Server, you need to enter the /<directory name>/klnagchk command and then fill in the other fields described in the table below.

You can also enter the directory name in the Working directory path (optional) field. In that case, do not enter the directory name in the Executable command field.

Command line arguments (optional)

Field for entering command line arguments to pass additional input to the script, utility, or application at startup.

For example, you can enter the -logfile klnagchk.log argument. This argument tells the tool to save the result to a file named klnagchk.log.

If you need to pass multiple arguments, separate them with spaces.

For example, you can enter -logfile klnagchk.log -savecert certificate.cer arguments. These arguments tell the tool to save the result to a file named klnagchk.log, and to save the certificate used to check access to the Administration Server in the certificate.cer file.

Working directory path (optional)

Field for entering the path to the working directory where the executable file of the script, utility, or application is located.

For example, you can enter /opt/kaspersky/klnagent64/bin/.

If you entered a directory name in the Executable command field, do not fill in the Working directory path (optional) field.

You can view the result of the task in the Assets (Devices) → Tasks → <task name> section, on the Results tab in the Description column.

Page top