Versions Compared

Version Old Version 3 New Version Current
Changes made by

Kiss, Mate

Hina Kouser

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Warning

A Verba Media Repository must be installed before starting Desktop Agent installation. The desktop agent installer kit checks verifies only a limited set range of hardware and 3rd third-party software prerequisites. Therefore, it is very important to fully understand the review all Prerequisites thoroughly before proceeding with the installation procedure.

Warning

Make sure

Ensure that the following TCP port is open on the desktops where the Verba Desktop Agent is deployed: 4433 (TCP). See Firewall configuration.

Manual installation

Installation

Please follow the steps below to install the Verba Desktop Agent:

Step 1 - Launch the VerbaDesktop.msi installer as Administrator.

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

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

Step 4 - Select the destination folder for the Verba Desktop Agent. 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 5a

(i) If using Verba CA is being used, then select the "Generate Certificate Signed by Verba Media Repository CA" option , then and click on the Generate button.

(ii) In the Generate the Verba Server Certificate window, provide the address of the first Media Repository server , and the Verba administrator username and password, then click Generate. Finally, click on .

(iii) Click Generate.

(iv) Finally, click the Next button. (If this option is being used, Step 5b can be skippedyou are using this, you can skip Step 5b.)

Step 5b - 5b

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

Image Modified

Info

title

Certificates generated by the Verba CA

Based on the Friendly Name of the certificates the

Identify the Verba server and

the

CA certificate

can be identified easily

using their Friendly Names. On the screenshot, the first

one

option is the server certificate and the second

one

option is the CA certificate.

Image Removed

Image Added

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

  • The account name

    • has to

  • must be entered with the domain.

  • The Domain

    • Account have to

  • account must be a part of the Local Administrators group and requires the Log on as a service right.

Image Modified

Info

title

When do I need domain account?

Ifthemediafileswillbestoredonanetworklocation.

  • If the media files will be stored on a network location.
    In this case,

make sure

  • ensure that the service account has rights to the folder.

  • If

windowsauthenticationwillbeusedfortheSQL

  • 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 requesting 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 supportedWindows authentication are supported. All Verba servers and components have to use the same database! 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 are successful, click Next.

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

Image Modified

Info

title

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

nameisprovidedattheSQL

  • 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 is the user account created at at Step 14 during during the installation of the Media Repository server.

Image Modified

Info

title

Verba API instead of direct database connection

If the direct database connection is not possible from the desktop PCs, the Verba Desktop Agent can use the Verba API connection for reachning the database. In this case, the Verba Web Application will work as a proxy between the Verba Desktop Agent and the database.

Step 9 - Click Click the Next again  button again to start installing the services. When it's donethe installation is complete, click Finish to exit the installer.

Info

The Verba Desktop Agent must be configured from the central web interface before it can work. For more information, see Configuring the Verba Desktop Agent.

Unattended installation

The Verba Desktop Agent installation package provides an unattended installation feature to support automated, enterprise-wide installation of the software. The installer is MSI-based. For more information, see Installer Parameters