Versions Compared

Version Old Version 50 New Version 51
Changes made by

Anand Rajaraman

Anand Rajaraman

Saved on

Key

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

...

After restoring the Velocity database to the new system, perform the following procedure to edit the data in the SQL tables of the Velocity database.

  1. For Windows 10 type of machines, to locate the computer name of your system:

    1. Open Control Panel. Click System and Security → System.

    2. On the View basic information, see the Full computer name under the Computer name, domain, and workgroup settings section. Visit Windows Support to check the computer name for other types of Windows versions.

  2. From the Windows desktop, select Start→ Microsoft SQL Server Tools 18→ Microsoft SQL Server Management Studio 18.
    The Microsoft SQL Server Management Studio opens.

    Image Modified

  3. Log in to SQL Server using your credentials.

  4. Expand the Databases folder to display the Velocity database in the Object Explorer navigation pane.

  5. Expand the Velocity database to display the Tables branch.

    Image Modified

  6. Make the changes specified in the following table by right-clicking each database table and selecting Edit Top 200 Rows from the pop-up menu. (After each change, click outside the edited row for the changes to take effect.)
    Note: Be extra careful while editing the tables because accidentally editing the tables can corrupt the database.

    Image Modified

    The table describes the modification of the SQL table properties and their value after a Database restoration. A set of table properties such as Server_Name, Remote Computer Name, Application path, Remote Server IP, and its value are replaced by the destination system name or target system name, for example, VEL1-LOCAL-SYSTEM.

In this table:

Select this column:

Enter this data:

MiscProperties


AuthenticationPath

  • If using local Windows accounts, the name of the local computer. For example, after restoring the database to a new system, the local computer name would be VEL1-LOCAL-SYSTEM.

  • If using domain accounts, the Windows Domain name.

UseDomainAuthentication

  • 0=Use Local accounts

  • 1=Use Domain accounts

Organizational Unit (OU)

(This column exists only if you selected an Organization Unit during the Velocity installation.)
LDAP://OU=Organizational Name,DC=Domain Name,DC=Top-Level Domain Name

For example: LDAP://OU=ENGINEERING,DC=SECURITY,DC=com

Operators

Name

If you are not logging in as Administrator for OperatorID=2, use your Windows user name. (If you are using the Administrator account, skip this step.)

DirectorySource

  • If using local Windows accounts, update all rows to the local computer’s name. For example, the local computer name can be \\VEL1-LOCAL-SYSTEM after restoring the database to a new system.

  • If using domain accounts, update all rows to the Windows Domain name. For example, \\SQL_Instance_name.

Servers

Server_Name

Name of the Velocity Server (all UPPERCASE). For example, after restoring the database to a new server, the server name can be VEL1-LOCAL-SYSTEM.

ServerExtensions

RemoteComputerName

Name of the Velocity Server (all UPPERCASE). For example, VEL1-LOCAL-SYSTEM.

Registry

AppPath

  • Destination of the application path. For example: C:\Program Files(x86)\Identiv\Velocity.

  • If this is a 64-bit version of Windows, the path is: C:\Program Files (x86)\Identiv\Velocity.

ComputerName

Name of the Velocity Server (all UPPERCASE). For example, VEL1-LOCAL-SYSTEM.

RemoteIP

Name of the Velocity Server (all UPPERCASE). For example, VEL1-LOCAL-SYSTEM

RemoteServerIP

Name of the Velocity Server (all UPPERCASE). For example, VEL1-LOCAL-SYSTEM.

SDServer

Name of the Velocity Server (all UPPERCASE). For example, VEL1-LOCAL-SYSTEM.

ServerName

SQL Server Instance name. For example, VEL1-LOCAL-SYSTEM\SQL_Instance_name.

Workstations

WorkstationName

Name of the Velocity Server for WorkstationID=1 (all UPPERCASE). For example, the workstation name is VEL1-LOCAL-SYSTEM.

...

To install a server extension:

  1. Click Velocity's menu button, then select Extensions > Server Extensions.

  2. The Velocity Server Extensions Manager appears.

  3. Click Install.
    The Find Server Extension dialog appears.

  4. Search for Identiv\Velocity root directory. Several HEX files are located here, as shown.

    Image Modified

  5. Select the extension you want to install and click Open.
    The newly installed extension appears in the Server Extension list in the Velocity Server Extensions Manager. By default, the extension is enabled (checked,) and the word 'True' appears in the first column.

    Image Modified

  6. Repeat steps 3 to 5 to install more extensions.

  7. When you are finished.
    A message appears, prompting you to restart the Extension Service before the extension takes effect.

  8. Click OK.

  9. For the service extension to take effect, right-click on the Velocity Service Control Manager (SCM) in Windows to try stopping and restarting the extension service.

  10. Start the Velocity DIGI*TRAC Network Service.

Tip

The extension services are displayed in Velocity’s Interfaces Configuration folder after installing and restarting them.

...

You can ignore this section if your Velocity system does not have SNIB2 or SNIB3 boards installed in any attached controllers.

  1. On the old system, locate the ...\ProgramData\Identiv\Velocity directory and find the velocitytmpxxxxx.dat files, where XXXX is the number of each encryption file.
    There should be one data file for each SNIB2/SNIB3 installed in the system.

  2. Copy all relevant .dat files to a USB drive, removable media, or network-accessible location.

  3. Paste the relevant .dat files into the ...\ProgramData\Identiv\Velocity directory on your new computer.

    These files will overwrite the existing files, and provide Velocity with the encryption information it needs to communicate with the connected SNIB2s/SNIB3s.

  4. Open Velocity and resume communication between this Velocity server and the SNIB2/SNIB3 installed controller using the specified encryption.

Right-click the .dat files to check if the permissions on each file are set to Full Control.

...

To delete the VelocityTLS certificate:

  1. Open certmgr.msc, goto certificates →Local Computer→ Personal → Certificates.

  2. Right-click VelocityTLS and select Delete.

    Image Modified

Importing the VelocityTLS certificate from the Velocity database to the Windows Certificate Store

To import the VelocityTLS certificate from the Velocity database:

  1. Open a command prompt with Administrator privileges (i.e., Run as administrator).

  2. Change the Directory to Velocity installation directory (i.e., cd C:\Program Files (x86)\Identiv).

  3. Run the GenerateVelocityTLSCertificate.exe with -import switch (i.e., C:\Program Files (x86)\Identiv\Velocity>GenerateVelocityTLSCertificate -import).

  4. Verify Velocity TLS certificate was imported to Local Computer → Personal → Certificates.

Sometimes after importing the Velocity TLS certificate, permission for VelocityServices is not set correctly even though VelocityServices displays as having permission. When this occurs, you can fix this problem by deleting and re-granting permission to VelocityServices.

  1. Open certmgr with Administrator permissions and go to Local Computer → Personal → Certificates.

  2. Right-click VelocityTLS certificate → All Tasks → Manage Private Keys...

    Image Modified

  3. Select the user VelocityServices and click the Remove button.

...

  1. Add again the VelocityServices user and grant Full control. Click OK.

    Image Modified