Jump to content

Thomas Becker

Kaspersky Employee
  • Posts

    53
  • Joined

  • Last visited

Reputation

12 Good

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Dear Omid, thank you for your request. As a global company Kaspersky complies with the applicable laws and regulations of the countries in which it operates and distributes its products and services to end users. I will send you a private message with contact details for your inquiry. Have a good day.
  2. Hello and sorry for the late reply. To support you we need to have a deeper look into this. Therefor please open a case with https://CompanyAccount.kaspersky.com Please also add the following infos into the case when creating it: attach a system diagnostic file from the machine where you see this error: https://support.kaspersky.com/3632 Thank you
  3. Hello and welcome to the Forum. there might be different ways to achieve what you want to do, either by blocking chrome.exe completely or by limiting the network for chrome. However, to support you we need to go a bit deeper. Therefor please open a case with https://CompanyAccount.kaspersky.com Thank you
  4. Hello and welcome to the forum there is no connection between B2B and B2C plans. You cannot "migrate" from your Endpoint Security to a home user product. There is no discount when switching from Endpoint Security to any B2C product. You can however go to your reseller and talk to him about this. Maybe is able to grant you a small discount.
  5. Hello and welcome to the Forum. To support you we need to have a deeper look into this. Therefor please open a case with https://CompanyAccount.kaspersky.com Please also add the following infos into the case when creating it: attach a system diagnostic file from the device where you see this error: https://support.kaspersky.com/3632 Make sure that Windows Eventlogs are collected as well Thank you
  6. Hello and welcome, unfortunately this timeout is "hardcoded" in the backend and cannot be changed by the user.
  7. KES12 should be updated automatically starting yesterday when KSN is active. For systems not using KSN the update should begin end of march.
  8. Hello, you can use avp.com to run existing tasks. In short: # "C:\Program Files (x86)\Kaspersky Lab\Kaspersky Endpoint Security for Windows\avp.com" STATUS this shows you all the running tasks and you can start them with: # c:\>"C:\Program Files (x86)\Kaspersky Lab\Kaspersky Endpoint Security for Windows\avp.com" START Updater$ak000043 (change the task number to your own tasknumber) Information to use: Managing the application from the command line https://support.kaspersky.com/KESWin/12.0/en-US/184545.htm More commands can be found here: https://support.kaspersky.com/kes10/how_to/11336 And general information. You can add avp.com to the system variables in the installation package. When you've done this you can just use: # avp.com STATUS
  9. Sorry for the late reply, I missed your comment. To support you we need to have a deeper look into this. Therefor please open a case with https://CompanyAccount.kaspersky.com Please also add the following infos into the case when creating it: attach a system diagnostic file (run as root) from one affected system: # curl -o collect.sh -J -L https://kas.pr/collect.sh && bash ./collect.sh Thank you
  10. Hello, sorry for the late reply. Maybe this link will help you: https://support.kaspersky.com/KSC/CloudConsole/en-US/175982.htm The address https://aes.s.kaspersky-labs.com/endpoints/ is included in managed device firewall exceptions.
  11. Correct. You must first update the utility itself to see new versions. That is due to the fact that the utility itself is not changed upon every new release but the database is.
  12. Hello and welcome to the Forum. To support you we need to have a deeper look into this. Therefor please open a case with https://CompanyAccount.kaspersky.com Please also add the following infos into the case when creating it: Check if the following process is present and also active and running on the main node: "klservercluster" attach a system diagnostic file from the server where you see this error: https://support.kaspersky.com/3632 Thank you
  13. Please open a ticket with https://CompanyAccount.kaspersky.com - we need to have a deeper look at what files are written. Therefor please also add a DirListing like this: 1) Open elevated CMD 2) run this command: dir "FOLDER_PATH" /o:s /s >> c:\filelist.txt Attach the filelist.txt to your new case.
  14. Hi, please make sure you have a valid license in your KSC and on the workstations. Then try finding a solution on these pages: https://support.kaspersky.com/KSC/13.2/en-US/195124.htm and https://support.kaspersky.com/KESWin/11.11.0/en-US/128080.htm On the device itself you can use this Test Utility: https://support.kaspersky.com/kes11/diagnostics/14328 If all this is of no help then please open an incident with CompanyAccount.kaspersky.com and attach the results of the Test Utility.
  15. Hello Bram, welcome to the Forum. In this special case please send your feedback directly via the dashboard of K-ASAP. Scroll all the way to the bottom and find "Roadmap / Request new features (English)" - there you can see our Roadmap and also submit your own ideas.
×
×
  • Create New...