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 updates to be applied to the client computer, the person logged into the Windows at the time Velocity is found must have local administrative privileges.
Updating Velocity Client from the same major.minor Version
After updating the Velocity server to a newer revision of version with the same major. minor version of Velocity Velocity (e.g., 3 from v3.8.1 to 3v3.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 the the same 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:
...
After establishing a connection with the Windows Server, the updated version of the Velocity Application opens as the Client window as shown:
...
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.1), then the Velocity clients will not be able to auto-update when run, 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:
...