LogRhythm Joins Lockheed Martin Cybersecurity Alliance

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.

Solution 2

Install a patch labelled “private fix 96 (pf96)” on the computers that are affected. This solution posed two issues:

• A patch needs to be requested through a support ticket, who has the time or energy to deal with technical support ONLY to request a patch? Plus previous encounters with Kaspersky support wasted days of my time and I ended up troubleshooting and solving the problem myself.
• It will need to be installed on a per client basis, given I was managing 20+ computers that would be a massive headache to implement.

Conclusion

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.

Related articles across the web