Versions Compared

Key

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

...

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 can 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, 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. For example, after restoring the database to a new system, the local computer name can be NewSystem1 vel1.local.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 NewServer1 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 NewServer1 vel1.remote.system.

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). For example, after restoring the database to a new server, the server name can be NewServer1 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 NewServer1 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 NewServer1 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 NewServer1 vel1.sdserver.system.

Registry

ServerName

SQL Server Instance name.

Workstations

WorkstationName

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

...

12. Reinstall the Server Extensions that are used.

Refer https://identivdocs.atlassian.net/wiki/x/n4B9ZQ on how to add Velocity Database in Database machine for Split Server Installation.

To install a server extension:

...