Upgrade of the Protection Server is performed by deploying SVM with the new version of the Protection Server in virtual infrastructure. SVMs are deployed using the Integration Server Console.
You can also deploy SVMs using the virtual infrastructure tools and then configure SVM settings using the klconfig script API manually or using automation tools.
After deploying SVMs with the new version of the Protection Server, you must prepare the Protection Server for operation.
If you are using a licensing scheme based on the number of cores in physical processors on the hypervisors, then after the solution is activated on a new SVM, Kaspersky Security may send Kaspersky Security Center an event indicating that the license restriction has been exceeded. You can ignore this event.
SVMs with the previous version of the Protection Server continue to work on hypervisors. They ensure that the previous version of Light Agents for Linux work on virtual machines that have not yet been updated, and ensure that the previous version of Light Agents for Windows work if you are using Kaspersky Security for Virtualization 5.2 Light Agent to protect virtual machines with Windows guest operating systems.
If you have updated all Light Agents for Linux and are not using Kaspersky Security for Virtualization 5.2 Light Agent, you can remove SVMs running the previous version of Protection Server on hypervisors. SVMs are removed using the Integration Server Console or manually using hypervisor tools.
SVMs that have been removed continue to be displayed in the Administration Console of Kaspersky Security Center. When the period specified in Kaspersky Security Center settings elapses (see Kaspersky Security Center help for details), the SVMs are automatically removed from the Administration Console.
You can manually remove SVMs with the previous version of the Protection Server from the Administration Console of Kaspersky Security Center as soon as the upgrade process has been completed.
Page top