Advice and Solutions (Forum Knowledgebase) Disclaimer. Read before using materials. There are multiple settings in both KES and KSC that allow to set notifications about various events. This article is based on example of setting complaint notification (message send to administrator if the users considers the blocking of the page to be mistaken). Let's review three main scenarios, when KES is connected to KSC (either constantly or intermittently) and when it is not connected. KES is always connected to KSC How to set To set address for email notifications go to Administration Server properties -> Notification delivery settings -> Notification and input email into Recipients filed. To enable email notifications do the following Open KES policy Navigate to KES policy -> Event notification -> Warning -> Web page access blockage message to administrator Press Properties Mark Notify by email checkbox What to expect Once the user will fill the form (way to change default complaint message will be covered later in this article) and press Send, Network agent will send event to KSC. Once KSC will receive it, email notification will be send to administrator. The default email will look like this: Event "%EVENT%" happened on computer %COMPUTER% in the domain %DOMAIN% on %RISE_TIME% %DESCR% %EVENT%, %COMPUTER%, %DOMAIN%, %RISE_TIME% are self explanatory, while %DESCR% may rise some questions. This part will be substituted the whole message that the user put in to the complaint form. You can change format of the email at Administration Server properties -> Notification delivery settings -> Notification. Note that it will affect all email notifications KES in not connected to KSC How to set Open KES GUI Navigate to Settings -> Endpoint control -> Web Control and press Templates Switch to Message to administrator tab Input address for notifications into To field Change Subject of the email and notification text if required. Open General Settings -> Interface -> Notifications Settings configure SMTP client connection settings in "Email notification settings" menu of Notifications. What to expect Once the user will fill the form (way to change default complaint message will be covered later in this article) and press Send, KES will send email to specified address. It will contain everything user put into the form. KES is connected to KSC from time to time How to set Follow the steps described in KES is always connected to KSC section. This will set KES for the time it has connection to KSC Do the same as described in KES is not connected to KSC with only difference – make changes to policy not KES local settings. This will set KES for the time when it is not connected to KSC: Open KES policy Navigate to Endpoint control -> Web Control and press Templates Set email address that will receive notifications when KES is not connected to KSC Change Subject of the email and notification text if required. What to expect When KES has connection to KSC you will receive message from KSC described in KES is always connected to KSC section. When KES has no connection to KSC you will receive email from KES described in KES is not connected to KSC section. The same goes for cases when out-of-policy is used. How it works As noted earlier, when you manage KES using Kaspersky Security Center you can specify two methods of email notification delivery, both of them could be configured in KES policy. KSC settings Open KES policy properties navigate to “Event configuration”, select event that you are interested in, mark “Notify by email” In this case, network agent transport will be used to deliver notification to KSC, then KSC will send an email to specified recipients. If you tracing KES activity, specialized information will be recorded in KES.version.date.time.PID.connector.log and KES.version.date.time.PID.SRV.log for each event sent by Nagent transport. KES settings Open KES policy, General Settings -> Interface -> Notifications Settings, leave tick marks in column "Notify by email" next to events that you are interested. Also you will have to configure SMTP client connection settings in "Email notification settings" menu of Notifications. In this case, KES will send emails using it’s own mail client, from computer where event was registered. KES actions will be recorded in KES.version.date.time.PID.SRV.log

I have a total subscription, and one device is supported, and when I added a new device it is not accepted . A device named Moth And my e-mail address is *****@*****.tld Please resolve as soon as possible

Да, галочки стоят. Политика активна.

It is working now, i did not change anything on my side. So not sure why i was getting that message.

Hallo, meine Kaspersky Passwort Manager Erweiterung funktioniert nicht. Das Icon ist rot und beim drauf klicken soll ich Kaspersky Passwort Manager für meinen PC herunterladen. Ist aber bereits auf dem System. Windows 10 Pro Version 22H2 Kaspersky Passwort Manager Version 24.0.0.428 (a) / 1712576387_7582 / 1.1.0.2_1 Browser Opera GX Version LVL5 (core: 107.0.5045.89) (Standard Sachen wurden gemacht Programme neu installiert und Erweiterung auch) Danke im Voraus.

@Александр 128, давайте проверим такой момент в начале, у вас используется значение "Добавить домен в исключения" для опции "В случае возникновения ошибки при проверке защищенного соединения" https://support.kaspersky.ru/kes-for-windows/12.2/175124 в настройках KES? Если нет, то установите его и попробуйте пару раз подключиться консолью, в идеале бы перезагрузить ОС.

Согласен, что версии уже не актуальны. Но проблема актуальна. При попытке запустить консоль выходит сообщение как на рисунке 0, при нажатии "ок" выходит сообщение как на 1 рисунке. Далее жму "да" и ошибка как на 2 рисунке. Проблема началась еще когда KSC 13 версии был. Пробовал переустановить консоль, но проблема сохранялась. Получилось запустить консоль путем приостановки защиты KES. Так и жил. Хочется исправить проблему.

В этом году пройдёт Архипелаг 2024 и среди прочего СПбГУ делает киберимунный квадрокоптер для соревнований. Киберимунность его заключается в добавлении модуля на KasperskyOS (плате Rpi4) который контроллирует, что квадрокоптер делает то, что задумано. Принять за идентификатор квадрокоптера в системе ОРвД уникальный серийный номер платы казалось самым простым решением, но т.к. такого серийника нет, то вероятно будут использоваться назначенные номера. Подробнее о квадрокоптере можно посмотреть на youtube.