Deploying SVMs using the Integration Server Console

If you use the Integration Server Console, SVMs are deployed using the SVM Management Wizard, which is launched from the Integration Server Console.

Following the instructions of the SVM Management Wizard, you need to configure the wizard's connection to the virtual infrastructure, specify all the SVM deployment settings, and start the deployment.

Information about SVM deployment results is displayed in the last step of the wizard.

Before deployment, you need to download the SVM images and SVM image description files.

To deploy SVMs using the Integration Server Console:

1. Open Integration Server Console and connect to the Integration Server.
2. In the SVM management section, click the SVM management button to start the SVM Management Wizard.
3. Follow the wizard instructions.

Selecting an action

At this step, choose the SVM deployment option.

Proceed to the next step of the wizard.

Selecting infrastructure for SVM deployment

At this step, you need to select the virtual infrastructure in which you want to deploy the SVM. If SVM deployment was not previously performed in this virtual infrastructure, you need to configure the connection of the SVM Management Wizard to the virtual infrastructure. Then select the hypervisors or OpenStack projects for SVM deployment depending on the type of virtual infrastructure.

To configure the connection of SVM Management Wizard to the virtual infrastructure:

1. Click the Add button.
2. In the Virtual infrastructure connection settings window that opens, specify the following settings:
   • Type

     Type of virtual infrastructure object that SVM Management Wizard will connect to.

     Depending on the type of virtual infrastructure, select a hypervisor, virtual infrastructure administration server, or Keystone microservice.

   • Protocol

     Protocol used to connect SVM Management Wizard to the virtual infrastructure. By default, the HTTPS protocol is used.

     The Protocol field is displayed if you are configuring a connection to a virtual infrastructure based on the OpenStack platform, VK Cloud platform or TIONIX Cloud Platform.

   • Addresses

     Addresses of the virtual infrastructure objects that SVM Management Wizard will connect to.

     Depending on the type of virtual infrastructure, you need to specify the hypervisor address or the address of the virtual infrastructure administration server. To connect to an OpenStack-based infrastructure, you need to specify the address of the Keystone microservice.

     The address can be specified as the IP address in IPv4 format or the fully qualified domain name (FQDN).

     You can specify multiple addresses by separating them with a semicolon, a space, or a new line. The number of correctly recognized addresses is shown under the list of addresses.

     In this field, you can also specify the port used to connect to the virtual infrastructure object in the format <IP address>:<port>.

     If you are configuring a connection to Microsoft Windows Server (Hyper-V) hypervisors that are part of a hypervisor cluster managed by the Windows Failover Clustering service, you can specify the address of the cluster. All hypervisors that are part of the cluster will be added to the list.

     If you are configuring a connection to VMware ESXi hypervisors managed by VMware vCenter Servers running in Linked mode, you can specify the address of any of these VMware vCenter Servers. All the hypervisors running on VMware vCenter servers in Linked mode will be added to the list.

     If you are configuring a connection to hypervisors that are managed by Microsoft SCVMM, you can specify the settings for connecting to Microsoft SCVMM. All hypervisors that are managed by Microsoft SCVMM will be added to the list.

     If you are configuring a connection to an infrastructure managed by Nutanix Prism Element, you need to specify the Nutanix Prism Element address. If the infrastructure is managed by Nutanix Prism Central, specify the Nutanix Prism Central address. All Nutanix Prism Element servers managed by Nutanix Prism Central will be added to the list.

   • OpenStack domain

     Name of the

     OpenStack domain

     An OpenStack domain is a collection of OpenStack accounts, groups of infrastructure objects, and projects in virtual infrastructures based on OpenStack (including infrastructures based on the VK Cloud platform or TIONIX Cloud Platform). Each account belongs to a particular OpenStack domain.

     that contains an account used to connect SVM Management Wizard to the virtual infrastructure object.

     The OpenStack domain field is displayed if you are configuring a connection to a virtual infrastructure based on the OpenStack platform, VK Cloud platform or TIONIX Cloud Platform.

   • User name

     Name of the user account that the SVM Management Wizard uses to connect to the virtual infrastructure during SVM deployment, removal and reconfiguration. This account must have privileges that are sufficient for SVM deployment, removal and reconfiguration.

     If you use a domain account to connect to a virtual infrastructure object, you can specify the account name in the <domain>\<user name> or <user name>@<domain> format.

   • Password

     Password of the user account that the SVM Management Wizard uses to connect to the virtual infrastructure during SVM deployment, removal and reconfiguration.

