Archive for the ‘kaspersky’ Category

Kaspersky Anti Virus Policy Not Enforced…….

Thursday, June 24th, 2010

Following the renewal of our Kaspersky anti virus products for another 12 months, the friendly sales person was also kind enough to point out that the license entitled us to upgrade to the lat[er|est] version, and that the new version supported Windows 7.

Sold !

We were previously running Administration Kit version 6 (6.0.1710) and were pushing out Anti Virus 6 for Workstation (6.0.3.837) to Vista desktops. That particular version of the client would not work under Windows 7, it would cause an exception and the process/service would shutdown (Windows kept going though, well done MS).

During a period of performance issues experienced last year, I had to dial back most of the Kaspersky features and functionality under Vista. The ‘Web Protect’ component increased some page load times to well over a minute if there were a lot of links on a page. And the ‘Proactive Defense’ component (which watches and protects the registry) would fire up so many alerts that just launching any approved application would result in so many popup alerts it resembled one of those naughty web sites with boobs all over them that hi-jack your screen with popups !

So all the components of the Anti Virus application were installed, but the Kaspersky policies were used to deactivate the bits causing problems. The only components left enabled were the ‘File Anti-Virus’ and the ‘Anti-Spy’ features. All the others components were unchecked.

I decided to create a new server instance and install the updated version cleanly onto it rather than upgrade the in place install. This gave me the luxury of migrating computers across to the new version in a more relaxed manner, and also leaving behind any bugs/isssues with the existing version on the old server.

So the new versions now in play are Administration Kit 8 (8.0.2090) and Anti Virus 6 for Workstation MP4 (6.0.4.1424). I have no idea what the MP4 stands for (if anything).

This time, I decided to save time and resources, I would only install the anti virus package components we wished to use, namely file and spyware scanning. So I attempted to modify the package as shown below

av package components

However, it became apparent that when the application was pushed out to the client something was not quite right. No matter what I tried, the policy for the workstation was not being applied. I tried removing and re-installing the AV client, but it did not change anything. Many google searches later did not return anything definative or useful (hence my writing this blog post, maybe someone else also tried to save a bit of disk space and found that their policies no longer worked !?!?).

So I went back to defaults and put all the components back into the package and re-deployed to the workstation. This had the effect that the policy was now being detected and applied to the workstation ?!? So now I just go in and modify the policy to deatcivate the protection components I am not using as per the previous version.

av component configuration

Happy to report that the new MP4 version of the AV client works fine under Windows 7 for both x64 and x86 bit, as well as Vista. CPU and memory utilisation would appear to be greatly reduced (the avp.exe process on my workstation is using a little under 17MB).

I am a little miffed that I had to install all the package components onto the workstation in order for policies to work (especially as I then just use those policies to deactivate over 75% of the products features !).

In summary, if you are having trouble with Kaspersky policies not being applied to AV workstation clients, check to see if you removed any of the components from the deployment package, it may be a factor.

Kaspersky NDIS 6 Filter Causes Network Loss…..

Wednesday, August 19th, 2009

We use Kaspersky for anti virus in the office. It’s an ok product, no better or worse than any others I have worked with. It did however turn out to be the cause of an issue that I was unable to figure out for a while now.

On x64 bit Vista systems, when moving large files across the network, the PC would suddenly loose it’s network connection. The network icon in the system tray would get a little yellow warning triangle on it and the status would indicate a connectivity issue.

It did not do this on systems that did not have kaspersky installed how ever. So I tried disabling the x2 Kaspersky services (anti virus and network agent). While this made the problem happen less, it did not go away completely, if I copied x3 or x4 large files (2gb+ in size each) at the same time, the network connection would drop again.

The problem was made even worse because there was no way to get the connection back without restarting the machine. Disabling and re-enabling the interface did not work, using netsh to reset the interface and winsock also did not work. The machine would become unstable and need a power cycle in the end.

I thought perhaps it was being caused by using bad network interface card drivers, so I downloaded the latest ones from the vendor web site but still the connection dropped under heavy load.

And then I spotted it. while checking the driver details for the network interface. kaspersky had added a protocol stack component that I knew nothing about, the ‘kaspersky NDIS 6 filter’.

kaspersky ndis 6 filter

kaspersky ndis 6 filter

Checking on the kaspersky site, it seems that this is a network level embedded packet interceptor. as packets arrive and leave the network card interface, the NDIS driver intercepts them for scanning to try to determin if the packet contains malicious content. It would seem that under heavy network load, the intercepts become too much and it trashes the network stack beyond repair.

Disabling this component by clearing it’s checkbox and unbinding it from the network stack seems to have fixed the issue and I was able to copy x8+ large files (2GB+) simultaneously without any connection issue. It also seems to have corrected a more minor issue I was experiencing with system pauses when network operations were happening.

I hope this helps anyone else having these issues.