Configuring general application settings via the Application Console

General settings and malfunction diagnostics settings for Kaspersky Security for Windows Server establish general operating conditions. These settings allow you to control the number of working processes used by the application, enable recovery of Kaspersky Security for Windows Server tasks after an abnormal termination, maintain the log, enable creation of dump files of Kaspersky Security for Windows Server processes after abnormal termination, and configure other general settings.

Application settings cannot be configured in the Application Console if the active Kaspersky Security Center policy blocks changes to these settings.

To configure Kaspersky Security for Windows Server settings:

1. In the Application Console tree, select the Kaspersky Security node and do one of the following:
   • Click the Application properties link in the results pane of the node.
   • Select Properties in the node context menu.

   The Application settings window opens.

2. Configure Kaspersky Security for Windows Server general settings according to your preferences:
   • The following settings can be configured on the Scalability and interface tab:
     • In the Scalability settings section:
       • Maximum number of working processes that Kaspersky Security for Windows Server can run
         

         Maximum number of active processes

         Setting	Maximum number of active processes
         Description	This setting belongs to the Scalability settings group in Kaspersky Security for Windows Server. It sets the maximum number of active processes that the application can run simultaneously. Increasing the number of processes running in parallel increases file scanning speed and improves the fail-safety of Kaspersky Security for Windows Server. However, if the value of this setting is too high, it may reduce general protected device performance and increase RAM usage. In Kaspersky Security Center Administration Console, you can change the Maximum number of active processes setting only for Kaspersky Security for Windows Server installed on a stand-alone protected device (using the Application settings dialog box). You cannot modify this setting in the policy settings for a group of protected devices.
         Possible values	1 – 8
         Default value	The application handles scalability automatically, depending on the number of processors on the protected device: Number of processors Maximum number of active processes 1 1 1< number of processors < 4 2 4 or more 4

       • Number of processes for Real-Time Server Protection
         

         Number of processes for Real-Time Protection

         Setting	Number of processes for real-time protection
         Description	This setting belongs to the Scalability settings group in Kaspersky Security for Windows Server. Using this setting you can specify a fixed number of processes in which Kaspersky Security for Windows Server will execute Real-Time Server Protection tasks. A higher value will increase the scan speed in Real-Time Server Protection tasks. However, the more processes Kaspersky Security for Windows Server uses, the greater its impact on the general performance of the protected device and RAM usage. In Kaspersky Security Center Administration Console, you can change the Number of processes for real-time protection setting only for Kaspersky Security for Windows Server installed on a stand-alone protected device (using the Application settings window). You cannot modify this setting in the policy settings for a group of protected devices.
         Possible values	Possible values: 1-N where N is the value specified using the Maximum number of active processes setting. You can set the Number of processes for real-time protection setting equal to the maximum number of active processes. This reduces the impact of Kaspersky Security for Windows Server on the data exchange rate between the devices and the protected device. This will further improve Real-Time Server Protection performance. However, update tasks and On-Demand Scan tasks with Medium (Normal) priority will be executed in Kaspersky Security for Windows Server processes that are already running. On-Demand Scan tasks will be executed more slowly. If the execution of a task causes an abnormal termination of a process, it will take more time to restart it. On-Demand Scan tasks with Low priority are always executed in a separate process or processes.
         Default value	Kaspersky Security for Windows Server handles scalability automatically depending on the number of processors on the protected device: Number of processors Number of processes for real-time protection =1 1 >1 2

       • Number of working processes for background On-Demand Scan tasks
         

         Number of processes for background On-Demand Scan tasks

         Setting	Number of processes for background on-demand scan tasks
         Description	This setting belongs to the Scalability settings group in Kaspersky Security for Windows Server. You can use this setting to specify the maximum number of processes which the application will use to run On-Demand Scan tasks in the background mode. The number of processes specified by this setting is not included in the total number of Kaspersky Security for Windows Server processes specified by the Maximum number of active processes setting. For example, if you specify the following values: Maximum number of active processes – 3; Number of processes for Real-Time Server Protection tasks – 3; Number of processes for background On-Demand Scan tasks – 1; and then start Real-Time Server Protection tasks and one On-Demand Scan task in background mode, the total number of kavfswp.exe processes of Kaspersky Security for Windows Server will be 4. Several On-Demand Scan tasks can be running in one process with low priority. You can increase the number of processes, for example, if you run several tasks in background mode in order to allocate a separate process for each task. Allocating separate processes for tasks increases the reliability and speed of task execution.
         Possible values	1-4
         Default Value	1

   • In the Interaction with user section, select whether the System Tray Icon will be displayed in the taskbar after each application start.
   • The following settings can be configured on the Security and reliability tab:
     • In the Self-defense section, configure protection of application processes.
       

       If the Protect application processes from external threats check box is selected, the application protects its processes against code injection or accessing of processes data.

       When enabling or disabling the option, no need to restart the application services for changes to apply.

       The option is enabled by default.

     • In the Self-defense section, configure the settings for password-protection for the application functions.
     • In the Password protection settings section, specify the number of attempts to recover an On-Demand Scan task if it crashes.
       

       Task recovery

       Setting	Perform task recovery
       Description	This setting belongs to the Password protection settings group in Kaspersky Security for Windows Server. It enables recovery of tasks if they terminate abnormally and defines the number of attempts to recover On-Demand Scan tasks. When a task crashes, the kavfs.exe process of Kaspersky Security for Windows Server attempts to restart the process the task was running at the time of the crash. If task recovery is disabled, the application does not restore the Real-Time Server Protection and On-Demand Scan tasks. If task recovery is enabled, the application attempts to restore the Real-Time Server Protection tasks until they are started successfully. The application also tries to restore On-Demand Scan tasks using the number of attempts specified in the setting.
       Possible values	Enabled / disabled. The number of attempts to recover On-Demand Scan tasks: 1–10.
       Default value	Task recovery is enabled. The number of attempts to recover On-Demand Scan tasks: 2.

   • In the Recover on-demand scan tasks no more than (times) section, specify actions that Kaspersky Security for Windows Server performs after switching to UPS power.
     

     Use of an uninterruptible power supply

     Setting	Recover on-demand scan tasks no more than (times)
     Description	This setting determines the actions that Kaspersky Security for Windows Server performs when the protected device switches to an uninterruptible power supply.
     Possible values	Run or do not run On-Demand Scan tasks to be started according to a schedule. Perform or stop all active On-Demand Scan tasks.
     Default value	By default, if an uninterruptible power supply is used to power the protected device, Kaspersky Security for Windows Server: Does not run On-Demand Scan tasks that run according to a schedule. Automatically stops all active On-Demand Scan tasks.

   • On the Scan settings tab:
     • Restore file attributes after scanning
       

       When Kaspersky Security for Windows Server performs on-demand scan tasks, the time when each scanned file was last accessed is updated. After the scan, Kaspersky Security for Windows Server resets the time when the file was last accessed to the initial value.

       This behavior can affect the work of backup systems by causing creation of backup copies for files that haven’t been changed. This can also cause false detections in file change tracking applications.

       By default, this option is enabled.

     • Limit CPU usage for scanning threads
       

       Kaspersky Security for Windows Server limits its use of the protected device CPU during on-demand scan tasks to the value specified in the Upper limit (in percents) field.

       Enabling of this option can negatively affect the performance of Kaspersky Security for Windows Server.

       By default, this option is disabled.

       • Upper limit (in percents)
         

         Maximum allowable value of CPU utilization by Kaspersky Security for Windows Server.

         The entry field is available if the Limit CPU usage for scanning threads option is selected.

     • Folder for temporary files created during scanning
       

       Folder into which Kaspersky Security for Windows Server needs to unpack archive files during scanning.

       By default, the C:\Windows\Temp folder is used.

   • On the Connection settings tab:
     • In the Proxy server settings section, specify the proxy server settings.
     • In the Proxy server authentication settings section, specify the authentication type and details required for authentication on the proxy server.
     • In the Licensing section, indicate whether Kaspersky Security Center will be used as a proxy-server for application activation.
   • On the Malfunction diagnosis tab:
     • If you want the application to write debug information to a file, select the Write debug information to trace file check box.
       • In the field below specify the folder in which Kaspersky Security for Windows Server will save trace files.
       • Configure the level of detail of debug information.
         

         This drop-down list lets you select the level of detail of debug information that Kaspersky Security for Windows Server saves to the trace file.

         You can select one of the following detail levels:

         • Critical events – Kaspersky Security for Windows Server saves information only about critical events to the trace file.
         • Errors – Kaspersky Security for Windows Server saves information about critical events and errors to the trace file.
         • Important events – Kaspersky Security for Windows Server saves information about critical events, errors, and important events to the trace file.
         • Informational events – Kaspersky Security for Windows Server saves information about critical events, errors, important events, and informational events to the trace file.
         • All debug information – Kaspersky Security for Windows Server saves all debug information to the trace file.

         A Technical Support representative determines the detail level required to resolve any issues that arise.

         The default level of detail is set to All debug information.

         The drop-down list is available if the Write debug information to trace file check box is selected.

       • Specify the maximum size of trace files.
       • Specify the maximum number of files for one trace log. Kaspersky Security for Windows Server will create up to the maximum number of trace files for each component to be debugged.
       • Specify the components to be debugged.
         

         A list of codes indicating Kaspersky Security for Windows Server components for which the application saves debug information in the trace file. Component codes must be separated by a semicolon. The codes are case sensitive (see table below).

         Kaspersky Security for Windows Server subsystem codes

         Component Code	Name of component
         *	All components.
         gui	User interface subsystem, Kaspersky Security for Windows Server snap-in in Microsoft Management Console.
         ak_conn	Subsystem for integrating Network Agent and Kaspersky Security Center.
         bl	Control process, implements Kaspersky Security for Windows Server control tasks.
         wp	Work process, handles anti-virus protection tasks.
         blgate	Kaspersky Security for Windows Server remote management process.
         ods	On-Demand Scan subsystem.
         oas	Real-Time File Protection subsystem.
         qb	Quarantine and Backup subsystem.
         scandll	Auxiliary module for virus scans.
         core	Subsystem for basic anti-virus functionality.
         avscan	Anti-virus processing subsystem.
         avserv	Subsystem for controlling the anti-virus kernel.
         prague	Subsystem for basic functionality.
         updater	Subsystem for updating databases and software modules.
         snmp	SNMP protocol support subsystem.
         perfcount	Performance counter subsystem.

         The trace settings of the Kaspersky Security for Windows Server snap-in (gui) and the Kaspersky Security for Windows Server Administration Plug-in for Kaspersky Security Center (ak_conn) are applied after these components are restarted. The trace settings of the SNMP protocol support subsystem (snmp) are applied after the SNMP service is restarted. The trace settings of the performance counters subsystem (perfcount) are applied after all processes that use performance counters are restarted. Trace settings for other Kaspersky Security for Windows Server subsystems are applied as soon as the crash diagnostics settings are saved.

         By default, Kaspersky Security for Windows Server logs debug information for all Kaspersky Security for Windows Server components.

         The entry field is available if the Write debug information to trace file check box is selected.

     • If you want the application to create a dump file, select the Create crash dump file check box.
     • In the field below, specify the folder in which Kaspersky Security for Windows Server will save the dump file.

     Kaspersky Security for Windows Server does not send any trace or dump files automatically. Diagnostics data can only be sent by a user with the corresponding permissions.

     Kaspersky Security for Windows Server writes information to trace files and the dump files in unencrypted form. The folder where files are saved is selected by the user and is managed by the operating system configuration and Kaspersky Security for Windows Server settings. You can configure access permissions and allow only required users to access logs, trace files, and dump files.

3. Click OK.

Kaspersky Security for Windows Server settings are saved.

Page top