Nikolay Arinchev

Hi, I observed some times that KES 11 for Windows policy (now is only one!) seems to be not properly applied as if the clients use a different policy Could you please provide us with an export of active policy and with screenoshot of settings thet are not applied corretly. Please notice, that ‘locks’ at policy settings should be locked in order to correctly apply correspondin policy settings. Thank you!

You can import computer structure from AD by right-click at Managed computer properties - all tasks - New Group structure and create a stucture at AD basis. Thank you!

Здравствуйте, Пожалуйста, ожидайте ответ в рамках заведенного инцидента. Спасибо!

Hi, Could you please clarify what updates exactly you are trying to install? Is it KES updates? Thank you!

Unfortunately, there are no files attached.

Thank you for that info! For further investigation please provide us with GSI log(https://support.kaspersky.com/common/diagnostics/3632) from admin server host.

Could you please provide us with an export of active policy or KES settngs(*.cfg)? Thank you!

Здравствуйте, Уточните, пожалуйста, после того, как активация слетает, активируется ли продукт при добавлеии ключа? Используете ли вы KSC? Как настроено распространение ключей - автоматически или задачей? Спасибо!

Hi, Could you please clarify what shared folder exactly was changed? Is it KLShare? What exactly was done to change it`s location? Thank you!

Hi, Have you tried to add that address to trusted at Web-AV settings? Thank you!

Device Parent ID will work kaspersky ? I`m not sure I understood you correctly. Could you please rephrase you question? Thank you!

Пожалуйста, удалите все обновления из папки, которая выбрана как источник обновления и загрузите их повторно. Пожалуйста, сообщите о результате. Спасибо!

Hi, What version of KSC do you use? Thank you!

For further investigation please provide us with Admin server update task traces ($up2date-1103.log and $up2date-1103-eka.log — update task trace files). Unfortunately, these files are ascent. Could you please re-download them to file sharing resource? Thank you!

Have you tried to run active directory polling? Thank you!

Пожалуйста, приложите к своему ответу скриншот ошибки. Спасибо!

Hi, Both ways should work to delete KES. Also, please refer to the article that describes migration process - https://support.kaspersky.com/13121#block1 Thank you!

Could you please provide us with ping utility output or screenshot? Thank you!

I`m sorry for my mistake. The correct name is “Distribute instalation package”.

How can I create a task without a package previously created? I’m not aware of this. Please open task creation wizard - Click New - Create installation package for user specified program - select patch`s exe file - wait for installation package to be created and follow task creation wizad to create remote installation task.

Hi, Could you please clarify that admin server account(KL-AK***) has corresponding permissions at DC? Thank you!

Спасибо за информацию. Согласно System event log ‘The processing of Group Policy failed. Windows attempted to read the file \\spb.tprogress.local\sysvol\spb.tprogress.local\Policies\\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following: a) Name Resolution/Network Connectivity to the current domain controller. b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller). c) The Distributed File System (DFS) client has been disabled.” Пожалуйста, убедитесь, что доменные службы Active Directory работают корректно. Спасибо!

Hi, Could you please confirm that 13000,14000TCP ports are opened and KSC could be successfully pinged from that host? Thank you!

Hi, Please notice that issue happens when attempting to download KES 11.2 upgrade patches. DB update should run successfully no matter the task ends up with an error and security of the hosts is not affected. Root cause of the issue is already discovered and we are now waiting for R&D to provide a fix. We will provide further updates in this post. Thank you!

Спасибо за информацию! Пожалуйста, приложите к своему ответу отчет GSI с сервера администрирования. Спасибо!