3. If you are deploying SVMs in a virtual infrastructure based on XenServer, VMware vSphere, KVM, Proxmox VE, Basis, Skala-R, HUAWEI FusionSphere, Nutanix Acropolis, OpenStack, Alt Virtualization Server, Astra Linux, Numa vServer, VK Cloud platform, or TIONIX Cloud Platform, to connect the Integration Server to the virtual infrastructure while Kaspersky Security is running, we recommend using an account that has limited rights to perform actions in the virtual infrastructure. Select the Account with restricted permissions check box and specify the settings of the user account that the Integration Server will use to connect to the virtual infrastructure during operation of Kaspersky Security.

   If the check box is cleared, during Kaspersky Security operation the Integration Server will connect to the virtual infrastructure using the same user account that is used for SVM deployment, removal and reconfiguration.

   In a virtual infrastructure running on the Microsoft Hyper-V platform, you can connect to the virtual infrastructure during Kaspersky Security operation only by using the same user account that is used for SVM deployment, removal and reconfiguration.

4. Click the Connect button.

   The Virtual infrastructure connection settings window closes. The Wizard adds the selected virtual infrastructure objects to the list and attempts to establish a connection.

   The Wizard verifies the authenticity of all virtual infrastructure objects with which the connection is established.

   Authenticity is not verified for a Microsoft Windows Server (Hyper-V) hypervisor.

   For Keystone microservices, authenticity is verified only when using the HTTPS protocol to connect the SVM Management Wizard to the virtual infrastructure.

   To verify authenticity, the Wizard receives the SSL certificate or fingerprint of the public key from each virtual infrastructure object and verifies them.

   If the authenticity of the received certificate(s) cannot be established, the Verify certificate window opens with a message about this. Click the link in this window to view the details of the received certificate. If the certificate complies with the security policy of your organization, you can confirm the authenticity of the certificate and continue connecting to the virtual infrastructure object. The received certificate will be installed as a trusted certificate on the device where the Kaspersky Security Center Administration Console is installed. If you do not consider this certificate to be authentic, click the Cancel button in the Verify certificate window to disconnect, and replace the certificate with a new one.

   If the authenticity of the open key could not be established, the Verify public key fingerprint window opens with a message about this. You can confirm the authenticity of the open key and continue the connection. The open key fingerprint will be saved on the device where the Kaspersky Security Center Administration Console is installed. If you do not consider this open key to be authentic, click the Cancel button in the Verify public key fingerprint window to terminate the connection.

   If a connection cannot be established with a virtual infrastructure object, information about the connection errors is displayed in the table.

The table displays information about the virtual infrastructures to which connections are configured in the SVM Management Wizard. If SVMs are already deployed in the virtual infrastructure, the table also contains information about them. Each row of the table displays a hierarchical list of virtual infrastructure objects and the following information:

• Name/Address

  Depending on the type of virtual infrastructure, the column may contain the following:

  • IP address or the fully qualified domain name (FQDN) of the virtual infrastructure administration server
  • IP address or the fully qualified domain name of the hypervisor
  • IP address or the fully qualified domain name of the Keystone microservice
  • Name of the OpenStack domain
  • Name of the OpenStack project
  • Name of the SVM deployed on the hypervisor

  If SVM deployment is restricted, or if a connection with the virtual infrastructure cannot be established, the warning icon is displayed. A description of the restriction or connection error is shown in the table and in the tooltip of the warning sign.

• State

  This column contains information on the state of the virtual infrastructure object or the SVM.

  For the hypervisor, one of the following values is specified: Enabled or Disabled. If a connection to the hypervisor cannot be established, the column shows Disconnected.

  For the Keystone microservice, the OpenStack project, and the OpenStack domain, one of the following values is specified: Enabled or Disconnected.

  One of the following values is specified for an SVM: Enabled, Disabled.

• Protection

  This column contains the SVM version number.

