This error may be caused by non-Latin characters in the policy name.
To fix this issue, check existing policy and place it with a new one, if it has non-Latin characters in its name:
1. In the NSX web console: Navigate to Security → Endpoint Protection Policies.
2. Delete the existing policy with Non-Latin characters in its name.
3. Create a new policy using English-only naming conventions.
Problem
Error Failed to get IP addresses for connecting to SVM appears during SVM deployment.
Solution
To troubleshoot this problem, you need to follow our step-by-step guide:
I. Disable SVM rollback
Go to C:\Program Files (x86)\Kaspersky Lab\Kaspersky VIIS Console\ for KSV LA 5.1 or to C:\Program Files (x86)\Kaspersky Lab\Kaspersky VIISLA Console for KSV LA 5.2
Edit the Kaspersky.VIISConsole.UI.exe.config file
Uncomment <!--<add key="disable
Problem Description, Symptoms & Impact
Network security assessment tools detect multiple vulnerabilities in the SVMs.
Workaround & Solution
Below is a list of detected vulnerabilities and solutions or reasons why it can't be fixed.
Open ports
SVMs have ports 22 and 80 open for communication with the Deployment Wizard and providing updates to Light Agents respectively. They are hardcoded, and therefore can't be changed or closed without at least partially breaking
Description and cautions
This article describes how to install a patch on multiple SVMs at once via Kaspersky Security Center.
Details
Create an installation package from a .kud file included with the patch
Advanced → Remote installation → Installation packages → Create installation package
Choose Create an installation package for a Kaspersky application
Choose a name for the package
Select the .kud file in the file pick
Problem:
Create Group On Demand Scan Task of Windows Kaspersky Light Agent 5.2/Linux Kaspersky Light Agent 5.2
Launch Group On Demand Scan Task
Group On Demand Scan Task of Windows Kaspersky Light Agent 5.2/Linux Kaspersky Light Agent 5.2 might detect infected object, but might not delete it.
Solution:
Delete created Group On Demand Scan Task of Windows Kaspersky Light Agent 5.2/Linux Kaspersky Light Agent 5.2
Delete all created Windows Kaspersky Light
Prerequisetes:
Supported vSphere by Kaspersky Agentless solution
Usage of NSX version 3.2+
Deployed Kaspersky Agentless 6.1 Antivirus or/and Network Attack Blocker Appliance
Problem
Anew registration and Kaspersky Agentless 6.1 Antivirus or/and Network Attack Blocker Appliance deployment completes successfully.
By attempt to create Service Profile for Kaspersky Agentless 6.1 Antivirus or/and Network Attack Blocker fails with error
AntiVirus and Network Attack service regi
Problem Description
Unexpectedly it can be observed that KSV AL 6.1 starts to be unavailable in Kaspersky Security Center as shown on the screenshot.
Root cause
The most probable cause of this issue is expired Kaspersky Security Certificate and new generated one is not transferred to KSV AL 6.1.
KSV AL 6.1 does not have functionality to automatically update certificate from Kaspersky Security Center.
Workaround
The script klmover should be launched on KSV AL
Problem:
When deploy the SVM of KSV LA on the vSphere 6.5, the following error may occur:
Reason：
This issue occurs because vCenter Server cannot detect any vSAN storage provider. There is no way to detect vSAN storage provider if no hosts are available when vCenter Server starts.
Note: vSAN storage provider cannot be recognized automatically even after host start working properly.
Workaround:
This is a known issue affecting vCenter Server.
To workaround
Officially exclusions from protection against external encryption are written on this page https://support.kaspersky.com/KSVLA/5.2/en-US/175626.htm
Starting from 07/06/2022 it is possible to add exclusions from protection against external encryption using "Exclusions" tab under "Exclusions and trusted applications" settings.
Steps:
Go to "Exclusions and trusted applications" settings and move to "Exclusions" tab
Add folder/filename (masks are supported) specifying Syst
SNMP daemon on SVM should have the following default settings:
protocol version: v2c
rocommunity name: public
listening address and port: 0.0.0.0:161
access type: read only
transport: UDP
logging: syslog
The following statistics can be received from SVM:
#
Description
Name
Identifier
Problem
Environment:
Citrix Virtual Apps and Desktops (Citrix XenApp and XenDesktop) with enabled option Citrix UPL (User Personalization Layer)
Citrix App Layer
Non-English Operation System localization.
After installation of KSV LA 5.2, you can face the error "The specified path does not exist" which appears by launching any executable file.
Possible root cause
Both Citrix technologies use separate vhd files for creating VMs by using Citrix App Lay
ATTENTION! All mechanisms described below will be applicable to all further released Cumulative Patches for Kaspersky Linux Light Agent 5.2.
On-Demand Scan exclusion mechanism has not been changed. The following mechanism of exclusions with installed Cumulative Patch for Kaspersky Linux Light Agent 5.2 is applicable to On Access Scanning only.
1. File Scanning Exclusion (an exclusion does not end with ‘/’)
If the option "Include subfolders" is enabled for exclusions fro
The symptoms of the issue are:
Installation/upgrade of KSV LA 5.2
vSphere Virtual Machine is unresponsive after KSV LA 5.2 installation
Based on the investigation results the problem related to NSX Introspection Drivers coming with VMware Tools. There is the article about it: https://kb.vmware.com/s/article/78016
Solution:
The best option is to uninstall NSX File Introspection and NSX Network Introspection by modifying VMware Tools on a virtu
Please note that Kaspersky Light Agent 5.2 has been passed basic test scenarios on Windows Server 2022 and Windows 11.
Currently KSV LA 5.2 supports installation on Windows Server 2022 and Windows 11.
Problem
Error Failed to get IP addresses for connecting to SVM appears during SVM deployment.
Solution
To troubleshoot this problem, you need to follow our step-by-step guide:
I. Disable SVM rollback
Go to C:\Program Files (x86)\Kaspersky Lab\Kaspersky VIIS Console\ for KSV LA 5.1 or to C:\Program Files (x86)\Kaspersky Lab\Kaspersky VIISLA Console for KSV LA 5.2
Edit the Kaspersky.VIISConsole.UI.exe.config file
Uncomment <!--<add key="disable
