Jump to content

Ignite

Members
  • Content Count

    11
  • Joined

  • Last visited

About Ignite

  • Rank
    Candidate
  1. Not the answer I was hoping for but thanks for your assistance.
  2. Thanks, but we are not using KSC. We are managing a small workgroup site and we just using command line and local KES interface to manage KES. Is there no way to create a Trusted Zone Scan exclusion using a system variable?
  3. I need to setup a Scan exclusion in Trusted Zone for a folder under the current user's profile: %UserProfile%\Test When I add this path to a new Scan exclusion rule, it gets saved as the resolved path: C:\Users\TechOnline\Test This is shown in the screenshots below. I cannot find how to add a path so that the system variable is retained.
  4. Fantastic, that has fixed it. Thank you so much for your assistance. Kaspersky should update the support article about How to manage KES via the command prompt.
  5. Thanks but that article is not relevant to KES10 SP1 (10.2.4.674). The article shows this command (avp.com ADDKEY C:\XXXXXXXX.key /password=123) and this is what I used previously with version 10.2.1.23(a). When I use that command now I get a prompt "Enter login:" as shown in the screenshot below.
  6. In the past I have operated KES10 from the command line to perform a number of actions, including updating the license key. The command I used was: avp.com ADDKEY C:\XXXXXXXX.key /PASSWORD=123 Now with KES10 SP1 a User name is required and the default value of the user name is: KLAdmin I have tried using this command, but it fails: avp.com ADDKEY C:\XXXXXXXX.key /pKLLOGIN=KLAdmin /pKLPASSWD=123 I have searched Kaspersky support trying to find how to manage KES10 SP1 for Windows workstations via the command prompt, but I have not found any references.
  7. How on earth can Kaspersky call this a business solution with such a hopeless response to a world-wide issue. We are paying for a business solution so we can get business level support & response times that mimise disruption to our business clients. This is simply not good enough & Kaspersky needs to explain why they could not do better.
  8. Sorry folks that was misinformation from one of our techs. The problems are all with KAV6 not KES.
  9. We have the same issue with a number of machines running Kaspersky Endpoint Security 8. Any update on a fix Kaspersky?
  10. Is there any update on this issue? We have had to put a stop on a 500 machine rollout of KES because of this problem. All users are on Google Apps & manually disabling the Outlook add-in is not going to fly as a fix. Kaspersky have promised a fix but I don't see any sign of one being released. How about it Kaspersky, what is happening?
  11. You are correct, it does not help. We have exactly the same problem & we raised this with Kaspersky when Workstation version 6 was first released (it was possible with version 5). At that time the advice from Kaspersky was that it could not be done & I don't think things have changed. Yes it is possible to create an AutoIT script to set the password (we did use one originally when KAV 6 was released), but it is not easy & unless you want to spend a lot of time to develop a sophistocated script to deal with all of the variations across different versions of Windows (we have XP, Vista & 7 in use across 300+ machines), it is not a satisfactory solution. Hoping someone has some better news.
×
×
  • Create New...

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.