Update for Velocity 3.0 (KB108) Release Notes
 

January 31, 2007

 

Update for Velocity 3.0 (KB108) Released 03/20/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.

 
KB108 - Update for Velocity 3.0 (KB108) is a counterpart but not exclusive to the March 2007 Installation CD revision for Velocity 3.0, created to accommodate advanced network installations of Velocity utilizing OU’s (Organizational Units) within a Windows 2003 Server domain, Windows Vista, and 64-bit versions of Windows XP, Vista, and Server 2003.
 
The March 2007 Installation CD revision has a redesigned Setup.exe allowing the installer to select an OU in addition to root Domain’s to allow OU Trustee’s the ability to install Velocity using an OU instead of having to be a Windows Domain Admin during the install process and when new Velocity Operators accounts are created, when the persons (new operator) Windows credential does not previously exist on the network and must be created.
 
Update for Velocity 3.0 (KB108) can be applied to an existing installation of Velocity 3.0 and allow the same infrastructure to be taken advantage of without the new installation CD revision. The manager of the Velocity system can migrate the Velocity Users and Velocity Services groups, as well as the VelocityServices account used by the Velocity server-side system, to an OU and from that point forward, manage all Operators from an OU. This is facilitated by selecting an OU in the Network section of the SCM (Service Control Manger) residing in the Windows tray. Depending on the configuration of the operating system, Velocity Users may be the only Windows group located on the domain. In cases where the SQL Server is remote or the operating system is a domain controller, the additional group mentioned above will also reside on the domain.