• Type

  This column contains the type of virtual infrastructure object that the SVM Management Wizard will connect to.

You can search the list of virtual infrastructure objects based on the Name/Address column. The search starts as you type in the Search field. The table displays only those virtual infrastructure objects that meet the search criteria. To reset the search results, delete the contents of the Search field.

You can update the list of virtual infrastructure objects using the Refresh button above the table. When updating a list, the Wizard verifies the SSL certificates or fingerprints of the public key, just like what happens when adding virtual infrastructure objects to the list.

You can use buttons in the Name/Address column to:

• Remove selected virtual infrastructure from the list.

  The Integration Server continues to connect to the virtual infrastructure removed from this list, and to receive the information required for SVM operation.

• If you cannot connect to the virtual infrastructure, open the Virtual infrastructure connection settings window to change the settings of the account used to make the connection.

  After the settings are modified, the Wizard verifies the SSL certificates or fingerprints of the public key, just like what happens when adding virtual infrastructure objects to the list.

To select infrastructure for SVM deployment:

1. Depending on the type of the virtual infrastructure, select check boxes in the table to the left of the names of the hypervisors on which you want to deploy an SVM, or the OpenStack projects in which you want to deploy an SVM.

   You can select hypervisors or OpenStack projects that are not subject to SVM deployment restrictions.

   If SVMs are being deployed in an infrastructure based on the OpenStack platform, VK Cloud platform, or TIONIX Cloud Platform, simultaneous SVM deployment in different infrastructures is not supported. You can deploy SVMs in only one of these infrastructures at a time, or in one or more infrastructures of other types.

   The simultaneous deployment of SVMs within OpenStack projects, which are running on different Keystone microservices, is not supported. You can simultaneously deploy SVMs only in OpenStack projects that are running on the same Keystone microservice.

2. If you want to allow concurrent deployment of multiple SVMs, select the Allow parallel deployment on N hypervisors or Allow parallel deployment on N SVMs check box (depending on the type of virtual infrastructure) and specify the number of SVMs to be deployed concurrently.

Proceed to the next step of the wizard.

Selecting the SVM image

At this step, select the file of the SVM image for deployment on the hypervisor. The SVM image file and SVM image description file (in XML format) must be placed in the same folder on the device where the Kaspersky Security Center Administration Console is installed, or in the same folder on a network resource to which the user account performing the installation has read access. If you are installing the Protection Server on different types of hypervisors, the SVM image files for each type of hypervisor and the SVM image description file must be located in the same folder.

To specify the SVM image, click Browse and in the window that opens select the SVM image description file (in XML format).

After a file has been selected, the field to the left of the button displays the full path to the file and its name. The Wizard automatically selects the required SVM image file:

• A VHDX file for deployment on a Microsoft Windows Server (Hyper-V) hypervisor.
• An XVA file for deployment on a XenServer hypervisor or on a Numa vServer hypervisor.
• An OVA file for deployment on a VMware ESXi hypervisor.
• A QCOW2 file for deployment on a KVM hypervisor (including on a KVM hypervisor running on OpenStack platform, Astra Linux, VK Cloud Platform or TIONIX Cloud Platform), on a Proxmox VE hypervisor, on a R-Virtualization hypervisor, on a HUAWEI FusionCompute CNA hypervisor, on a Nutanix AHV hypervisor, or on an ALT Virtualization Server platform basic hypervisor.

The window displays the following information about the selected image:

• Vendor is the name of the vendor of the solution that the SVM is part of.
• Publisher is the name of the publisher of the solution that the SVM is part of.
• Solution name is the name of the solution that the SVM is part of.
• SVM version is the version number of the SVM image.
• Description is a brief description of the SVM image.
• Virtual drive size is the amount of disk space required to deploy the SVM.

The Wizard verifies the authenticity of the image. The verification results are displayed in the window as follows:

• If the image is authentic, the Publisher field displays the value AO Kaspersky Lab.
• If the authenticity of the image has not been verified, an error message is displayed at the top of the window, and Unknown is displayed in the Publisher field.

If the authenticity of the image has not been verified, it is recommended to use a different image for SVM deployment. To do this, you need to re-download the archive with the files necessary for SVM deployment using the Kaspersky Security Components Installation Wizard or on the Kaspersky website.

