Update for Velocity 3.0 (KB238) Release Notes

 

 

Update for Velocity 3.0 (KB238) Released 01/14/2008 contains file changes to address the following knowledge base articles:

 

Download and install the update by executing the EXE file on the Velocity Security Domain server which will launch the update wizard. Once the update completes, as each client re-connects to the Velocity Security Domain, updates will automatically be applied. You do not need take the update to each Velocity client and run it.

Note: Requirements & planning for a system update

 

Before applying an update to the Velocity server, you must plan for independent client down time until the the update has been applied to each client respectively, in order for each client to stay in sync with the server system to prevent application errors and possible database corruption.

 

Before you install Velocity updates, the following requirements must be met:

Applying updates to the Velocity Server:

  • You must be logged into the Velocity server computer with a Windows account that has local Administrative privileges in order to install updates. Velocity Update may install new files and register them with the local Windows environment. On a Windows member server, you must be a member of the local Administrators group. On a domain or backup controller, you must logged in as Administrator or be a member of Domain Admins.

  • You must also be logged into the Velocity server computer with a Windows account that has 'sysadmin' privileges in the Velocity SQL Server. Updates may include schema changes to the Velocity database or modifications to SQL Server system databases. In order to make those changes, 'sysadmin' privileges is required. If the SQL Server used by Velocity is located on another computer on the network, your Windows account must have local Administrative privileges as well as 'sysadmin' privileges on the remote SQL Server.

Applying updates to the Velocity Client:

  • When updates are applied to the Velocity server, you will be advised that all Velocity clients will be updated the next time they are launched. In order for the updates to be applied to the client computer, the person logged into Windows at the time Velocity is launched must have local Administrative privileges. This is required in order for Velocity Update to apply file and folder and possibly Windows Registry changes to the Windows environment. If a non Administrator launches the Velocity client after an update has been applied to the Velocity server, they will be advised that the update cannot be run without local Administrative privileges and Velocity will exit.
This update reorganizes Roles to the advanced scheme used in Velocity 3.1. Roles have changed as a result of customer feedback.  The new Role scheme significantly enhances performance when adding new Controllers, Workstations, and Roles, and drastically reduces the size of your database.  It has been made available in advance of Velocity 3.1.

The new Role scheme eliminates the tedious selection of each Workstation in Roles and has removed the necessity to store the alarms & events in the database when a Port, XBox, Controller, or controller point is denied access.

This allows the Operator to have his/her Role profile follow them providing they have access to the Velocity Workstation they are attempting to use.  This allows you to create new Roles and assign permission to application components and hardware without the need to manually set or copy those permissions to each individual workstation.  In its place, added to Roles is a new Workstation folder.  This allows you to grant or deny access to members by simply selecting or deselecting a Workstation instead of traversing each Workstation and un-checking all the permissions.

For Routing, the implications are that it is now by Role and not by Workstation.  As before, the Velocity Security Domain validates that each client machine running Velocity is allowed to receive an alarm or event.  Using the advanced 3.1 scheme, the service determines if the client is logged in with an Operator account with access to a Role that can receive a particular alarm or event, regardless of what Workstation they are at.

Installation Requirements

If you are currently using Roles to deny permissions by Workstation, before running this update you will need to run the “Roles with Permissions” report in Velocity.  Following the update, Roles will be reset to factory default.  Administrators will have full rights to everything and all other Roles will be reset to full permissions to the hardware and no permissions to application areas with the exception of “Supervisors”, “Badging Personnel”, and “Officers”, which will be restored to the factory defaults the same as following installation.

NOTE:  The update will truncate all Role permissions and re-create your Roles, keeping the Role Members in tact but will erase the permissions. Backup your Velocity database in the event a problem should occur. The update can be re-run without incident but once started the changes are irreversible.

After applying the update, use the “Roles with Permissions” report to reapply the restrictions you want on each Role.  It may be necessary to create new Roles and add Operators to more than one Role in order to suit your organization.  An Operator will have the sum of all their application permissions when members of more than one Role.
 

Last modified:  Jan. 14, 2008 14:44:45