Hello, this is by design of the cloud product. You can only use syslog. regards

Hello, this will only work in conjunction with a password setting in KES Policy. Goto General Settings in your Policy and "Interface". Then set a Password for KES. Default is User KLAdmin (case sensitive). Thank you in advance Best Regards

@Insatisfação Bem-vindo Peço que por favor entre em contato com o suporte técnico → Suporte Técnico Somente eles podem auxiliar nos casos de compras e reembolsos.

@AureBIt Bem-vindo Verifique se ela está logada e conectada a conta My Kaspersky no Kaspersky VPN. Ainda assim, caso o problema persista, por favor entre em contato com o suporte técnico → Suporte Técnico

Hello, it seems the client was not rebooted or no connection since reboot. In this case you can ignore the message and close it when the client is successfully installed and rebooted and properly shown by cloud management console Best Regards

@garioch7 I am glad you have stated that 'Malwarebytes is not a true anti-virus'. This is one major reason I run MBam and Kaspersky side by side. As I stated on the MBam forum (as BeeGeemb, it fills in any possible holes missed by either MBam or K. (I have a legacy license for MBam). After reading your response on the MBam forum I enabled the Real-time protection on MBam and have seen NO issues arise from that action. As of this writing both are running just fine with no warning pop-ups from either program. Other then the little notice within the Dashboard of K, (which I can ignore) all seems to be well. Should I go back and remove Real-Time Protection to prevent a slow-down?? I've not really noticed a slow down.

Hello Jean, using Remote Access Software needs probably changing an option in your Policy. Please open your policy, navigate to general settings and Self-Defense. Disable the option " Block external management of system services". Wait until the policy is taken over and retry Thank you in advance Best Regards

Настравиваем мониторинг узлов KSMG 2.1 по snmp. Почему-то snmpwalk (и мониторинг, соответственно) не показывает часть данных snmp, которая находится в ветке 1.3.6.1.4.1.2366.1735.1. Здесь находятся данные о состоянии кластера (согласно mib). В конфиге snmpd.conf указана вся ветка с Касперским: view monitoring included .1.3.6.1.4.1.23668.1735 В выводе snmpwalk только ветка 1.3.6.1.4.1.2366.1735.2 # snmpwalk -v3 -l authPriv -u snmpmonitor -a SHA -x AES -A "aaa" -X "xxx" 127.0.0.1 .1.3.6.1.4.1.23668 SNMPv2-SMI::enterprises.23668.1735.2.1.1.0 = Counter64: 5 SNMPv2-SMI::enterprises.23668.1735.2.1.2.0 = Counter64: 58269 SNMPv2-SMI::enterprises.23668.1735.2.2.1.0 = Counter64: 6155 ... ... SNMPv2-SMI::enterprises.23668.1735.2.12.4.0 = Counter64: 0 SNMPv2-SMI::enterprises.23668.1735.2.12.5.0 = Counter64: 0 SNMPv2-SMI::enterprises.23668.1735.2.12.6.0 = Counter64: 1 SNMPv2-SMI::enterprises.23668.1735.2.12.6.0 = No more variables left in this MIB View (It is past the end of the MIB tree) Подскажите, пожалуйста, с чем такое может быть связано?