The SVM image integrity check section displays information about the results of SVM image file integrity check for each type of hypervisor. If integrity check was not performed, the Validation not performed message is displayed.

It is recommended to validate the SVM image. To do so, click the Validate button in the SVM image integrity check section. The verification results are displayed in the window as follows:

• If the image file successfully passed the integrity check, the Valid message is displayed.
• If the image file gets modified or corrupted while being transmitted from the publisher to the end user or if the image format is not supported, the upper part of the window shows an error message and the SVM image integrity check section displays information about the detected problem.

If an SVM image file integrity check ended with an error, it is recommended to use a different image for SVM deployment. To do this, you need to re-download the archive with the files necessary for SVM deployment using the Kaspersky Security Components Installation Wizard or on the Kaspersky website.

If the authenticity of an image has been verified and the image file integrity check completed successfully, proceed to the next step of the Wizard.

If the authenticity of an image has not been verified or an image file integrity check has not been performed or ended with an error but you accept the risk and want to use the selected SVM image, to proceed to the next step of the Wizard you need to select the check box located in the lower part of the window.

Selecting the number of SVMs for deployment (infrastructures based on OpenStack)

This step is displayed if you are performing SVM deployment in a virtual infrastructure managed by the OpenStack platform, VK Cloud platform, or TIONIX Cloud Platform.

For this step, you must specify the number of SVMs to be deployed on the hypervisors within each selected OpenStack project. The OpenStack project column displays the name of the project that the SVM will be deployed in, as well as the project path in the infrastructure.

In the Number of SVMs column, specify the number of SVMs to be deployed on the hypervisors within the OpenStack project.

Proceed to the next step of the wizard.

Specifying SVM settings

This step is displayed if you are deploying the SVM to a virtual infrastructure based on Microsoft Hyper-V, XenServer, VMware vSphere, KVM, Proxmox VE, Basis, Skala-R, HUAWEI FusionSphere, Nutanix Acropolis, Alt Virtualization Server, Astra Linux, or Numa vServer.

For this step, you must specify deployment options for each SVM to be deployed on the selected hypervisors. The Hypervisor column displays the IP address in IPv4 format or the fully qualified domain name (FQDN) of the hypervisor on which the SVM will be deployed.

Specify the following settings required for SVM deployment:

• SVM name

  An arbitrary name for new SVM.

• Storage

  Data storage for SVM image.

  The drop-down list displays the storage repositories available for SVM deployment.

  If you are deploying SVMs on a Microsoft Windows Server (Hyper-V) hypervisor that is part of a cluster, only shared repositories can be selected in the list.

  If you are deploying SVMs on a Microsoft Windows Server (Hyper-V) hypervisor that is not part of a cluster, you can manually enter the path to the repository.

• Network name

  The name of the virtual network that the SVM will use to connect to Light Agents, the Integration Server and the Kaspersky Security Center Administration Server.

  You can specify one or more virtual networks available on the hypervisor. To add or remove a field for selecting virtual networks, use the buttons next to the network selection field.

  If you intend to use dynamic IP addressing (DHCP) for all SVMs, the network settings will be received from the DHCP server via the first virtual network in the list of networks specified for each SVM. Make sure that the Wizard can connect to the SVM with the network settings of the first virtual network received from the DHCP server.

  If the virtual infrastructure uses the VMware Distributed Virtual Switch component, you can specify a Distributed Virtual Port Group to which the SVM will be connected.

If you are deploying an SVM in a virtual infrastructure running the Microsoft Hyper-V platform, you can also specify the VLAN ID.

Proceed to the next step of the wizard.

Specifying SVM settings (infrastructures based on OpenStack)

This step is displayed if you are performing SVM deployment in a virtual infrastructure managed by the OpenStack platform, VK Cloud platform, or TIONIX Cloud Platform.

On this step, you must specify deployment settings for each SVM that is to be deployed within the selected OpenStack projects. The OpenStack project column displays the name of the project that the SVM will be deployed in, as well as the project path in the infrastructure.

Specify the following settings required for SVM deployment:

• SVM name

  An arbitrary name for new SVM.

