|
Update for Velocity 3.0 (KB68) Release Notes |
|
|
|
|
Update for Velocity 3.0 (KB68) Released
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.
KB64 - PRB: Enrollment Manager
scanning
Symptom:
When the user scans a business card, drivers license or passport using the
ScanShell 800/1000 scanners or a smart card using the
Gemplus or Integrated Engineering readers to
populate user defined fields in Enrollment Manager, they receive the following
error message:
"The following unexpected application error occurred...
Function Name: frmEMScanner.CmdReadPIV_Click
FunctionSubItem: 16
Number 429
Description: ActiveX component can't create object"
Causes:
1.
The problem occurs because of an incompatibility between the HirschPIV.dll and
HirschEMScanner.dll.
2. The GemPlus reader drivers are absent and may be
required on some Windows computers.
Solution:
Install and register HirschEMScanner.dll version 1.0.0.78 dated
After
applying the update to the Security Domain, the user must launch the GemPlus reader driver installation. The file is named GemPCTwin_PC_SC_MSI_Installer_32_bits.msi on
each client machine.
Applies
To: DC4129
KB65 - PRB: DTLM & RQE changes to
Doors and Inputs in Velocity do not download to controllers
Symptom:
When a user changes a DTLM or RQE settings in either the Door or Input
window of Velocity and clicks OK, the changes are not downloaded to the
DIGI*TRAC
Case: A
defect in HirschDoor.dll & HirschInput.dll that track changes in the user
interface fail to detect changes to DTLM, RQE and state change reporting.
When the user clicks OK the window determines no changes were made and does not
download the new settings.
Solution:
Install HirschDoor.dll version
3.0.0.24
Applies
To: DC4124, DC4125, DC4126
KB66 - PRB: May not be able to delete
a time zone from Velocity. Dialog states the time zone is in use when it is not
Symptom:
When the user tries to delete a time zone from Velocity they receive a dialog
stating the time zone is in-use and cannot be deleted. The display shows the
time zone is in use by an expansion input when it is not configured that way in
the controller or any input.
Case:
The time zone component will display expansion relays as expansion inputs in
the in-use dialog. This will cause the user to look for the time zone
being in use in the wrong location.
Solution:
Install HirschTimeZone.dll
version 3.0.0.22
Applies
To: DC4119
KB67 - PRB: Firmware versions may not
display properly on the Controller and XBox windows
Symptom:
The firmware version on the Controller and XBox windows may be improperly
formatted when single digit firmware revisions are present, e.g. CCM 7.4.2
should read 7.4.02 and may be confused with a future firmware version 7.4.20 or
7.4.2 which would be newer than 7.4.02.
Cause:
The displays are not properly formatting the version number taken from the
Velocity database.
Solution:
Install HirschController.dll
version 3.0.0.23 December 04, 2006 and HirschXBox.dll
version 1.0.0.185 December 04, 2006 and register the files with Windows. These
files are available in Update
for Velocity 3.0 (KB68) and will automatically be installed on
each client once applied to the Security Domain.
Applies
To: DC4128