Jump to content

Alex

Members
  • Posts

    107
  • Joined

  • Last visited

    Never
  1. Hi, Several KES for MAC are reporting infected objects within the Time Machine folder. Are they false positives? Please look at attached images. Can I exclude Time Machine folders from the scans? I mean from the KSC policy.
  2. Thanks Alex. The problem was a manager laptop countdown was almost completed and he was in a call… big problem… because he didn’t restarted the laptop before!
  3. Hi, I configured KES 11.2 (KSC 12) uninstallation task with 90 minutes for computer restart. Is there a way to stop this planned restart? I tried with shutdown -a \\hostname (with domain admin privileges) but I received an error. Cheers,
  4. How is possible that the MAC IP is properly recorded and tasks search the other IP??? There is a way to force DNS update to KSC?
  5. Hi Alexacad, Thanks, I already tried it but all tasks fail. I also configured IP range polling with VPN addresses, found the MAC, added it to the MACs group but tasks fail and I can’t see installed KES and NetAgent…. It's really frustrating! The first is the VPN IP, the second the hostname and the other another MAC.
  6. Hi, I’ve added again a MAC to our MAC-clients group and manually installed on it latest NetAgent and KES for MAC. KSC isn’t able to reach the MAC, ping from server to MAC works fine but if I launch a task there is a wrong hostname resolution to a different IP address. MAC is remotely connected to the VPN and KSC resolve the hostname to a different IP related to the office network. I deleted and updated host’s DNS entries and ping or tracert from server or KSC custom tools are working fine but the problem remains. I can’t see MAC status and every task fails. KSC 11.0.0.11.31 patch B NetAgent 12.0.0.35 KES 11.0.1.753
  7. Try with the app Kaspersky Security Center 11 Remote Diagnostics Utility and if it fail open a ticket to the company support
  8. I already found it and added the IP address, now the hostname but I’m unable to properly open vSphere. Now it’s a Chrome issue not KES. XXXXXXXXXX normally uses encryption to protect your information. When Google Chrome tried to connect to XXXXXXXXXX this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be XXXXXXXXXX, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Google Chrome stopped the connection before any data was exchanged. You cannot visit XXXXXXXXXX right now because the website uses HSTS. Network errors and attacks are usually temporary, so this page will probably work later.
  9. Where are Trusted Domains? I only found Trusted Addresses or Applications.
  10. I read a lot of issues with KSC12, have you detected them?
  11. I hate this way to force users to update KSC! I didn’t noticed it and we’re using KES13 with KSC11 without evident issues… I hope we won’t face compatibility issues
  12. Thanks for the news. Is 11.3 compatible with KSC11? I’m using it without issues
  13. Hi, Are latest NetAgent for MAC 12.0.0.35 and KES 11.0.1.753 fully compatible with KSC 11.0.0.31 B?
×
×
  • Create New...