• Virtual machine type

  Virtual machine type (instance type) determines RAM volume, disk size, number of CPU cores, and other settings of created virtual machine.

  Select appropriate virtual machine type for SVM deployment from available types for OpenStack project. Virtual machine type must match recommendations of Kaspersky experts concerning the resource allocation for SVMs.

  If there is no virtual machine of the suitable type in the list, use the virtual infrastructure to create the required virtual machine type. After that, to refresh the list of available virtual machine types, you can go back to the infrastructure selection step and select the Refresh button or restart the SVM deployment procedure.

You can also specify the following settings:

• Volume type

  Volume type determines which data storage will be used for disk creation during the SVM deployment. Select a volume type from available types for OpenStack project.

• Availability zone

  A logical collection of hypervisors used to provide fault tolerance in infrastructures based on OpenStack. Select an availability zone into which the SVM will be located.

• Server group

  Grouping of virtual machines according to the policy that determines the hypervisors on which virtual machines will be started. Select a Server group, into which the SVM will be located.

Proceed to the next step of the wizard.

Configuring SVM network settings (infrastructures based on OpenStack)

This step is displayed if you are performing SVM deployment in a virtual infrastructure managed by the OpenStack platform, VK Cloud platform, or TIONIX Cloud Platform.

For this step, you must specify network settings for each SVM to be deployed within the selected OpenStack projects. The OpenStack project column displays the name of the project that the SVM will be deployed in, as well as the project path in the infrastructure.

For each SVM, specify one or more virtual networks in the Network name column.

You can also specify the following settings:

• VLAN ID

  The ID of the virtual local area network (VLAN) that the SVM will use to connect to Light Agents, the Integration Server and the Kaspersky Security Center Administration Server.

  If a VLAN is not used, the column shows No.

• Security group

  Set of network traffic filtering rules that are created in the virtual infrastructure and applied in the virtual network.

  You can specify one or more security groups for each selected virtual network. To add or remove a field for selecting security groups, use the buttons next to the Security groups selection field.

Proceed to the next step of the wizard.

Configuring IP address settings for SVM

For this step, you must specify IP addressing settings for all SVMs. You can use dynamic or static IP addressing.

If you want to use DHCP network settings for all SVMs:

1. Select Dynamic IP addressing (DHCP).

   By default, the IP address of the DNS server and the IP address of the alternative DNS server received over the DHCP protocol are used for each SVM (the Use list of DNS servers received via DHCP check box is selected). If you specified several virtual networks for the SVM at the previous step, by default the network settings for the SVM are received from the DHCP server of the first virtual network in the list of the specified virtual networks.

2. If you want to manually specify the IP address of the DNS server and alternative DNS server, clear the Use list of DNS servers received via DHCP check box. This opens a table containing the following information:
   • Hypervisor

     IP address in IPv4 format or the fully qualified domain name (FQDN) of the hypervisor on which the SVM will be deployed.

     The Hypervisor column is displayed if you are deploying the SVM to a virtual infrastructure based on Microsoft Hyper-V, XenServer, VMware vSphere, KVM, Proxmox VE, Basis, Skala-R, HUAWEI FusionSphere, Nutanix Acropolis, Alt Virtualization Server, Astra Linux, or Numa vServer.

   • OpenStack project

     Name of the OpenStack project selected for SVM deployment, as well as project path in the infrastructure.

     The OpenStack project column is displayed if you are performing SVM deployment in a virtual infrastructure managed by the OpenStack platform, VK Cloud platform, or TIONIX Cloud Platform.

   • SVM name

     The name that was defined when specifying SVM settings.

   Specify the IP addresses of DNS servers in the DNS server and Alternative DNS server table columns.

If you want to specify all network settings of the SVM manually, select:

