Kaspersky Security Center is a great tool to manage several PCs from a server where you can manage, monitor, scan for viruses, update, etc… from one control panel installed on the server. However, recently I have hit the problem below even though I scanned the workstations several times.
After endless head banging and googling, I was able to find a solution which we will explore in this post.
It turns out that there is a bug/defect in Kaspersky Endpoint Security that only affects the version I was using (10.1.0.867) that but was fixed in Kaspersky Endpoint Security 10 MR1 (version 10.1.249) and above as explained in the link below:
As the page above suggests there are two solutions if I wanted to stay at the current version of 10.1.0.867:
Disable the Inherit option and then the Not scanned for a long time option in the Set computer status to Critical and Set computer status to Warning sections in the group properties. This was not a favourable option in my case since I do consider an unscanned PC as a critical event. Plus this solution merely downgrades the severity of the event not so much resolves the underlying issue.
Install a patch labelled “private fix 96 (pf96)” on the computers that are affected. This solution posed two issues:
At this point in time, the latest stable version is 10.2.1.23 which can be downloaded from the link below and contains the fix for that defect:
The fix is mentioned in the “Kaspersky Endpoint Security 10 for Windows Workstations Maintenance Release 1 (version 10.2.1.23) release info”
Incorrect status Not scanned for a long time after a full scan.
I then created a distributive package using the exe installer in Kaspersky Security Center and launched the remote installation across all the workstations. Sure enough after the new version was installed and running a full scan on all the PCs, the status went from “critical” to “Ok” as seen below:
If you have any problems, questions, or concerns please leave a comment below.