Velocity Client/Server Update

Owned by Anand Rajaraman
Last updated: Jun 20, 2024 by Del Gonzalez
4 min read

The Windows Client should be in the same domain as the Windows server. When updates are applied to the Velocity Server, all Velocity Clients will be updated the next time they are launched.

For the Velocity updates to be applied to the client computer, the person logged in to Windows at the time Velocity is launched must have local administrative privileges.

Updating Velocity Client from the same major.minor Version

After updating the Velocity server to a newer version with the same major.minor version of Velocity  (e.g., from v3.8.5 to v3.8.6), the client computers will be automatically updated when started with administrator privileges. Therefore it is recommended that after updating the Velocity server, all clients should be initially started by “Run as administrator” to ensure the proper Administrator privileges are in effect.

  • When a user with the Administrator credentials logs in to the Velocity client system, the Velocity application is launched, the updates are applied, and the client system is updated to the the same version as the Velocity server.

  • When a person with non Administrative privileges is logged on to the client machine, then Velocity can be updated by starting the Velocity client  by “Run as administrator” and entering the administrative credentials in the User Account Control window as shown:

Velocity Client Update Steps

The following update steps should be followed in Windows 10 Pro Client.

  1. Right-click the Velocity icon in the Windows Client system and select Run as administrator.

  2. The screen proceeds as follows:

  3. After reading the End User Agreement (scroll to the bottom),

  4. Click Accept

  5. Click ‘Yes’ to Start Velocity after the update is complete

    The update screen proceeds as follows:

     

After establishing a connection with the Windows Server, the updated version of the Velocity Application opens:

Updating Velocity Client to a different major.minor version

When the Velocity server has been updated to a new major.minor version of Velocity  (e.g., from v3.7 to v3.8.6), then the Velocity clients will not be able to auto-update when launched and you will see a popup message to notify you that there is a mismatch with the Velocity client version that you are trying to connect. A sample screen like the one below appears:

In this case, you should:

  • Run the same Velocity updater executable you previously used on the Velocity Server.  For example, if you have used Velocity_Update_3.8.6.exe to update the Velocity Server, then the same executable should be used to update the Velocity Client.

The sample steps for a Velocity Client updater 3.8.6, the same as the Windows Server, are shown:

  1. Right-click the Velocity Updater and select Run as administrator

  2. The screen appears as below:

  3. Click ‘Yes’ if you want to start Velocity after the update.

    The screen progress appears as below:

     

  4. Click OK on successful update

    The Velocity Application opens automatically after the update, as shown.