Applies to Kaspersky Anti-Virus 8.0 for Windows Servers Enterprise Edition
By default, the task Scan critical areas is scheduled to run daily. Kaspersky Anti-Virus scans objects located in critical areas of an operating system:
- autorun objects,
- boot sectors and hard/removable drives MBR,
- system and processor memory
- files in system folder, e.g. \system32.
Kaspersky Anti-Virus uses security settings level Recommended.
According to default settings, System audit log registers an event “Critical areas have not been scanned for a long time” if this task has not been finished (e.g. was started but interrupted) for 30 days.
This time interval can be changed in Kaspersky Anti-Virus properties – right-click Anti-Virus Console node Kaspersky Anti-Virus, invoke the command Properties and modify the value Critical areas have not been scanned for a long time on the tab Advanced:
If Kaspersky Anti-Virus 8.0 for Windows Servers Enterprise Edition is managed via Kaspersky Administration Kit, you can assign another task to be deemed as a critical areas scan task. It can be either a local Kaspersky Anti-Virus task (created via Anti-Virus console or Kaspersky Administration Kit console), or a group / global task.
It can be done in properties of a scan task created via Kaspersky Administration Kit or during creation of a new task in Kaspersky Administration Kit by enabling the option Task performance is considered as scanning of critical areas.
Enabled option Task performance is considered as scanning of critical areas makes Administration server register an event Critical areas scan executed and refreshes server status after executing such a task. This option is inactive in Anti-Virus console. It can be checked in task settings via Kaspersky Administration console only.
It is impossible to check/uncheck the box Task performance is considered as scanning of critical areas in Anti-Virus console. But you can see its status in the properties of the task Scan critical areas in Anti-Virus console: