We just recently upgraded our Admin kit from version 6 to 8 and have since had an issue with workstations trying to run version 6.0.4.1212. Everything seems to work except the workstation doesn't keep the license key for more than half a minute. If you point it again from the the workstation directly to the license key file, it takes it initially but just flips back to showing as unlicensed... what did we miss?

Thanks!

Rather than point the Client to the license key have you tried running a Deploy License file task from the admin kit to those clients? Also, did you include the license to your 6.0.4.1212 installation package? Go to your packages and look at the properties, under the license tab it should show your license info. You can go in and select the license that you've installed on your admin kit.

I've tried using the 'Deploy License file' task and it says it's successful but the user's install still shows as not being 'activated' and therefor is not able to update. The install package was indeed missing the license file, so I added it in, re-saved the install package and deployed it but it's doing the exact same thing.

Does this possibly have something to do with the MP4 version or upgrade? Do we need to change anything in the admin kit to work with 'MP4'?

If my memory serves me correctly, upon initial installation of the Admin Kit 8, you go through a wizard (first time you run Admin Kit 8). One of the questions is to setup an automatic task that distributes the license to all nodes. I could imagine your problematic behaviour if that task was created, but with the wrong (or no) license file. That would explain why your PC's revert back to 'no/incorrect license' after a number of minutes has passed: the automatic task that should keep your licenses in order has run (and, actually, broken your licenses on the PC's).

This is not the case here though - when Admin Kit 8 was installed, it didn't update all users so we must have skipped that task creation. This is only happening when we try to deploy the latest version of Kaspersky workstation (6.0.4.1212) which we've created a new deployment 'Installation Package' for. The older version (6.0.3.867) deploys okay and works. I've found that the same issue occurs regardless of which version of the Kaspersky Network agent is installed - (6.0.1591 or 8.0.2048).