...
Editing the data in the tables in the restored Velocity database
Importing the Velocity TLS certificate from one server to another
...
For Windows 10 type of machines, to locate the computer name of your system:
Open Control Panel. Click System and Security -> System.
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 versionversions, visit Windows support.
From the Windows desktop, select Start-> Microsoft SQL Server Tools 18-> Microsoft SQL Server Management Studio 18.
The Microsoft SQL Server Management Studio opens.
Login to SQL Server using your credentials.
In the Object Explorer navigation pane, expand the Databases folder to display the Velocity database.
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.
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 to the table for data modifications.
...
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.
...
12. Reinstall the Server Extensions that are actually used.
To install a server extension:
Click Velocity's menu button, then select Extensions > Server Extensions.
The Velocity Server Extensions Manager appears.
Click Install.
The Find Server Extension dialog appears.Search for Identiv\Velocity root directory. Several HEX files are located here as shown.
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.
Repeat steps 3 till to 5 to install more extensions.
When you are finished. click OK.
A message appears, prompting you to restart the Extension Service before the extension takes effect.Click OK.
For the service extension to take effect, right-click on the Velocity Service Control Manager (SCM) in the Windows to try to stop the extension service and restart it again.
Start the Velocity DIGI*TRAC Network Service.
| Tip |
|---|
After installing and restarting the extensions services, they The extension services are displayed in the Velocity’s Interfaces Configuration folder after installing and restarting them. |
Moving Velocity Archive Files
In a larger facility with a lot of activities taking place, the events and alarms table in the Velocity database can become quiet quite large. It becomes critical for the older alarms and events to be archived.
The Velocity archive file contains a snapshot of the alarms and events recorded for a specified Velocity system. This file is created every time the Scheduling Agent runs the Archive Alarm/Event Logs schedule.
To maintain the past 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\Microsoft SQL Server\MSSQL15.IDENTIV\MSSQL\DATA folder from your old source system to the new target system.
...
On the old system, locate the ...\Program Files\Identiv\Velocity directory and find the velocitytmpxxxxx.dat files, where xxxxx XXXX is the number of each encryption file.
There should be one data file for each SNIB2/SNIB3 installed in the system.Copy all relevant .dat files to a USB drive, removable media, or network-accessible location.
On your new computer, paste the relevant .dat files into the ...\Program Files\Identiv\Velocity directory.
These files will overwrite the existing files, and provide Velocity with the encryption information it needs to communicate with the connected SNIB2s/SNIB3s.
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.
Importing the VelocityTLS certificate from one server to another
Replacing a Velocity server machine will require the customer to delete the VelocityTLS certificate added by the Velocity installer and manually import the certificate from the Velocity database to the new computers Windows Certificate store (using -import switch option of provided tool, GenerateVelocityTLSCertificate.exe).
Deleting the VelocityTLS certificate added by the Velocity installer
To delete the VelocityTLS certificate:
Open certmgr.msc, goto certificates →Local Computer→ Personal → Certificates.
Right-click VelocityTLS and select Delete.
Importing the VelocityTLS certificate from the Velocity database to the Windows Certificate Store
To import the VelocityTLS certificate from the Velocity database:
Open command prompt with Administrator privileges (i.e., Run as administrator).
Change Directory to Velocity installation directory (i.e., cd C:\Program Files (x86)\Identiv).
Run the GenerateVelocityTLSCertificate.exe with -import switch (i.e., C:\Program Files (x86)\Identiv\Velocity>GenerateVelocityTLSCertificate -import).
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.
Open certmgr with Administrator permissions and go to Local Computer → Personal → Certificates.
Right-click VelocityTLS certificate → All Tasks → Manage Private Keys...
Select the user VelocityServices and click the Remove button.
Re-add the VelocityServices user and grant full permission.
