ElvinE5

try running the command from the problematic device tnc <IP address KSC> -port 17000 it should be something like this

тут наверное обращение в СА с выгрузкой всех необходимых дампов поможет быстрее ... порты действительно открыты ? tnc <IP контроллера домена> -port <порт>

when you click on the link... https://keyfile.kaspersky.com/en/ you should be taken to this page where does it redirect you? Yes, to activate the application with a code, the device needs Internet access. However, check the connection from these servers to your KSC on port 17000... it is used precisely for activation when the client does not have the Internet and the server does... https://support.kaspersky.com/KSC/14.2/en-US/158830.htm Try contacting your solution provider, they should help you obtain the key files from your activation code. When using key files, device access to the Internet is not required.

Все работает ... https://support.kaspersky.com/KSCLinux/15/ru-RU/257877.htm настройки опроса ... пользователь с правами в домене ... ну и запустить после настройки

Small addition... with 15 KSC the old MMC (14.2) does not work yet...

only if you use the Syslog method https://support.kaspersky.com/KSC/14.2/en-US/151330_1.htm

4. :))) I think I understand what's going on with you, I'll assume that you click here... and get your picture It’s funny I didn’t pay attention to this before, I can’t tell if it’s a bug or a feature :)) try this... profit... :))) 3. The 15th version of KSCL was recently released Distributions have already appeared today ... I think you will be interested in the addition of useful functionality - for example, AD polling, which did not exist in 14.2 ...

1. probably a limitation of the web console... the item still remains in the tasks ... one since there is no context menu, sending this command in the same way is not possible ... in principle, you can connect an MMC console in your Linux KSC https://support.kaspersky.com/help/KSCLinux/15/en-US/230088.htm in this console it looks a little different and you won’t see the usual tree like in MMC, you kind of follow the link by clicking on the group that you need... and on the right side you should see the devices that are located in it I hope you have become familiar with the functionality of KSCL before switching to using this version of the management server ... since it does not yet support all KSCW functions https://support.kaspersky.com/KESB/14.2/en-US/228569.htm

Since you are using SQLExpress, one of the reasons may be that the database is full; Experess has a 10GB limit. Check the current size of the default database, it is called KAV Check the server events; you may see errors in operation there. check the availability of backups (and their size may also indicate that the limit has been exceeded) I think it will be easier for you to restore the system from a backup on a new server with the current version of KSC (currently 14.2), and update your clients, rather than on the old platform (2008) and KSC 12 trying to solve the problem.

Консоль всегда ставится отдельно ... 1. соберите пакет из дистрибутива что скачали, это должен быть архив такого вида ... 2. соберите пакеты для установки KSWS и консоли ( да это разные пакеты) - https://support.kaspersky.ru/ksc14/install/10625#block4 по первому и второму пункту, MSI для консоль в папке client, KUD файл для пакета KSWS в папке сервер. что значить не формируются ? подробнее можно ? какие-то ошибки или что ? тема начиналась как проблема обновления KSWS - этот вопрос вы решили ? если у вас ... чаще всего помогает просто переустановка клиента KSWS

the first thing that could be is that Proxm is not included in the supported platforms (compatibility has not been checked quickly) https://support.kaspersky.com/KSC/14.2/en-US/255791.htm the second is that KSC also does not support such migration options and any kind of snapshot recovery. The correct transfer method is to restore the system from a backup taken by the KSC server itself You just need to set up a new server in your new environment and try restoring it from backup. https://support.kaspersky.com/KSC/14.2/en-US/236441.htm during such a transfer, make sure that when deploying a new server, its IP, server FQDN, as well as the SQL platform used (MSSQL, MardiDB, Postgres), the database name (what you specified during the first deployment) coincide with the previous ones otherwise, if the name of the database and platform form differs from the original, the system will not be restored from backup. and if the IP or FQDN is different (depending on how your agents are connected), client devices will not be able to connect to the restored server... and they will have to be reconnected... separately or if it is not possible or you do not want to restore from a backup, the server can be fully deployed and configured again and reconnect clients to it using the “change administration server” task

