You first go one step back from there and in the lower part add profile. That profile should point to other KSC server or connection gateway network agent. After that you go there in network location, select your new profile and configure conditions when to use that profile. You have in documentation about that, just search for conection profiles. Thats not out of office policy, that is something else. Out of office policy is activated when network agent cant reach KSC server 3 times.

При обработке входящего письма KSMG корректно проверяет DKIM (статус pass в заголовке X-KSMG-AntiSpam-Auth), но при передаче письма дальше (re-inject в Postfix) ломает синтаксис тега b= в DKIM-Signature. Проблема наблюдается на длинных ключах (2048 бит, Mail.ru). KSMG вставляет лишнюю точку с запятой (;) или некорректный разрыв строки внутрь хеша подписи, делая письмо невалидным для следующих узлов. Пример заголовка X-KSMG-AntiSpam-Auth подтверждает, что на входе подпись была валидна. Версия 3.0.0.9059

Hi, the idea of creating two separated KESs and point agents to the second one is really great, i would like if there's actually documents about that scenario. Is that out of office configuration from network agent profile ?

Hello @eina, Thank you for the information! IF the *update* errors persist - READ & follow *all* of: General recommendations for solving database update issues in Kaspersky applications. Uninstall Kaspersky Premium using Windows -> Add or remove programs & READ: How to uninstall the application in Windows 8 or later - in the check-boxes that appear - Save subscription *only*, leave all other check-boxes clear - at the end of the *uninstall* of Kaspersky Premium shutdown the computer using SHUTDOWN, not Restart, when the computer is OFF, power ON by pressing the power button, log in. Download a new Kaspersky Premium installer from (your) MyKaspersky account OR https://www.kaspersky.com/downloads#update-product, install Kaspersky Premium, run a manual Database update -> *make sure it's successful*? Recheck the Arknights: Endfield and OR Duet Night Abyss issue, IF *either* persist log a request with Kaspersky Customer Service, https://support.kaspersky.com/b2c#contacts -> select Email, then fill in the template as shown, include a *detailed history*. Support may request logs, data & traces, they will advise you. *Note - don't use the AI-bot to submit the case* Please share the outcome with the Community, when it's available? Thank you🙏 Flood🐳+🐋

Была точно такая же ошибка. Полностью вылечилась вот этими командами: DISM /Online /Cleanup-Image /ScanHealth DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow

@Markus Yes, it will work.

Добрый день. Если у вас есть лицензия на любой коммерческий продукт Лаборатории Касперского, обратитесь в техподдержку. В противном случае попробуйте создать тему на форуме Клуба лаборатории Касперского, выполнив порядок оформления запроса о помощи.

That worked! I've updated to NetAgent version 16.1 and now the Reg is edited! Now... as in your screenshot, the key will be made under "WOW6432Node", and with the "/reg:64" argument, it'll change the 64bit registry: echo Adding to registry (located under "HKLM\SOFTWARE\WOW6432Node\") reg add "HKLM\SOFTWARE\_test_32" /v "test" /d "1" /t "REG_DWORD" /f echo Adding to registry (located under "HKLM\SOFTWARE\") reg add "HKLM\SOFTWARE\_test_64" /v "test" /d "1" /t "REG_DWORD" /reg:64 /f Thanks a bunch!!