After it had finished I started going back to the workstations and looking around, and noticed that a few of the workstations weren't under the policy anymore, including my test case from yesterday.Īs seen in my illustration below, when KES updates itself from 10.5 (mr2) to 10.2.4.674 (mr2), it seems to think it is now autonomous, and does not have to submit to the policy. Clearly this thinking is wrong.
I then deployed KES to all 14 workstations using the preconfigured network install package set on "standard". I RDP'd into the 14 policy-less workstations that the users had left on and uninstalled KES. The next day (today) I set out to deploy the same fix and get our network happy again. And it worked! The workstation was happily running under the policy. I set it to "standard" and tested it by uninstalling KES on one workstation and then deploying it again with the Network Agent. I checked our KES network deploy package and sure enough it was set to "custom" with none of the boxes checked. It sounded just like the solution to my issue. I looked around to find a solution and found Ray (Kaspersky)'s answer on SpiceWorks here. I was looking through Kaspersky Security Center the other day and noticed that the KES policy was only being applied to 11 of 33 workstations, but the Network Agent policy was being applied to all 33. Facing an irritating but hopefully simple issue here.