Velocity Client/Server Update

Updating Velocity Client from the same Version

After updating the Velocity server to a newer revision of the same major.minor version of Velocity (e.g. 3.8.1 to 3.8.2) 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 a newer version same 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 Client.

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

   

2. The screen proceeds as follows:
   

   

3. After reading the End User Agreement,
   

   

4. Click Accept.
   

   

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

   

   
   The update screen proceeds as follows:

   
   

   

After establishing a connection with the Windows Server, the updated version of the Velocity Application opens as in the Client window as shown:

Updating Velocity Client to a different version

When the Velocity server has been updated to a new major.minor version of Velocity  (e.g.,  from v3.7 to v3.8.1) then the Velocity clients will not be able to auto-update when run and you will see a popup message to notify 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 with which you previously updated the Velocity server.  For example, if you have used the 3.8.1.XXXX updater to update the Velocity server, then the same version should be used to update the Velocity client system.

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

1. Right the Velocity Updater and 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.
   

   

Unattended Client Update

The Velocity client unattended update package is delivered as a .zip file, for example, UnattendedUpdate(build-3.8.0.xxxx).zip. 

This package contains a configuration file named UnattendedInstall.xml that allows the user to define the options needed to be auto-selected during the installation without user intervention. The unattended client update should be compatible with any deployment software.

The process of updating the Velocity client in unattended mode involves the following steps:

1. Download the “UnattendedUpdate(build-3.8.0.xxxx).zip”.

2. Extract the .zip file.

3. Locate the "unattededupdate.xml" file from the extracted zip file.
   
   A portion of the sample  "unattededupdate.xml" file is highlighted below.
   

   25 <BackupDB> 

   26 <Description>ServerOnly: Would you like to backup database before applying update?</Description>

   27 <PossibleValues>No=0; Yes=1</PossibleValues>

   28 <Value>0</Value>

   29 </BackupDB>

   30 <RestartServices> 

   31 <Description>ServerOnly: Would you like to restart the services after applying update?</Description>

   32 <PossibleValues>No=0; Yes=1</PossibleValues>

   33 <Value>0</Value>

   34 </RestartServices>

   35 <RestartVelocity> 

   36 <Description>Would you like to restart Velocity after applying update?</Description>

   37 <PossibleValues>No=0; Yes=1</PossibleValues>

   38 <Value>1</Value>

   39 </RestartVelocity>
   
   Each section in the above sample file has three parts:

   • Description:  A message box that the user would see, or otherwise a description of the item being silenced. For example, the <Description> tag contains setting definitions and values to use during the backup database before the update.

   • PossibleValues: A name/value pair of possible choices for the current item. For example, <PossibleValues> tag values are by default set to 0. To modify the answers, simply change the number between the <Value> tag.

   • Value: The chosen value that is either 0 or 1 that the Update will use if required by the update logic flow.

4. Compress the .zip file back to “UnattendedUpdate(build-3.8.0.xxxx).zip”. 

To deploy the Velocity update using the deployment tool:

1. Upload the “UnattendedUpdate(build-3.8.0.xxxx).zip” file as a package/application in the deployment tool.

2. Make configurations to select the list of all client machines where update needs to be applied

3. Configure such that the deployment application runs the UnattendedUpdate.exe file (this exe file will read all the configurations/options from the XML file and will update accordingly)

4. Make configuration to run the UnattendedUpdate.exe as a (domain) Admin user. 

When the deployment process starts, the deployment tool will automatically download the zip files to all the client machines, extract the zip, and will run UnattendedUpdate.exe as Admin (even if the client machine is logged in as an operator/non-admin user) and the update will continue according to the options configured in the unattendedupdate.xml file(particularly in the above sample highlighted section).