Обсуждение немного другой проблемы ... но тоже с сломанными задачами обновления ... натолкнуло на одну мысль. @Maxmud Fayziev попробуйте одно проблемное устройство удалить из управляемых устройств, а потом и из нераспределенных. Это должно обнулить все групповые задачи на устройстве (удалить). Подождите, периода синхронизации, когда устройство вновь появится в группе нераспределенных и верните его в туже группу где он был. Проверьте задачу обновления.

https://support.kaspersky.ru/ksc11/troubleshooting/error/10665 ну и присоединяюсь к @tyazhelnikov

Если ни чего не путаю ... то на сервере KSC %ProgramData%\KasperskyLab\adminkit\1093\cert лежат все сертификаты, в пакете агента укажите сертификат klserverksc PS: Ну или как вариант просто пересоздать сам пакет агента, из "сырого" дистрибутива

It looks like you have again chosen a key to activate the devices; according to your picture, the number is different... That's what I mean, when you add both files to the repository... then the one you need should be called something like this if you don’t have such a key, contact your supplier, the one who provided you with trial licenses... I think he can help

Это отдельная консоль для сервера ... как GUI интерфейс для KES, его нужно поставить отдельно на сервер ... и уже там смотреть ... если скачивали дистрибутив с сайта (полный дистрибутив) ...то в архиве должен быть каталог либо при запуске выбрать пункт...

judging by the picture you have Total, this is enough to use the management functionality... however, you only have one key file...the one that activates the security solutions themselves on clients (KES, KSWS, etc.) you need a second key file...for KSC ... they can be supplied together in an archive... ask your colleague what else they gave him with the trial version... perhaps an activation code... then everything can be activated with it or get the keys from it on the manufacturer’s website... https://keyfile.kaspersky.com you must have many keys since the Total package includes many products that can be activated... along with the keys there should be a text file describing which key can activate what... something like this

там просто тоже плагин не стоит .... но там именно web нужен

так там свои плагины web ... с этими не связаны... можно попробовать удалить их из установленных ... https://support.kaspersky.ru/ksc14/uninstall/9303 но у меня с Linux 11.4 после этого вышла проблема ... не могу установить этот плагин повторно удалил 11.0 и с ним улетел и 11.4 после сего могу тольк 11.3 поставить ...обновить до 11.4 или установить начисто не выходит ...

what version of KSC server do you have? Removing and reinstalling the Web console did not help? Try clearing your browser cache add your server to the list of trusted servers to verify certificates...

ok a few steps... 1. You have added a license to the repository, look at its name... 2. if the license is different from Basic, to activate the functionality (management) in the properties of the administration server, add a server key... then SIEM integrations (CEF, LEEF) will become available to you you need the key on the server (you must have two files), or if you activated with an activation code...specify it 3. If the license is still Basic, then integration with SIEM is still available to you... but only via the Syslog protocol However, for this integration you will have to manually select ALL events that you want to send to SIEM

Порверьте все что вам советовали выше ... и не забудьте про валидность ваших лицензий на серверах и конечных устройствах ...

Trial versions are not limited in functionality except for the time of use... Tell me what product license you have. Basic, Advanced, Optimum, Total, etc. and in what variation do you use it... internal server - https://support.kaspersky.com/KSC/14.2/en-US/5022.htm cloud - https://support.kaspersky.com/Cloud/1.0/en-US/187780.htm or cloud console - https://support.kaspersky.com/KSC/CloudConsole/en-US/5022.htm

check on the target machine whether everything really applies to it and all other settings including traffic decryption

я имел в виду что к головному серверу подключены KSWS машины ? они нормально обновляются ? проблема только с KSWS что на подчерненном ? опробуйте классические решения ... 1. Пересоздать задачи загрузки обновлений (да да да 🙂 ), все задачи как обновление в хранилище так и для клиентов. 2. очистить хранилища от баз (на обоих серверах если надо) и повторить загрузку 3. переустановить клиента KSWS ... 4. Попробовать закачать обновления KUU и все же проверить возможность обновления из папки ... в настройках укажите локализацию и параметр LangNone