Versions Compared

Version Old Version 42 New Version 43
Changes made by

Anand Rajaraman

Anand Rajaraman

Saved on

Key

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

...

  • If the migrated system does not have the Velocity license, a 30days 30 days temporary license will be installed.

  • An expired Velocity license notification message displays when the original Velocity license installed is more than 30 days.

  • If the installation is less than 30 days, a pop-up message asks the user to purchase the Velocity Licensed version.

  • The Velocity license found in the database that does NOT match the Server ID of that machine will be removed.

  • All other license types, including plugins or any created and used by IGS, are not applied or extended.

...

  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 RemovedImage Added

  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.

  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.

    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, Remote IPApplication path, and Remote Server IP, and its value are replaced by the destination system name or target system name, for example, VEL1-LOCAL-SYSTEMor Windows Domain name.

Registry

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, \\WORKGROUP 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\WORKGROUP NAME.

Workstations

WorkstationName

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

...

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

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

    Image RemovedImage Added

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

  4. Re-add the VelocityServices user and grant Full control. Click OK.