Remko
-
Posts
10 -
Joined
-
Last visited
Never
Posts posted by Remko
-
-
We have a similar problem. Prior to the holidays (X-Mas and Happy New Year) we updated the Kasperksy client on all machines.
Now it appears that this problem occurs on computers which have not restarted.
They appear Yellow in de KSC and are pending reboot. For some reason, people are not willing to reboot a machine. As long as the machine is not rebooted, the c:\windows\installer folder is flooded with these 80 MB files.
In some case this now adds up to over 100 GB per machine.
We are now looking for a solution to correct this and cleanup all the orphaned Files.
This is potential a huge problem as all our hardrives are filling up rapidly on our workstations.
-
We will not be pursuing any further detailed investigation at the moment as this is just in a test phase. The message is FYI that we have encountered the issue. No further resolvement is required at the moment. It appears that a new computer object has been created in the KSC and that protection continues via the new computer object.
-
Windows also shows Kasperksy as turned off while Kasperky shows it is on?!?!?! Which one is true?
-
Hi, we are running version 11.0.0.6499 of Kasperksy for Workstations. After I had upgraded my test Windows 10 1803 machine to the latest 1903 May update I noticed that Kasperksy was not running anymore. After I enabled Kasperksy again via the Windows Notification Center I noticed in the KSC that I have now duplicate computer objects as shown in the picture.
We will test with another test machine but thought I should mention this.
-
My estimate is that in approx 5% of the newly deployed machines the problem has occured so far. Some people complain that Outlook stops fetching mail. When we rebuild the OST every thing is back to normal. Others complain that an Outlook add-in crashes. When we investigate, it is Kasperksy as shown above. The biggest problem I have is that I cannot reproduce this. Keep also in mind that it is a software refresh, not a hardware refresh and the OS is not upgraded but newly imaged.
-
Is it possible to update KES to 11.1 version?
I suppose this is possible but will take some time to implement (Management of Change) Are you suspecting Kasperksy as a possible culprit? -
I have noticed that the files have not been downloaded yet. Please be advised that the files will be available till May 15th. Remko
-
As requested: Download link No upload option available?
-
Hi, We are receiving an unusual high amount of failing "Kasperksy for Workstation 11.0.0.6499" Outlook add-in's and corrupt OST files since we have migrated our machines from Windows 7 to Windows 10 and Office Version from 2010 to 2016. We have an on premise Exchange 2013 server and the Kasperksy for Workstation version has remained unchanged. So only the Office version and the OS has changed on the workstations. So far I have not been able to find the culprit. I was wondering if more people experience a failing Kasperksy add-in or if they see higher than usual corruption of the OST files. As the Kasperksy add-in is the only add-in we have in Outlook, my first thought was that perhaps Kasperksy could be a culprit to this. We had negative experiences with this add-in in the past causing very slow Outlook performance.
Outlook disabled the following add-in(s): ProgID: OutlookKLAvPlg.Addin_25135DE3-BB52-4185-9E7D-A72F82E5A224 GUID: {01D7D203-BF4B-4E4E-8DE9-169082FA6386} Name: Kaspersky Outlook Anti-Virus Addin Description: Addin for anti-virus protection Load Behavior: 0 HKLM: 1 Location: c:\program files (x86)\kaspersky lab\kaspersky endpoint security for windows\mcou.dll Threshold Time (Milliseconds): 500 Time Taken (Milliseconds): 531 Disable Reason: This add-in caused Outlook to close slowly. Policy Exception (Allow List): 0
Kaspersky flooding clients with MSI files
in Kaspersky Endpoint Security for Business
Posted
We were upgrading from 11.0.1.90 to version 11.1.1.126.
I also escalated the problem to Kasperksy Suppport. They send me a personal fix last thursday but I need to figure out how to implement this. There is no documentation associated with it.