|
Critical Update for Velocity 3.0 (KB109) Release Notes |
|
|
January 31, 2007 |
|
Critical Update for Velocity 3.0 (KB109) Released 03/08/2007 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.
KB109 - United States Daylight Savings Time Zone Update for 2007
Download and install the update by executing the EXE file on the Velocity Security Domain server which will launch the update wizard. You do not need take the update to each Velocity client and run it.
Background: In August of 2005 the United States Congress passed the Energy Policy Act, which changes the dates of both the start and end of daylight saving time (DST). When this law goes into effect in 2007, DST will start three weeks earlier (2:00 A.M. on the second Sunday in March) and will end one week later (2:00 A.M. on the first Sunday in November) than what had traditionally occurred.
To address this issue Microsoft has released an update described in Microsoft Article ID: 928388
Problem: After applying the Microsoft update the “Time zone where controller is located” selection on the Velocity Controller Property window may be empty. You must then select a time zone to be able to save the controller properties.
Cause: Mexico has not adopted the DST changes that were made in the United States. Therefore, the Microsoft update splits time zones that used to be shared between the United States and Mexico (i.e., Pacific Standard Time).
The Velocity database stores host time zone information for each controller. If a Velocity controller references a Time zone that has been altered by the Microsoft update, then when the Controller Properties window is opened, a matching time zone cannot be found and the selection is empty.
Resolution: Install Critical Update for Velocity 3.0 (KB109) on the Velocity server to update the Velocity database with the new time zone information created by the above referenced Microsoft update. When the fix is installed a scan of the Windows registry is performed and the program will attempt to patch the controller host time zone information in the Velocity database. The program will list any changes made to controller database.
Users of previous versions of Velocity (1.0 to 2.6 Service Pack 2) must manually change the time zone in each controller's properties after applying the Microsoft update where effected.