Update for Velocity 3.1 (KB610) Release Notes

   

Update for Velocity 3.1 (KB610) Released 09/06/2011. © 2011 Hirsch Electronics, LLC.

Contents

Update Instructions

New Features
      Support for 56-bit DESFire and MiFare ID cards—Wiegand Hex Pass-through
      Ability to Customize Alarm Inputs to Report as Events Only
      Support for Custom Active Directory User Group and User Names

Bug Fixes
      Installation
      Velocity Operation
      Reporting
      Printing
     
Documentation

Update Instructions

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

IMPORTANT:  If ANY of the Velocity Services or Processes fails to "STOP" automatically while applying the updates, use the "Task Manager" and select the "Processes" tab to manually end the process.

 

NOTE:  Applying (KB610) may take much longer than normal depending on the size of the database.  Please wait for the process to complete and DO NOT "End Task" while the Update is being applied.

 

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 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 be logged in as Administrator or be a member of Domain Admin.

  • 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.

For complete installation instructions, refer to the Velocity 3.1 Installation Guide or Velocity 3.1 Quick Install Guide.

New Features

Support for 56-bit DESFire and MiFare ID cards—Wiegand Hex Pass-through
Velocity now supports 56-bit DESFire Cards. Previously, card ids were limited to 48 bits. The new Wiegand Hex Pass-through setting in Velocity’s Enrollment manager enables a MATCH2 to read cards in a hexadecimal format. This new feature enables the use of cards that carry up to 62 bits of information, including DESFire and MiFare cards. To use this feature, you must have:

See the Velocity Administrator’s Guide or Velocity Help for more information on using this new feature.

Ability to Customize Alarm Inputs to Report as Events Only  
You can now customize specific inputs to report as events only. Previously, all inputs would automatically register as alarms. These modified alarms can retain all alarm functions while reporting as an event. For more information on using this feature, see Velocity Administrator’s Guide or Velocity Help.

Support for Custom Active Directory User Group and User Names
Velocity now supports the use of custom user group and user names. This setting prevents the system from using the default “Velocity Users” and "Velocity Services" group in Active Directory, and the default "VelocityServices" user that starts Velocity Services. Use of this feature requires advanced understanding of domain and database administration. Before implementing Custom Velocity Users Group Names, contact Hirsch Technical Support for instructions.

Bug Fixes

Installation

Velocity Update Fixed for German-localization
In a previous version of Velocity, stand-alone installations could fail to update on German-localized computers. The Velocity updater did not recognize the localized German Administrators group name. This bug has now been fixed. (Vel-800)

Velocity Operation

Renamed Expansion Inputs Now Automatically Update
Expansion inputs such as DVRs, time zones, and holidays now automatically update with the new name in the event viewer. In previous versions of Velocity, services would need to be restarted after an expansion input was renamed in order to see an updated name in the event viewer. (Vel-876)

Controller Time Zone Setting Now Saves on Windows 7
The setting “Time zone where controller is located” now saves properly on Windows 7 machines. In a previous version, this setting was not saving on Windows 7 systems. (Vel-977)

Credential Enrollment: Badge Template Added to Tab Order
The Badge Template box on the Credential Enrollment dialog box has been added to the tab order. When you use the TAB key to navigate through this page, the Badge Template box is now selected after the Description box. (Vel-993)

Changing Text to Date Data Type No Longer Produces Error
In a previous version, changing data entry field types from text to date could produce an error. The error arose after a Validate Exiting Data dialog box displayed non-conforming data. Clearing all non-conforming data after changing the UDF field from a text data type to a date data type has now been fixed. (Vel-964)

Added Default to SDSServerSetting to Prevent Database Lag
Events are now written to the Velocity database immediately using a default setting in the file SDServerSettings.ini. In the previous version, settings for this service were not included, which could create a lag between events and records in the database. In this fix, any current settings for SDServerSettings.ini will not be overwritten; this change only affects customers with no SDServerSettings default. (Vel-999)

Memory Leak in SQLTransaction Process Fixed
A memory leak was introduced by Microsoft in Windows 7 and Windows Server 2008 Service Pack 1. This issue has been fixed. (Vel-1066)

Memory Leak in Velocity DIGI*TRAC Service Fixed
A gradual memory leak that could cause the Velocity DIGI*TRAC service (DTService) to crash has now been fixed. (Vel-1054)

Windows Update KB2570791 Fix
Windows Update KB2570791 caused Velocity to fail when a user attempted to open Controller Properties on Windows XP and Server 2003 systems. This has now been fixed. (Vel-1268)

Reporting

Reports with Archived Data Fixed
In a previous version of Velocity, running a report that utilized archived data could interrupt Velocity Client operation. In this version, archived data is accessed in managed chunks, thereby allowing disk and processor time for other operations. This fix uses less system resources during a restore operation for running reports that need archived data. (Vel-619)

Reports Now Show All Active Credentials
Previously, running the Velocity report Active Credentials with UDFs 1, 2, and 3 would only report credentials with associated functions. Any active credentials without associated functions would not be reported. The Velocity report Active Credentials with UDFs 1, 2, and 3 now reports all active credentials, even when a credential does not have an assigned function. (Vel-781)

Archiving Reports Fixed
Previously, the database connection between the Report Manager and the Archive Log could create errors in the Archive Log. This issue has been fixed. (Vel-1102)

Printing

Printing Badges with a User-Defined Date Field Fixed
In a previous version of Velocity, attempting to print or preview a badge with an empty user-defined date field would result in an error. This has now been fixed. (Vel-925)

Documentation

SQL Support Statement Updated
SQL support statements have been modified in the Velocity Quick Installation Guide and Velocity Installation Guide. SQL support now includes Workgroup edition. (Vel-956)

Instructions for Wiegand Hex Pass-through Feature Added
Instructions for using the new Wiegand Hex Pass-through feature have been added to the Velocity Administrator’s Guide and Velocity Help. (Vel-1003)

Description and Support Statement for Custom User Groups Added
A description and support statement for using the new Custom User Group Names feature has been added to the Velocity Administrator’s Guide and Velocity Help. (Vel-1004)

Velocity Help Updates
Velocity Help now properly displays when the Help button is clicked in the “Verify Scanner Data” dialog box and the “PIV Reader” tab of the “Verify Scanner Data” dialog box. (Vel-1001 and Vel-1002)

NOTE:  After you apply the Velocity 3.1 Update, verify that the update successfully installed.  In Velocity, go to Help and select About Velocity and click the scroll bar to verify the current version number of the Update

Last modified:  September 2, 2011

© 2011  Hirsch Electronics, LLC.  All rights reserved.