1. Select Static IP addressing. This opens a table containing the following information:
   • Hypervisor

     IP address in IPv4 format or the fully qualified domain name (FQDN) of the hypervisor on which the SVM will be deployed.

     The Hypervisor column is displayed if you are deploying the SVM to a virtual infrastructure based on Microsoft Hyper-V, XenServer, VMware vSphere, KVM, Proxmox VE, Basis, Skala-R, HUAWEI FusionSphere, Nutanix Acropolis, Alt Virtualization Server, Astra Linux, or Numa vServer.

   • OpenStack project

     Name of the OpenStack project selected for SVM deployment, as well as project path in the infrastructure.

     The OpenStack project column is displayed if you are performing SVM deployment in a virtual infrastructure managed by the OpenStack platform, VK Cloud platform, or TIONIX Cloud Platform.

   • SVM name

     The name that was defined when specifying SVM settings.

   • Network name

     The name of the virtual network that the SVM uses to connect to Light Agents, the Integration Server and the Kaspersky Security Center Administration Server.

2. Specify the following IP addressing settings for each SVM:
   • SVM IP address
   • Subnet mask
   • Gateway
   • DNS server
   • Alternative DNS

   If you specified several virtual networks for the SVM at the previous step, specify the settings for each virtual network.

Proceed to the next step of the wizard.

Specifying Kaspersky Security Center connection settings

This step is performed if the wizard cannot automatically determine the settings for connecting to Kaspersky Security Center.

At this step, you must specify the settings of SVM connection to the Kaspersky Security Center Administration Server.

Specify the following settings:

• Address

  Address of the device hosting the Kaspersky Security Center Administration Server. You can specify the IP address in IPv4 format or the fully qualified domain name (FQDN) of the device.

• Port

  Number of the port for connecting the SVM to the Kaspersky Security Center Administration Server.

• SSL port

  Number of the port for connecting an SVM to the Kaspersky Security Center Administration Server using an SSL certificate.

Proceed to the next step of the wizard.

Creating the configuration password and the root account password

At this step, you need to create a klconfig account password (configuration password) and a root account password on the SVM.

The configuration password is required for SVM reconfiguration. The root user account is used for access to the operating system on SVMs.

Enter passwords for each account into the Password and Confirm password fields.

Passwords must be no longer than 60 characters. You can use only letters of the Latin alphabet (uppercase and lowercase letters), numerals, and the following special characters: ! # $ % & ' ( ) * " + , - . / \ : ; < = > _ ? @ [ ] ^ ` { | } ~. For security purposes, you are advised to set passwords that are at least 8 characters long and use at least three of the four categories of characters: lowercase letters, uppercase letters, numerals, and special characters.

If you want to configure access to SVMs over SSH under the root account, select the Allow remote access to SVM for the root account via SSH check box.

Proceed to the next step of the wizard.

Starting SVM deployment

This step is displayed if you are deploying the SVM to a virtual infrastructure based on Microsoft Hyper-V, XenServer, VMware vSphere, KVM, Proxmox VE, Basis, Skala-R, HUAWEI FusionSphere, Nutanix Acropolis, Alt Virtualization Server, Astra Linux, or Numa vServer.

For this step, the wizard window displays all previously entered settings required for deploying the SVM:

General settings for all SVMs:

• SVM image description file

  The full path and name of the SVM image description file (in XML format) that you specified at the SVM image selection step.

• SVM IP settings

  Method of configuring IP addressing settings.

  Possible values: Dynamic IP addressing (DHCP), Static IP addressing.

• SSH-based remote access to the SVM for the root account

  Remote access to the SVM over SSH for the root user account.

  Possible values: Allowed, Blocked.

• Kaspersky Security Center connection settings

  IP address in IPv4 format or fully qualified domain name (FQDN) of the device hosting the Kaspersky Security Center Administration Server, and port numbers for connecting the SVM to the Kaspersky Security Center Administration Server.

• Parallel deployment

  The number of SVMs to be deployed concurrently.

Individual settings for each SVM:

• Hypervisor

  IP address in IPv4 format or the fully qualified domain name (FQDN) of the hypervisor on which the SVM will be deployed.

• SVM name

  The name that was defined when specifying SVM settings.

• Storage

  Data storage for SVM image.

• Network name

  The name of the virtual network that the SVM uses to connect to Light Agents, the Integration Server and the Kaspersky Security Center Administration Server.

• VLAN ID

  The ID of the virtual local area network (VLAN) that the SVM uses to connect to virtual machines, the Integration Server and the Kaspersky Security Center Administration Server.

  The VLAN ID is displayed if you are deploying the SVM in the virtual infrastructure running on Microsoft Hyper-V platform.

