Jump to content

Peter Cauwenbergh

Members
  • Content Count

    2
  • Joined

  • Last visited

About Peter Cauwenbergh

  • Rank
    Candidate
  1. I got this finally fixed with a personal fix (an personal update provided by Kaspersky). there seems to be no other way around it: you need to create a support ticket with Kaspersky support and they will give you a personal fix. Luckally, the personal fix works for avery computer in my domain. I guess it might have something to do with your licensefile that requires them to create a unique fix for each enviroment. Somehow they don't manage to get the fix in a general update... quite dissapointing. But after the personal fix, i have't had any issues anymore.
  2. I Have the same problem on 2 computers (one has outlook 2013 and the ther 2016) in a pool of 125 computers. all other computers seem to have no problem with is. I solved it first by upgradeing from KES 10 to KES 11 but as soon as i configured the policy in the KCS, problem came back. So the reply by Janith seems to make sense. However, this is alomst ONE YEAR after this problem was reported by charbelseif for the first time on this thread... HOWECOME THIS IS'NT SOLVED in the software patches by default? Why do I need to spend hours of time searching for a sollution that shouldn't be a problem in the first place? and even when i find a sollutin, i still need to request a Private Patch??? VERRY DISAPOINTED IN KES!
×
×
  • 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.