Application upgrade when migrating to VMware NSX-T platform

An upgrade consists of the following steps:

1. Removing the components of the previous Kaspersky Security version in VMware virtual infrastructure. The removal procedure is described in Kaspersky Security for Virtualization 6.0 Agentless help.

   When an SVM with the File Threat Protection component is removed, the copies of files that were placed in Backup are automatically deleted.

2. Updating VMware virtual infrastructure to meet Kaspersky Security software requirements and migrating to VMware NSX-T platform (for more information about migration to VMware NSX-T, refer to VMware documentation).
3. Preparing virtual infrastructure managed by VMware NSX-T Manager for installation of Kaspersky Security components.
4. Update of administration plug-ins for Kaspersky Security, Integration Server, and Integration Server Console.
5. Configuring the settings for connecting the Integration Server to one or more virtual infrastructure administration servers.
6. Registering Kaspersky Security services in VMware NSX Manager.
   • If you want to install the File Threat Protection component, you need to register the file system protection service (Kaspersky File Antimalware Protection).
   • If you want to install the Network Threat Protection component, you need to register the network protection service (Kaspersky Network Protection).

   The settings required for registration and deployment of Kaspersky Security services are entered through a Wizard that is started from the Integration Server Console. When you have finished entering the settings, Integration Server registers the Kaspersky Security services in VMware NSX Manager.

   You can verify that Kaspersky Security services are registered successfully in VMware NSX Manager Web Console or in VMware vSphere Client console (depending on the type of VMware NSX Manager you use: VMware NSX-T Manager or VMware NSX-V Manager).

7. Deploying SVMs with Kaspersky Security components and configuring protection settings in the virtual infrastructure.
8. Removing SVMs with the components of the previous application version from Kaspersky Security Center Administration Console. To ensure correct calculation of the licensing restrictions, manually remove SVMs from Kaspersky Security Center Administration Console after the application update is completed.

After the application is updated, prepare it for operation: activate the application on all new SVMs, make sure that the application databases are updated on all new SVMs, and configure the application operation settings by using a policy.

After upgrading the application, you can use policies and tasks configured for the previous Kaspersky Security version. The policies and tasks are automatically converted to the policies and tasks for Kaspersky Security for Virtualization 6.1 Agentless after policy protection settings and task scan settings are edited and saved for the first time.