Installing the Verba Media Collector and Proxy component

Owned by Kiss, Mate
Jul 31, 2018
5 min read

The Verba Media Collector and Proxycomponentisresponsiblefor capturing the media streams on the node it's installed on and forwarding it to a Verba Recording Server. In a Lync environment, it's typically installed on the Edge server or the Mediation server depending on your recording needs. 

Do not install the VerbaAdditionalRoles.msi onaSingeServeror Recording Server because the Verba Media Collector and Proxy Service is already installed there and you will end up with corrupt registry settings.

Please follow the steps below to install the component:

Step 1 - The install kit starts installing Verba components. Simply press the Next button to start the installation.

Step 2 - Read the Verba license agreement carefully before you click Next button.

Step 3 - Select the Media Collector & Proxy Server role from the list. Click Next.

Step 4 - Select the destination folder for Verba software. You can change the default setting by clicking on the Change button and selecting another folder. If you have finished the destination folder configuration, press the Next button.

Step 5a - If a Verba CA is being used, then select the "Generate Certificate Signed by Verba Media Repository CA" option, then click on the Generate button. In the Generate the Verba Server Certificate window provide the address of the first Media Repository server, the administrator username and password, then click Generate. Finally, click on the Next button. (If this option is being used, Step 5b can be skipped.)

Step 5b - If there is an existing certificate from a previous Verba installation (in case of reinstall or upgrade), or a pre-generated certificate for the server exists (requested from a local or a 3rd party CA), then select the "Select Certificate" option, then click on the Browse button.

 

Servers in DMZ and Verba CA

If the server is in DMZ (for example in case of Edge servers), then the server certificate cannot be requested directly from the Verba CA, and Step 5b has to be selected. In this case, there are two prerequisites:

  • The server certificate has to be downloaded from the Verba Web Interface, and imported into the server's certificate store manually. For the certificate downloading guide see: Server Certificates
  • The CA certificate of the Verba CA has to be manually exported from thecertificate store of the first Media Repositroy (or Singel) server, then imported manually into the server's certificate store.

Certificates generated by the Verba CA

Based on the Friendly Name of the certificates the server and the CA certificate can be identified easily. On the screenshot, the first one is the server certificate and the second one is the CA certificate.

 

 

 

 

 

Step 6 - Select the service account type. If the Domain Account is selected then please note the followings:

      • The account name has to be entered with the domain
      • The Domain Account have to be part of the Local Administrators group and requires the Log on as a service right


When do I need domain account?

  • If windows authentication will be used for the SQL connection (Step 7). In this case, the same account has to be used for the services.

Step 7a - The Verba installer is asking for the MS SQL Server credentials. The server name can be entered either as an IP address or an FQDN. Both SQL server based and windows authentication is supported. All Verba servers and components have to use the same database! If Verba install kit has installed MS SQL Server 2012 Express Edition as a prerequisite, the password for the sa user is: Verba456+. If SQL Mirroring is being used or AlwaysOn with Multi-Subnet failover, then a different SQL Driver has to be selected. In this case, the driver has to be installed on the server. Click 'Test Connection' to verify your input. If the tests were successful, click Next.

Step 7b - If the incoming connection from the server is not possible (because the server is in DMZ for example), then uncheck the "Enable Automatic Node Registration" setting. In this case, the server has to be added manually to the server list in the System \ Servers menu after the installation. Click Next.

 

Database connection troubleshooting tips

  • Try to ping the database server. Try to connect to the 1433 port on the database server. (telnet or Test-NetConnection)
  • Check if the user has the DB Creator role.
  • If Windows Authentication used then check if the user has the Local Administrator group membership and the 'Logon as a service right'.
  • Check if the correct instance name is provided at the SQL Server name. If there are multiple instances, then the SQL Server Browser service must run on the SQL server side.
  • If you installed SQL Server Express Edition, then check if the TCP/IP protocol is enabled under the SQL Server Network Configuration in the SQL Server Configuration Manager.

Step 8 - Provide the address of the Verba Media Repository server, and the API user password. The API user created at Step 14 during the installation of the Media Repository server.


Step 9 - Select the primary IP address of the server from the list, then click Next.

 

 

Step 10 - Please provide a target email address, a source email address and an SMTP server address for system alerts. If authentication required then please enter the credentials. The target email address will receive alerts concerning the various services of the recording system. This step can be skipped and the details can be provided or modified after the installation. When you are done, click Next.


Step 11 - Click Next again to start installing the services. When it's done, click Finish to exit the installer.