Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

If you are restoring a backup of the Velocity database to the same computer (a Velocity server, data server, or standalone workstation) where the backup was made, follow the instructions in Moving a Velocity 3.8 Database

If you are restoring a backed-up Velocity database to a different computer other than the one where it was originally backed up, you must perform the additional procedures mentioned after you have restored the Velocity database to the new computer. The additional tasks are:

  • Getting a New Velocity License

  • Editing the data in the tables in the restored Velocity database

  • Moving the Velocity archive files

  • Restoring the SNIB2 encryption files

  • Importing the Velocity TLS certificate from one server to another

Getting a New Velocity License

The Velocity licensing mechanism uses the unique machine ID of your computer. It is required to contact Identiv Sales to obtain a new Velocity license for the new system.

Editing the Data in the Tables in the restored Velocity Database

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. To check the computer name for other types of Windows version, visit Windows support.

  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. In the Object Explorer navigation pane, expand the Databases folder to display the Velocity database.

  5. Expand the Velocity database to display the Tables branch.
    Note: Be extra careful while editing the tables, because accidentally editing the tables can corrupt the database.

  6. Make the changes specified in the following table, by right-clicking on 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.)

    Refer the table for data modifications.

In this table:

Select this column:

Enter this data:

MiscProperties

AuthenticationPath

  • If using local Windows accounts, the name of the local computer.

  • 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, your Windows user name. (If you are using the Administrator account, skip this step.)

Operators

DirectorySource

  • If using local Windows accounts, update all rows to the name of the local computer.

  • If using domain accounts, update all rows to the Windows Domain name.

Servers

Server_Name

Name of the Velocity Server (all UPPERCASE).

ServerExtensions

RemoteComputerName

Name of the Velocity Server (all UPPERCASE).

Registry

AppPath

  • Destination of the application path. For example: C:\Program Files\Hirsch Electronics\Velocity

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

Registry

ComputerName

Name of the Velocity Server (all UPPERCASE).

Registry

RemoteIP

Name of the Velocity Server (all UPPERCASE).

Registry

RemoteServerIP

Name of the Velocity Server (all UPPERCASE).

Registry

SDServer

Name of the Velocity Server (all UPPERCASE).

Registry

ServerName

SQL Server Instance name.

Workstations

WorkstationName

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

7. Restart the Velocity Security Domain Service and launch the Velocity Application.

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

9. The Velocity Server Extensions Manager appears.

The Server Extensions Manager lists the service extensions that need to have the name of the computer updated before they will work on the new computer. Make note of which server extensions you are actually using.

10. Click to highlight an existing service extension. The Uninstall button is activated.

11. Click Uninstall. The selected extension service is removed from the system.

12. Reinstall the Server Extensions that are actually used.

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.

  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.

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

  7. When you are finished. click OK.
    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 the Windows try to stop the extension service and restart again.

  10. Start the Velocity DIGI*TRAC Network Service.

After installing and restarting the extensions services, they are displayed in the Velocity’s Interfaces Configuration folder.

Moving Velocity Archive Files

  • No labels