...
The Velocity database file you will be moving is the backup file (.BAK). The database backup procedure differs depending on whether you are using:
...
Right-click on the Velocity Service Control Manager (SCM) icon on the source computer, stop all Velocity services, then select the Exit option to exit SCM.
Open Microsoft SQL Server Management Studio; from the Windows desktop, select Start->Microsoft Server Tools 18->Microsoft Server Management Studio 18.
The Connect to Server dialog appears:
Click Connect.
The Microsoft SQL Server Management Studio screen appears
In the left tree pane, expand the Databases folder to reveal the Velocity database.
Right-click on the Velocity database.
A pop-up menu appears.Select Tasks -> Back Up...
The Back-Up Database – Velocity dialog appears:
If one or more backups are already displayed in the Destination pane, remove them by highlighting the device and clicking the Remove button.
Click the Add... button to the right of the Destination pane.
The Select Backup Destination dialog appears:
Click to select the File name radio button.
In the ‘File name’ field, place your cursor at the end of the path and type a name for the database file you are about to create. For example, Velocity_backup.bak.
Make note of the path where this backup file is created, because you will need to access the file during a later step.
Click OK to close this dialog and return to the Back Up Database – Velocity dialog.
The new file name now appears in the Destination pane.
Click OK again.
The current Velocity database is backed up to the selected destination. A message appears indicating that the database was backed up successfully.
Click OK.
Exit the SQL Server Management Studio.
Moving a Velocity 2.6 SP2 Database
To make sure no data or history is lost; the following files must be copied to the target PC:
SNIB2 Encryption files (.DAT)
Velocity archives (detached databases)
Velocity database backup
To move a Velocity 2.6 SP2 database from one computer to another:
If your installation does not use SNIB2 ports, skip Steps 1 – 3 and go to Step 4.
On the source PC, open Windows Explorer and navigate to C:\Program Files\Hirsch Electronics\Velocity.
Scroll down until you see files with the general format velocitytmpxxx.dat, where xxx is the address of the Velocity SNIB2 port.
These .dat files are the encryption key files Velocity generates for each of its master SNIBs.
There should be one .dat file for each SNIB2 port.Copy all encryption .dat files to a thumb drive, media, or other network-accessible location.
Copy the Velocity backup file created previously using this procedure:
On the source computer, go to the appropriate \Backup subdirectory on your version of SQL Server
Locate the backup created previously.
Copy this backup file to a thumb drive, media, or other network-accessible location.
Right-click on the Velocity Service Control Manager icon on the target PC, stop all Velocity services and then select the Exit option to exit SCM.
If your installation does not use SNIB2 ports, skip Steps 6–7and go to Step 8Copy the source PC’s .dat files from the thumb drive, media, or other network-accessible location to the C:\Program Files\Hirsch Electronics\Velocity subdirectory on the target PC.
Check the permissions of the .dat file(s). To do this:
Right-click on the .dat file.
Select Properties then click the Security tab.
Highlight the Velocity Service account as shown below.
.png?version=1&modificationDate=1633410377810&cacheVersion=1&api=v2&width=408)
If you have any Velocity archive files, you need to copy these files as well so that you don't lose any of the history stored on these archives.
To move the Velocity archive files:On the source PC, locate the VelocityArchivexxx.mdf and VelocityArchivexxx_log.ldf file (where xxx is the time and date when the file was created) in the C:\Program Files\Microsoft SQL Server\MSSQL.1\ MSSQL\Data subdirectory.
Copy these files to a thumb drive, media, or other network-accessible location.
On the target PC, copy the VelocityArchivexxx.mdf and VelocityArchivexxx_log.ldf files to the same SQL Server subdirectory specified in Step 8a.
On the target PC, make a backup of the current database and store it under a name, such as Velocity_default_db.bak.
This database can be used later as a comparison to indicate whether you need to modify (or add rows) tables in the migrated database or kept in case you need to restore the original.Copy the database backup file created previously from the thumb drive, media, or other network-accessible location to the appropriate SQL Server backup subdirectory:
For MSDE or SQL 7-> select C:\MSSQL 7\Backup
For SQL 2000->select C:\Program Files\Microsoft SQL Server\MSSQL\Backup
On the target PC, open the SQL Server Enterprise Manager by selecting Start > Programs, then:
For MSDE or SQL 7-> select Hirsch Electronics Velocity -> SQL Database Manager
For SQL 2000->select Microsoft SQL Server -> Enterprise Manager
The SQL Server Enterprise Manager screen appears like this example:
From the left tree pane, expand the Databases folder to reveal the Velocity database.
Right-click on the Velocity database.
A pop-up option list appears.
Select All Tasks > Restore Database...
The Restore Database dialog box appears like this example:
.png?version=1&modificationDate=1633410378643&cacheVersion=1&api=v2&width=374)
Click to select the ‘From device:’ radio button then click the Select Devices... button.
The Choose Restore Devices dialog box appears.Click Add... then locate and select the backup file you copied from the source PC.
Click OK until the Restore Database dialog box reappears.
The .bak file to be restored should now appear in the bottom window like this example:
.png?version=1&modificationDate=1633410378551&cacheVersion=1&api=v2&width=374)
Click the Options tab.
Make sure the ‘Force restore over existing database’ box is checked.
Click OK.
The current Velocity database is overwritten. When it is completed successfully, a message appears.
Click OK once again.
The main page appears.
Right-click on the Velocity database and select the Refresh option.
Expand the Velocity database and highlight Tables from the left pane.
A list of Velocity tables appears like in the example below:.png?version=1&modificationDate=1633410378445&cacheVersion=1&api=v2&width=476)
Right-click on the following tables and select Open Table -> Return all Rows, then make the changes specified.
...
For this table...
...
Select this column...
...
And enter...
...
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.)
...
Servers
...
Server_Name
...
Name of the new Velocity Server (all UPPERCASE)
...
ServerExtensions
...
RemoteComputerName
...
Name of the new Velocity Server (all UPPERCASE)
...
Workstations
...
WorkstationName
...
Name of the new Velocity Server for WorkstationID=1 (all UPPERCASE)
After each change, click outside the edited row for the changes to take effect.
25. Minimize, but do not close, the SQL Server Database Manager.
You must verify that everything is working properly before closing SQL Server.
26. Open Velocity Service Control Manager and start all Velocity Services starting with the Security Domain Service, then the DIGI*TRAC Service, then the Extension Service, then finally the CCTV Service.
27. Launch Velocity.
The source database should now be running on the Velocity target PC.
Moving a Velocity 3.0 Database
To make sure no data or history is lost; the following files must be copied to the target PC:
SNIB2 Encryption files (.DAT)
Velocity archives (detached databases)
Velocity database backup
To move a Velocity 3.0 database from one computer to another:
If your installation does not use SNIB2 ports, skip Steps 1 – 3 and go to Step 4.
On the source PC, open Windows Explorer and navigate to C:\Program Files\Hirsch Electronics\Velocity.
Scroll down until you see files with the general format velocitytmpxxx.dat, where xxx is the address of the Velocity SNIB2 port.
These .dat files are the encryption key files Velocity generates for each of its master SNIB2s.
There should be one .dat file for each SNIB2 port.Copy all encryption .dat files to a thumb drive, media, or other network-accessible location.
Copy the Velocity backup file created previously using this procedure:
On the source computer, go to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup.
Locate the Velocity backup created previously.
Copy this backup file to a thumb drive, media, or other network-accessible location.
Right-click on the Velocity Service Control Manager icon on the target PC, stop all Velocity services and then select the Exit option to exit SCM.
If your installation does not use SNIB2 ports, skip Steps 6–7and go to Step 8Copy the source PC’s .dat files from the thumb drive, media, or other network-accessible location to the C:\Program Files\Hirsch Electronics\Velocity subdirectory on the target PC.
Check the permissions of the .dat file(s). To do this:
Right-click on the .dat file.
Select Properties then click the Security tab.
Highlight the Velocity Service account as shown below.
Check the ‘Allow’ box on the Full Control line.
If you are not running on a domain or are not using SNIB2 ports, ignore this step and proceed to Step 8.
If you have any Velocity archive files, you need to copy these files as well so that you don't lose any of the history stored on these archives.
To move the Velocity archive files:
On the source PC, locate the VelocityArchivexxx.mdf and VelocityArchivexxx_log.ldf file (where xxx is the time and date when the file was created) in the C:\Program Files\Microsoft SQL Server\MSSQL.1\ MSSQL\Data subdirectory.
Copy these files to a thumb drive, media, or other network-accessible location.
On the target PC, copy the VelocityArchivexxx.mdf and VelocityArchivexxx_log.ldf files to the same SQL Server subdirectory specified in Step 8a.
On the target PC, make a backup of the current database and store it under a name, such as Velocity_default_db.bak.
This database can be used later as a comparison to indicate whether you need to modify (or add rows) tables in the migrated database or kept in case you need to restore the original.
Copy the database backup file created previously from the thumb drive, media, or other network-accessible location to the C:\Program Files\Microsoft SQL Server\MSSQL.1\ MSSQL\Backup
On the target PC desktop, open the SQL Server Management Studio by selecting Start > All Programs > Microsoft SQL Server 2005 > SQL Server Management Studio (or SQL Server Management Studio Express)
The Connect to Server dialog box appears like this example:
.png?version=1&modificationDate=1633410377101&cacheVersion=1&api=v2)
Click Connect.
The SQL Server Management Studio screen appears like in this example:.png?version=1&modificationDate=1633410376947&cacheVersion=1&api=v2)
From the left tree pane, expand the Databases folder to reveal the Velocity database.
Right-click on the Velocity database.
A pop-up option list appears.
Select Tasks > Restore > Database...
The Restore Database – Velocity dialog box appears like this example:
.png?version=1&modificationDate=1633410376852&cacheVersion=1&api=v2)
Click to select the ‘From device:’ radio button then click the browse button.
The Specify Backup dialog box appears like in this example:
.png?version=1&modificationDate=1633410376760&cacheVersion=1&api=v2)
Click Add... then locate and select the backup file you copied from the source PC.
Click OK until the Restore Database dialog box reappears.
The appropriate .bak file to be restored should now appear in the bottom window.
Click the Options tab.
Make sure the ‘Overwrite the existing database’ box is checked.
Click OK.
The current Velocity database is overwritten. When it is completed successfully, a message appears.
Click OK once again.
The main page appears.
Right-click on the Velocity database and select the Refresh option.
Expand the Velocity database and highlight Tables from the left pane.
A list of Velocity tables appear like this example:.png?version=1&modificationDate=1633410376660&cacheVersion=1&api=v2)
Right-click on the following tables and select Open Table, then make the changes specified.
...
In this table...
...
Select this column...
...
And enter this data:
...
MiscProperties
...
AuthenticationPath
...
If using local Windows accounts, the name of the local computer. If using domain accounts, the Windows Domain name.
...
UseDomainAuthentication
...
0=Use Local accounts
1=Use Domain accounts,
...
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=SEC URITY,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.)
...
DirectorySource
...
If using local Windows accounts, update all rows to the name of the local computer. (for example: \\Hirsch)
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)
...
Workstations
...
WorkstationName
...
Name of the Velocity Server for WorkstationID=1 (all UPPERCASE)
After each change, click outside the edited row for the changes to take effect.
26. Minimize, but do not close, the SQL Server Database Manager.
You must verify that everything is working properly before closing SQL Server.
27. Open Velocity Service Control Manager and start all Velocity Services starting with the Security Domain Service, then the DIGI*TRAC Service, then the Extension Service, then finally the CCTV Service.
28. Launch Velocity.
The source database should now be running on the Velocity target PC.
Moving a Velocity 3.1 Database
To make sure no data or history is lost; the following files must be copied to the target PC:
SNIB2 Encryption files (.DAT)
Velocity archives (detached databases)
Velocity database backup
To move a Velocity 3.1 database from one computer to another:
If your installation does not use SNIB2 ports, skip Steps 1 – 3 and go to Step 4.
On the source PC, open Windows Explorer and navigate to C:\Program Files\Hirsch Electronics\Velocity.
Scroll down until you see files with the general format velocitytmpxxx.dat, where xxx is the address of the Velocity SNIB2 port.
These .dat files are encryption key files for the individual SNIB2s this Velocity system controls.
There should be one .dat file for each SNIB2 port.Copy all encryption .dat files to a thumb drive, media, or other network-accessible location.
Copy the Velocity backup file created previously using this procedure:
On the source computer, go to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup.
Locate the Velocity backup created previously.
Copy this backup file to a thumb drive, media, or other network-accessible location.
Right-click on the Velocity Service Control Manager icon on the target PC, stop all Velocity services and then select the Exit option to exit SCM.
If your installation does not use SNIB2 ports, skip Steps 6–7and go to Step 8Copy the source PC’s .dat files from the thumb drive, media, or other network-accessible location to the C:\Program Files\Hirsch Electronics\Velocity subdirectory on the target PC.
Check the permissions of the .dat file(s). To do this:
Right-click on the .dat file.
Select Properties then click the Security tab.
Highlight the Velocity Service account as shown below.
.png?version=1&modificationDate=1633410377810&cacheVersion=1&api=v2&width=442)
Check the ‘Allow’ box on the Full Control line.
If you are not running on a domain or are not using SNIB2 ports, ignore this step and proceed to Step 8.
If you have any Velocity archive files, you need to copy these files as well so that you don't lose any of the history stored on these archives.
To move the Velocity archive files:
On the source PC, locate the VelocityArchivexxx.mdf and VelocityArchivexxx_log.ldf file (where xxx is the time and date when the file was created) in the C:\Program Files\Microsoft SQL Server\MSSQL.1\ MSSQL\Data subdirectory.
Copy these files to a thumb drive, media, or other network-accessible location.
On the target PC, copy the VelocityArchivexxx.mdf and VelocityArchivexxx_log.ldf files to the same SQL Server subdirectory specified in Step 8a.
On the target PC, make a backup of the current database and store it under a name, such as Velocity_default_db.bak.
This database can be used later as a comparison to indicate whether you need to modify (or add rows) tables in the migrated database or kept in case you need to restore the original.
Copy the database backup created previously from the thumb drive, media, or other network-accessible location to the appropriate SQL Server backup subdirectory. This can be:
For SQL 2005, select C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup
For SQL 2008, select C:\Program Files\ Microsoft SQL Server\MSSQL.10.MSSQLSERVER\MSSQL
On the target PC, open the SQL Server Management Studio by selecting Start > All Programs > or Start > Programs, then:
For SQL 2005 Express, select Microsoft SQL Server 2005> SQL Server Management Studio Express
For SQL 2005, select Microsoft SQL Server 2005> SQL Server Management Studio
For SQL 2008, select Microsoft SQL Server 2005> SQL Server Management Studio
The Connect to Server dialog box appears like this example:
.png?version=1&modificationDate=1633410378352&cacheVersion=1&api=v2&width=272)
Click Connect.
The SQL Server Management Studio screen appears like this example:.png?version=1&modificationDate=1633410378260&cacheVersion=1&api=v2&width=408)
From the left tree pane, expand the Databases folder to reveal the Velocity database.
Right-click on the Velocity database.
A pop-up option list appears.
Select Tasks -> Restore -> Database...
The Restore Database – Velocity dialog box appears like in this example:
.png?version=1&modificationDate=1633410378166&cacheVersion=1&api=v2&width=374)
Click to select the ‘From device:’ radio button then click the browse button.
The Specify Backup dialog box appears like in this example:
.png?version=1&modificationDate=1633410378067&cacheVersion=1&api=v2&width=306)
Click Add... then locate and select the backup file you copied from the source PC.
Click OK until the Restore Database dialog box reappears.
The appropriate .bak file to be restored should now appear in the bottom window.
.png?version=1&modificationDate=1633410377970&cacheVersion=1&api=v2&width=374)
Click the Options tab.
Make sure the ‘Overwrite the existing database’ box is checked.
Click OK.
The current Velocity database is overwritten. When it is completed successfully, a message appears.
Click OK once again.
The main page appears.
Right-click on the Velocity database and select the Refresh option.
Expand the Velocity database and highlight Tables from the left pane.
A list of Velocity tables appear like this example:Right-click on the following tables and select Open Table (for SQL Server 2005) or Edit Top 200 Rows (for SQL Server 2008), then make the changes specified.
...
In this table...
...
Select this column...
...
And enter this data:
...
MiscProperties
...
AuthenticationPath
...
If using local Windows accounts, the name of the local computer. If using domain accounts, the Windows Domain name.
...
UseDomainAuthentication
...
0=Use Local accounts
1=Use Domain accounts,
...
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=SEC URITY,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.)
...
DirectorySource
...
If using local Windows accounts, update all rows to the name of the local computer. (for example: \\Hirsch)
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
...
ComputerName
Name of the Velocity Server (all UPPERCASE).
...
RemoteIP
...
RemoteServerIP
...
SDServer
...
ServerName
...
Workstations
...
WorkstationName
...
Name of the Velocity Server for WorkstationID=1 (all UPPERCASE)
After each change, click outside the edited row for the changes to take effect.
26. Minimize, but do not close, the SQL Server Database Manager.
You must verify that everything is working properly before closing SQL Server.
27. Open Velocity Service Control Manager and start all Velocity Services starting with the Security Domain Service, then the DIGI*TRAC Service, then the Extension Service, then finally the CCTV Service.
28. Launch Velocity.
The source database should now be running on the Velocity target PC.
Moving a Velocity 3.5 Database
Before you can move a Velocity 3.5 database over to a different Velocity 3.5 computer, you must first apply KB542 or later.
Before proceeding, make sure you have installed Velocity 3.5 on the target computer using the instructions in the Velocity 3.5 Installation Guide.
Currently, Microsoft SQL Server 2008 R2 is not supported.
To make sure no data or history is lost, the following files must be copied to the target computer:
Velocity database backup
SNIB2 Encryption files (.DAT)
Velocity archives (detached databases)
To move a Velocity 3.5 database from one computer to another:
If your installation does not use SNIB2 ports, skip Steps 1 – 3 and go to Step 4.
On the source PC, open Windows Explorer and navigate to C:\Program Files\Hirsch Electronics\Velocity.
Scroll down until you see files with the general format velocitytmpxxx.dat, where xxx is the address of the Velocity SNIB2 port.
These .dat files are encryption key files for the individual SNIB2s this Velocity system controls.
There should be one .dat file for each SNIB2 port.Copy all encryption .dat files to a thumb drive, media, or other network-accessible location.
Copy the Velocity backup file created previously using this procedure:
On the source computer, go to C:\Program Files\Microsoft SQLServer\MSSQL.10.MSSQLSERVER\MSSQL\Backup
Locate the Velocity backup created previously.
Copy this backup file to a USB drive, media, or other network-accessible location.
Right-click on the Velocity Service Control Manager icon on the target PC, stop all Velocity services and then select the Exit option to exit SCM.
If your installation does not use SNIB2 ports, skip Steps 6–7and go to Step 8Copy the source PC’s .dat files from the thumb drive, media, or other network-accessible location to the C:\Program Files\Hirsch Electronics\Velocity subdirectory on the target PC.
Check the permissions of the .dat file(s). To do this:
Right-click on the .dat file.
Select Properties then click the Security tab.
Highlight the Velocity Service account as shown below.
.png?version=1&modificationDate=1633410377810&cacheVersion=1&api=v2)
Check the ‘Allow’ box on the Full Control line.
If you are not running on a domain or are not using SNIB2 ports, ignore this step and proceed to Step 8.
If you have any Velocity archive files, you need to copy these files as well so that you don't lose any of the history stored on these archives.
To move the Velocity archive files:
On the source PC, locate the VelocityArchivexxx.mdf and VelocityArchivexxx_log.ldf file (where xxx is the time and date when the file was created) in the C:\Program Files\Microsoft SQL Server\MSSQL.10.MSSQLSERVER\ MSSQL\Data subdirectory.
Copy these files to a thumb drive, media, or other network-accessible location.
On the target PC, copy the VelocityArchivexxx.mdf and VelocityArchivexxx_log.ldf files to the same SQL Server subdirectory specified in Step 8a.
On the target PC, make a backup of the current database and store it under a name, such as Velocity_default_db.bak.
This database can be used later as a comparison to indicate whether you need to modify (or add rows) tables in the migrated database or kept in case you need to restore the original.
Copy the database backup created previously from the thumb drive, media, or other network-accessible location to the C:\Program Files\ Microsoft SQL Server\ MSSQL.10.MSSQLSERVER\MSSQL\Backup subdirectory
On the target PC, open the SQL Server Management Studio by selecting Start > All Programs or Start > Programs, then select Microsoft SQL Server 2008 > SQL Server Management Studio.
The Connect to Server dialog box appears:.png?version=1&modificationDate=1633410377723&cacheVersion=1&api=v2&width=238)
Click Connect.
The SQL Server Management Studio screen appears:.png?version=1&modificationDate=1633410377565&cacheVersion=1&api=v2&width=408)
From the left tree pane, expand the Databases folder to reveal the Velocity database.
Right-click on the Velocity database.
A pop-up option list appears.
Select Tasks -> Restore -> Database...
The Restore Database – Velocity dialog box appears:
.png?version=1&modificationDate=1633410377467&cacheVersion=1&api=v2)
Click to select the ‘From device…’ radio button then click the browse button.
The Specify Backup dialog box appears:
.png?version=1&modificationDate=1633410377372&cacheVersion=1&api=v2&width=238)
Click Add... then locate and select the backup file you copied from the source PC.
Click OK until the Restore Database dialog box reappears.
The appropriate .bak file to be restored should now appear in the bottom pane.
.png?version=1&modificationDate=1633410377279&cacheVersion=1&api=v2&width=374)
Click the Options tab.
Make sure the ‘Overwrite the existing database’ box is checked.
Click OK.
The current Velocity database is overwritten. When it is completed successfully, a message appears.
Click OK once again.
The main page appears.
Right-click on the Velocity database and select the Refresh option.
Expand the Velocity database and highlight Tables from the left pane.
A list of Velocity tables appear like in this example:.png?version=1&modificationDate=1633410377189&cacheVersion=1&api=v2)
Right-click on the following tables and select Edit Top 200 Rows, then make the changes specified.
...
In this table...
...
Select this column...
...
And enter this data:
...
MiscProperties
...
AuthenticationPath
...
If using local Windows accounts, the name of the local computer. If using domain accounts, the Windows Domain name.
...
UseDomainAuthentication
...
0=Use Local accounts
1=Use Domain accounts,
...
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=SEC URITY,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.)
...
DirectorySource
...
If using local Windows accounts, update all rows to the name of the local computer. (for example: \\Hirsch)
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
...
ComputerName
Name of the Velocity Server (all UPPERCASE).
...
RemoteIP
...
RemoteServerIP
...
SDServer
...
ServerName
...
Workstations
...
WorkstationName
...
Name of the Velocity Server for WorkstationID=1 (all UPPERCASE)
After each change, click outside the edited row for the changes to take effect.
26. Minimize, but do not close, the SQL Server Database Manager. You must verify that everything is working properly before closing SQL Server.
27. Open Velocity’s Service Control Manager and start all Velocity Services starting with the Security Domain Service, then the DIGI*TRAC Network Service, then the Extension Service, then finally the CCTV Service.
...
.
Moving a Velocity 3.6 Database
...