• All IP addressing settings that you provided for the SVM.

To start deploying SVMs, go to the next step of the wizard.

Starting SVM deployment (infrastructures based on OpenStack)

This step is displayed if you are performing SVM deployment in a virtual infrastructure managed by the OpenStack platform, VK Cloud platform, or TIONIX Cloud Platform.

For this step, the wizard window displays all previously entered settings required for deploying the SVM:

General settings for all SVMs:

• Keystone microservice address

  IP address or fully qualified domain name (FQDN) of the Keystone microservice that manages the OpenStack project in which the SVMs are being deployed.

• SVM image description file

  The full path and name of the SVM image description file (in XML format) that you specified at the SVM image selection step.

• SVM IP settings

  Method of configuring IP addressing settings.

  Possible values: Dynamic IP addressing (DHCP), Static IP addressing.

• SSH-based remote access to the SVM for the root account

  Remote access to the SVM over SSH for the root user account.

  Possible values: Allowed, Blocked.

• Kaspersky Security Center connection settings

  IP address in IPv4 format or fully qualified domain name (FQDN) of the device hosting the Kaspersky Security Center Administration Server, and port numbers for connecting the SVM to the Kaspersky Security Center Administration Server.

• Parallel deployment

  The number of SVMs to be deployed concurrently.

Individual settings for each SVM:

• OpenStack project

  Name of the OpenStack project selected for SVM deployment, as well as project path in the infrastructure.

• SVM name

  The name that was defined when specifying SVM settings.

• Virtual machine type

  Type of virtual machine (instance type) selected for SVM.

• Volume type

  Volume type to be used during SVM deployment.

• Availability zone

  Logical collection of hypervisors where the SVM will be located.

• Server group

  Group of virtual machines in which the SVM will be located.

• Network name

  The name of the virtual network that the SVM uses to connect to Light Agents, the Integration Server and the Kaspersky Security Center Administration Server.

• VLAN ID

  The ID of the virtual local area network (VLAN) that the SVM uses to connect to virtual machines, the Integration Server and the Kaspersky Security Center Administration Server.

• Security group

  Security group selected for the virtual network.

• All IP addressing settings that you provided for the SVM.

To start deploying SVMs, go to the next step of the wizard.

SVM deployment

At this step, SVMs are deployed on hypervisors. The process takes some time. Please wait until deployment is complete.

The window shows, one row at a time, the stages of deployment of each SVM with the status of each stage: Processing N%, Pending, Skipped, Completed, Error.

After SVM deployment is complete, you are advised to make sure that the Integration Server is running and can be accessed by the SVM over the network.

If an error occurs on a hypervisor during the SVM deployment process, the Wizard rolls back the changes on this hypervisor. Deployment continues on the other hypervisors.

When deployment is completed, SVM is turned on automatically.

Proceed to the next step of the wizard.

Finishing SVM deployment

This step displays information about the SVM deployment results in the virtual infrastructure.

You can use the links to open a brief report and the SVM Management Wizard log.

You can view the following information in the brief report:

• Addresses of the hypervisors on which SVMs were deployed, or OpenStack projects, within which SVMs were deployed (depending on the type of virtual infrastructure).
• Names of deployed SVMs.
• Brief description of the completed stages of deployment of each SVM, including the start and end times of each stage. If an error occurred during a particular stage, the relevant information is reflected in the report.

The brief report is saved in a temporary file. To be able to use information from the report later, save the log file in a permanent storage location.

The SVM Management Wizard log saves information specified by you at every step of the wizard. If the SVM deployment process ends in an error, you can use the wizard log when contacting Technical Support.

The SVM Management Wizard log is saved on the device where the wizard was launched, in the file %LOCALAPPDATA%\Kaspersky Lab\Kaspersky VIISLA Console\logs\KasperskyDeployWizard_<file creation date and time>.log and does not contain account passwords. A new log file is created each time the wizard starts.

Finish the wizard.

If your virtual infrastructure uses a Microsoft Windows Server (Hyper-V) hypervisor, after SVM deployment the event log may contain an event indicating the need to update the Integration Services package on the SVM. You can ignore this notification because the Integration Services do not need to be updated to operate the SVM.