Versions Compared

Version Old Version 24 New Version 25
Changes made by

Anand Rajaraman

Anand Rajaraman

Saved on

Key

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

...

  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.

  3. Login 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.

  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.

    To add or edit the data in the SQL table properties such as operators, servers, server extensions, and registry, we have considered a scenario with examples that use a sequence of system names such as vel1.server.system, vel1.local.system, vel1.remote.system etc., based on the entered data.

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 NewSystem1.

  • If using domain accounts, the Windows Domain name.

MiscProperties

UseDomainAuthentication

  • 0=Use Local accounts

  • 1=Use Domain accounts

MiscProperties

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.)

Operators

DirectorySource

  • If using local Windolocal computer’s namews Windows accounts, update all rows to the local computer’s name of the local computer. 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.

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.server.system.

ServerExtensions

RemoteComputerName

Name of the Velocity Server (all UPPERCASE). For example, after restoring the database to a new server, the server name can be vel1.remote.system.

Registry

AppPath

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

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

Registry

ComputerName

Name of the Velocity Server (all UPPERCASE). For example, after restoring the database to a new server, the server name can be vel1.newserver.system.

Registry

RemoteIP

Name of the Velocity Server (all UPPERCASE). For example, after restoring the database to a new server, the server name can be vel1.remoteIP.system.

Registry

RemoteServerIP

Name of the Velocity Server (all UPPERCASE). For example, after restoring the database to a new server, the server name can be vel1.remoteserverIP.system.

Registry

SDServer

Name of the Velocity Server (all UPPERCASE). For example, after restoring the database to a new server, the server name can be vel1.sdserver.system.

Registry

ServerName

SQL Server Instance name.

Workstations

WorkstationName

Name of the Velocity Server for WorkstationID=1 (all UPPERCASE)

...

To maintain the history of your Velocity system, you should copy the VelocityArchivexxx.mdf and VelocityArchivexxx_log.ldf files (where xxx is the time and date when the file was created) in the C:\Program Files(x86)\Microsoft SQL Server\MSSQL15.IDENTIV\MSSQL\DATA folder from your old source system to the new target system.

...

  1. On the old system, locate the ...\Program Files(x86)\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 ...\Program Files(x86)\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.

...