Start or stop application on managed device not working

[Danijel Jovanovic JAPICOM]

Hi,

After an upgrade from KSC 14.2 to 15.1 and upgrade of Network Agents on version 15.1.0.2 i have problem in one enviroment with stoping or starting KES through KSC.

For example, in web console when i go to managed devices and select one managed device, in applications tab i select KES and click on stop, i get an error ''failed to connect to device''.

In mmc console, when i open device and in applications do a right click on KES, start and stop options are greyed out.

Does anyone have a clue what could be a problem?

[KarDip]

Hi @Danijel Jovanovic JAPICOM

This issue could stem from a few common causes when managing Kaspersky Endpoint Security (KES) after upgrading Kaspersky Security Center (KSC) and Network Agents. Here are some possible solutions:

1. Network Agent Configuration: Ensure that the Network Agent configuration settings on the managed devices are compatible with KSC 15.1. In some cases, after an upgrade, specific ports or communication settings may not match the new KSC version requirements. Confirm that the Network Agent is actively connected to the KSC by checking the connectivity status in KSC.

2. Permissions Issue: Sometimes, after an upgrade, the permissions for managing application states, such as starting or stopping KES, may need to be reassigned. Double-check the access permissions in KSC, especially in the MMC console, to confirm that your user role has full control over these actions for KES.

3. Kaspersky Endpoint Security (KES) Policy Settings: KES policies may have restrictions that prevent remote start or stop commands. Review the KES policy settings and ensure that remote management actions are allowed for the managed devices. Adjusting the "Self-Defense" settings may also help if they are preventing KSC from executing these actions.

4. Network Agent Synchronization: After an upgrade, the Network Agent might require a resynchronization with KSC. This can usually be done by forcing a policy synchronization through the KSC console or manually on the affected endpoints.

5. Firewall or Security Software Conflicts: Verify if there are any firewall rules or security software on the network or devices that might be blocking communication between KSC and the managed devices after the update.

If the issue persists, reviewing KSC and KES logs for more detailed error messages might help identify the root cause.

Thank you

[Renan Corassa]

4 horas atrás, Danijel Jovanovic JAPICOM disse:

Oi,

Após uma atualização do KSC 14.2 para o 15.1 e uma atualização dos Agentes de Rede para a versão 15.1.0.2, tive um problema em um ambiente ao parar ou iniciar o KES por meio do KSC.

Por exemplo, no console da web, quando vou para dispositivos gerenciados e seleciono um dispositivo gerenciado, na aba de aplicativos seleciono KES e clico em parar, recebo o erro ''falha ao conectar ao dispositivo''.

No console mmc, quando abro o dispositivo e nos aplicativos clico com o botão direito do mouse no KES, as opções iniciar e parar ficam esmaecidas.

Alguém tem alguma ideia do que pode ser o problema?

Eu tive um problema parecido e era o Network Agent ou a política do KES, não lembro exatamente. Criei um grupo, movi o dispositivo, criei políticas separadas (não herdadas) e testei. Funcionou. Você consegue executar o procedimento e validar? Depois retorno o dispositivo para o grupo original e verifique se o problema persiste. 

Edited November 14 by Renan Corassa

[Danijel Jovanovic JAPICOM]

I found a solution...actually i found my mistake.

I have noticed this issue few days after upgrade, but the thing is that during that period i was configuring connection gateway and distribution point in dmz for mobile device protection and laptops that are going in and out of corporate network. I configured that distribution point for all managed devices instead of just groups for those laptops and mobile devices and in the policy for network agents left enabled to force connection via that connection gateway.

When i configured in connection gateway to act as distribution point just for those groups that it should, problem was resolved and i can start or stop KAS app again.

Tahnks @Renan Corassa and @KarDip for fast reply.