Configuring the settings for connecting the Integration Server to the virtual infrastructure administration server

Depending on the virtual infrastructure that you want to protect using Kaspersky Security, you need to configure a connection to the following virtual infrastructure administration servers:

• To protect a virtual infrastructure managed by one or multiple VMware vCenter Servers, you need to configure the connection of the Integration Server to each of these VMware vCenter Servers.
• To protect a virtual infrastructure managed by VMware vCenter Servers connected to the VMware Cloud Director Server, configure the Integration Server connection to each of these VMware vCenter Servers, and to the VMware Cloud Director Server.

The connection to each virtual infrastructure administration server is established separately.

In an infrastructure managed by VMware Cloud Director, you can connect the Integration Server to VMware vCenter Servers and VMware Cloud Director Servers in any order. The Integration Server automatically determines whether each added VMware vCenter Server is a standalone server or is connected to a VMware Cloud Director Server.

Kaspersky Security operation is not supported in the infrastructure managed by VMware NSX Manager, to which several VMware vCenter Servers are connected.

To configure the settings for connecting the Integration Server to the virtual infrastructure administration server:

1. Start the Integration Server Console.
2. In the Virtual infrastructure protection section, click the Add button.
3. In the opened Connection to virtual infrastructure window, select the type of virtual infrastructure administration server to which you need to configure a connection, and click Next.
4. Specify the following settings:
   • IP address in IPv4 format or fully qualified domain name (FQDN) of the virtual infrastructure administration server to which the Integration Server connects.
   • Name and password of the account that the Integration Server uses to connect to the virtual infrastructure administration server.

   The entered connection settings (except the password) are saved in the registry of the operating system in encrypted form.

5. Click the Validate button. The Integration Server checks the specified connection settings and the SSL certificate received from the virtual infrastructure administration server. If a connection could not be established or certificate errors are detected during the connection, the window displays an error message.

   If a connection error occurs because the certificate received from the virtual infrastructure administration server is not trusted for the Integration Server, the Certificate validation window opens. If the received certificate complies with the security policy of your organization, you can confirm the authenticity of the certificate and establish the connection. To do so, click the Install certificate button in the opened window. The received certificate is saved as a trusted certificate for the Integration Server.

   Certificates that are trusted in the operating system in which the Integration Server is installed are also considered to be trusted for the Integration Server.

   If there are problems with the SSL certificate, it is recommended to make sure that the utilized data transfer channel is secure.

6. After establishing a connection with the virtual infrastructure administration server, click OK in the Connection to virtual infrastructure window.

   The entered address or name of the virtual infrastructure administration server is displayed in the table in the Virtual infrastructure protection section.

   If you configure connection to the VMware Cloud Director Server and to the VMware vCenter Servers connected to it, the rows containing information about these VMware vCenter Servers are automatically grouped into a list located under the row with this VMware Cloud Director.

For each virtual infrastructure administration server, the table displays a list of actions that you can perform when configuring a connection to this server and for subsequent deployment of virtual infrastructure protection. You can expand or collapse the list of possible actions by clicking on the address or name of the virtual infrastructure administration server in the Address column.

If necessary, you can change or delete previously enter settings for connecting the Integration Server to the virtual infrastructure administration server.

To change the settings for connecting the Integration Server to the virtual infrastructure administration server:

1. Expand the list of possible actions for the selected virtual infrastructure administration server by clicking on the address or name of the virtual infrastructure administration server in the Address column.
2. Depending on the type of virtual infrastructure administration server, select Change VMware vCenter Server connection settings or Change VMware Cloud Director connection settings. The Connection to virtual infrastructure window opens.
3. Enter the new connection settings and verify the capability to connect, as described in the procedure for configuring the settings for connecting the Integration Server to the virtual infrastructure administration server (see items 4–6 of the previous instructions).

To delete the settings for connecting the Integration Server to the virtual infrastructure administration server:

1. Expand the list of possible actions for the selected virtual infrastructure administration server by clicking on the address or name of the virtual infrastructure administration server in the Address column.
2. Depending on the type of virtual infrastructure administration server, select Remove VMware vCenter Server from the list or Remove VMware Cloud Director from the list.
3. Confirm the deletion in the window that opens.

   Removing a VMware vCenter Server from the list is possible only if Kaspersky Security services are not registered in VMware NSX Manager.

After configuring the connection between the Integration Server and one or several VMware vCenter Servers, you can proceed to deploying protection in the VMware virtual infrastructure.