Jump to content

About this blog

Entries in this blog

KSC displays the message "you must install WADK" even if WADK is installed [KSC for Windows]

Problem You install latest Windows Assessment and Deployment Kit (Windows ADK) on the server where KSC is installed, but KSC console still shows message "to deploy OS images, you must install the Windows Assessment and Deployment Kit (Windows ADK) on the device that has KSC installed". Solution KSC doesn't see all the needed WADK components being installed. Because Microsoft is always changing components within their installation packages, we recommend to install all utiliti

svc_kms

svc_kms in Known Problem

How to save server list in MMC Console after upgrade [KSC for Windows]

If you are using the MMC console with different servers, you may want to keep a list of configured servers after upgrading to a new version. Fortunately, this is possible. Step-by-step guide Follow these steps before the upgrade. Save Kaspersky Security Center XX file from C:\Users\%username%\AppData\Roaming\Microsoft\MMC Upgrade. Start and close the MMC console. Remove newly create Kaspersky Security Center XX file from C:\Users\%username%\AppData\Roaming\

svc_kms

svc_kms in How-to

Equality logic in subnet conditions of klnagent connection profiles [KSC for Windows]

Advice and Solutions (Forum Knowledgebase) Disclaimer. Read before using materials. Consider the following scenario: You have a large local area network 10.36.0.0/16. There is a managed device with the following IP config: IPv4 address: 10.36.35.10 and Subnet Mask: 255.255.255.0. You create a new subnet condition for klnagent connection profile: 10.36.0.0/16. Actual result: The connection profile is not applied to the managed device. The reason of this behavior is equali

svc_kms

svc_kms in Known Problem

How to find out the name of an automatically created on installation KSC service account [KSC for Windows]

Description If you need to know the name of the standard KSC service account (KL-AK...) that has been created during installation, it is stored in the registry key. This information can be viewed in the registry, using the following paths: for 64-bit systems: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\KasperskyLab\Components\34\1093\1.0.0.0 for 32-bit systems: HKEY_LOCAL_MACHINE\SOFTWARE\KasperskyLab\Components\34\1093\1.0.0.0 this key is called AutoCreatedS

svc_kms

svc_kms in How-to

KSC: System error 0x52E (Logon failure: unknown user name or bad password) when downloading updates to the repository [KSC for Windows]

Try the following: 1. Check if the Administration Server is configured to use a proxy server on the Kaspersky Security Center server. 2. Try to clear the updates repository. Download the updates once again and check behavior. If you still have issues, Delete the Download updates repository task and create a fresh task.

svc_kms

svc_kms in Known Problem

How to check JS in cases when MMC administration console is not showing data properly [KSC for Windows]

Advice and Solutions (Forum Knowledgebase) Disclaimer. Read before using materials.   In cases when some data is not displayed/shown properly in the MMC administration console, for example, data in the right pane is not displayed properly: One of the most common reasons of such behavior may be blocked/prohibited execution of JS in the Internet Explorer on the host with the console. This can be easily identified by the following test: Step-by-step guide Star

svc_kms

svc_kms in How-to

KSC and ROBOT attack [KSC for Windows]

This article explains ROBOT attack, RSA Key Exchange, OpenSSL and KSC. Explanation If you are running security analyzer and it shows that connections on ports 13000 (server-nagent traffic) and 17000 (activation proxy) are suspicious for a ROBOT attack, don't panic. Automatic analysis is not accurate. Run specific diagnostics to make sure that KSC traffic is actually not vulnerable. Examples: https://testssl.sh/ https://github.com/robotattackorg/robot-det

svc_kms

svc_kms in Known Problem

KSC difference between Application Registry and Incompatible Applications Report [KSC for Windows]

Problem You may run into differences between Application Registry and Incompatible Applications Report when trying to find computers with incompatible applications. For example, you created Device selection based on an Applications registry criteria, where you specified incompatible application name in Application name field and got a device selection of 12 computers. After that, you open Incompatible Applications Report and only get 3 computers with that software. It is expected, and

svc_kms

svc_kms in Known Problem

Fix vulnerabilities task fails with error 'Transaction became the database conflict victim: '1205, ...' [KSC for Windows]

Problem While running Fix vulnerabilities task, the following error can occur: 'Transaction became the database conflict victim: '1205, 'Lock wait timeout exceeded; try restarting transaction' , LastStatement='CALL vapm_arrange_task_updates(119, 0xC89EAD3312227039C9FAC933840D7936)' Solution Most possible, the reason of the problem is that you have Fix vulnerabilities task or tasks with a big number of vulnerabilities that should be fixed inside one task. For example, you scro

svc_kms

svc_kms in Known Problem

How to disable SNMP scan on KSC to minimize network load [KSC for Windows]

To minimize network load, stop receiving error messages related to SNMP scan or to comply with security standards, you can disable SNMP scan completely. Step-by-step guide On KSC server:  Execute: klscflag.exe -pv klserver -fset -n KLSRV_NETSVAN_MAY_USE_SNMP -v 0 -t d Restart network agent service net stop klnagent net start klnagent In case if you need to disable SNMP scan made by UA/DP, then the command will be slightly different:   klscf

svc_kms

svc_kms in How-to

Machines' status doesn't change or events are not registering on Administration server [KSC for Windows]

Advice and Solutions (Forum Knowledgebase) Disclaimer. Read before using materials. KSC13 introduced a feature that limits the frequent publication of events. In the event that the event storage overflows on the Server, the most common event in the storage is calculated, and such events are blocked when published on hosts. Problem: Machines have status "Virus scan wasn't performed for a long time" but the "Virus scan" task was started recently. Events that oc

svc_kms

svc_kms in Known Problem

Computer description field is not updated on KSC console

Problem Computer description may stop updating on KSC console. It may be different from what is set on managed PC in computer properties. Solution If computer description field was changed on KSC side manually it will no be updated again. To enable synchronization with local description you have to delete the computer from managed computers group, then from unassigned, and add it back. In case it did not help check that the following services are enabled (set to automatic sta

svc_kms

svc_kms in Known Problem

Issue with encoding of events transferred to SIEM by the KSC [Kaspersky Security Center]

KSC sends events to SIEM in UTF-8 encoding. If the events received from KSC in the SIEM system look unreadable, for example, like this: Тип приложениÑ: ÐеизвеÑтное приложение\r\nÐаправление: ВходÑщее\r\nПротокол: ICMPv6\r\nСтатуÑ: Разрешено\r\nУдаленныРIt is necessary to configure UTF-8 encoding in the SIEM system itself.

Stan Shpatar

Stan Shpatar in Known Problem

How to restore a device that was deleted from KSC [Kaspersky Security Center]

If you accidentally deleted a device from KSC, you can either wait until the next sync (15 minutes by default), or run these commands in a cmd started as administrator: cd C:\Program Files (x86)\Kaspersky Lab\NetworkAgent klnagchk.exe -sendhb Or this command, if you deleted a device running linux: sudo /opt/kaspersky/klnagent64/bin/klnagchk -sendhb After that the device should reappear in Unassigned devices.

Stan Shpatar

Stan Shpatar in How-to



×
×
  • Create New...