Jump to content

Actarus

Members
  • Posts

    11
  • Joined

  • Last visited

    Never

Posts posted by Actarus

  1. Hello, I’ve found it: the setting is into the policy.

    This is an inherited policy, created onto the master server and inherited to my slave server (and from here to kes clients). This policy is locked, so I cannot activate the setting I need.   I tried creating a local copy of the policy, so that I can activate my setting, but when I disable inheritance on my new local policy, it seems to revert to something default, loosing a lot of settings I’d like to keep “alive”. 

    I’d like to keep all of those settings except the one I must change :-)    Perhaps I want too much :-)

    I am going to ask to enable my setting on the “master” policy :-) Perhaps this is the solution...

    Sorry for my bad English :-)

  2. Hello, Can you help me? I searched over the other conversations, but haven’t found a solution to my issue.

    KSC with connected clients: in case of virus detection no popups are displayed on client computers.

    Windows notifications are enabled correctly, I even tried enabling all of them, but no way: no popup window notification (I’m testing this issue using Eicar, no real infection.

    Have you ever come into this issue? 

    P.S.: Windows 10 rev. 21H1

    Thank you very much.

  3. Hello, sorry for my bad English. I am here because I need help about Ksc11. My problem is this: ksc does not send notifications regarding virus detected on clients. The events into the policy are configured to send an email (and the mail test is ok:, I receive the test email) when a virus is detected . I have tried running eicar test virus: the result is that the file eicar.com is deleted by the antivirus, but with no notification on the client, and ksc do not send any mail showing the event. Can you help me? Theank you very much.
  4. Hello, sorry for my bad English. Can someone help me? We moved our KSC server from an old domain to the new one. Everything went ok, but... When we install KSP to new clients, the agent tries to connect to KSC using the old server name, example: ksc.olddomain.net instead of ksc.newdomain.net To bypass this problem, on every new client, after the Agent installation, we launch the command klmover -address ksc.newdomain.net Theere must be something wrong in KSC settings, we searched, but IMHO everything is ok, the name and domain specified are correct... Have you any ideas? Thank you very much.
×
×
  • Create New...