Velocity Unattended Update
- Anand Rajaraman
- Del Gonzalez
This section describes the general procedure that has to be followed for setting up an unattended Velocity Server/Client/Workstation update. Further, the XML file configuration changes that need to be followed during the Velocity Server/Client/Workstation updates are also discussed in the below sub-sections.
Note: Before setting up an unattended update make sure you configure firewall rules through your deployment tools
The unattended Velocity updates for Server/Client/Workstation are available from the Identiv websites. To set up an unattended update the user must complete these tasks:
Download the Unattendedupdate(build-3.8.6).zip
Extract the .zip file
Locate the Unattededupdate.xml file from the extracted zip file
This UnattendedUpdate(build-3.8.6).zip contains a configuration file named UnattendedUpdate.xml that allows the user to define the options needed to be auto-selected during the update without user intervention. The unattended update is compatible with any deployment software.
Note: For software deployment purposes Microsoft's System Center Configuration Manager (SCCM), PDQ Deploy, etc., can be used
Each section in the UnattendedUpdate.xml configuration file mentioned below has three parts:
Description: A message box that the user would see, or otherwise a description of the item being silenced.
For example, <Description> tag contains setting definitions for the possible system reboot that takes place after the update is finished
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
After making the necessary changes in the respective XML configuration files for unattended Server/Client/Workstation update, the extracted folder is zipped.
Compress the .zip file back to UnattendedUpdate(build-3.8.6).zip
To deploy the Velocity update using the deployment tool:
Upload the UnattendedUpdate(build-3.8.6).zip file as a package/application in the deployment tool
Note: Make configurations to select the list of all client machines where update needs to be appliedConfigure such that the deployment application runs the VelocityUpdate.exe file (this exe file will read all the configurations/options from the XML file and will update accordingly).
Make configuration to run the VelocityUpdate.exe as a Domain Admin user
When the deployment process starts, the deployment tool will automatically download the zip files to the server, extract the zip, and will run VelocityUpdate.exe as Admin and the update will continue according to the options configured in the UnattendedUpdate.xml file.
Note: For any information about errors that may occur during the unattended update operation, refer to the Velocity_Update.txt log file in the velocity install location.
Unattended Update XML Configuration
Unattended Update XML Configuration
The UnattendedUpdate.xml file for the Velocity unattended update setup is given:
<Configuration>
<!--
If you plan to add an optional execute application (IE Web Console) you need to add it to this file in a specific way.
The XMl node needs to match the title in the updatemanifest.ini file instruction. See The VelocityWebServicesClient as
and example of this.
-->
<SQL2012NC>
<Description>If Microsoft SQL Server 2012 Native Client - QFE is not installed
Velocity updater will upgrade your system's SQL Connectivity to Microsoft SQL Server 2012 Native Client - QFE with TLS1.2 support.
After it finishes, you may choose to reboot at a later time and continue with Velocity Update and then restart your machine.
Alternatively, if you choose to restart right away, you will need to re-run this update.
</Description>
<PossibleValues>Continue=0; Reboot=1</PossibleValues>
<Value>0</Value>
</SQL2012NC>
<RunAsAdmin>
<Description>Message:
Your Windows profile may not have sufficient privileges to install this software.
It is recommended that a profile that is a member of the local group 'GetAdminGroupName(Computer)' is used.
If you continue, you may encounter an error while applying the update.
Do you want to continue anyway?</Description>
<PossibleValues>No=0; Yes=1</PossibleValues>
<Value>0</Value>
</RunAsAdmin>
<BackupDB>
<Description>ServerOnly: Would you like to backup database before applying update?</Description>
<PossibleValues>No=0; Yes=1</PossibleValues>
<Value>0</Value>
</BackupDB>
<RestartServices>
<Description>ServerOnly: Would you like to restart the services after applying update?</Description>
<PossibleValues>No=0; Yes=1</PossibleValues>
<Value>0</Value>
</RestartServices>
<RestartVelocity>
<Description>Would you like to restart Velocity after applying update?</Description>
<PossibleValues>No=0; Yes=1</PossibleValues>
<Value>0</Value>
</RestartVelocity>
<!-- Web Console does not support unattended mode at this time and should not be used
<VelocityWebServicesClient>
<Description>Would you like install the Velocity Web Console?</Description>
<PossibleValues>No=0; Yes=1</PossibleValues>
<Value>0</Value>
</VelocityWebServicesClient>
-->
<ServiceInfo>
<Description>Provide service information for the login account used.</Description>
<UserName></UserName>
<Password></Password>
</ServiceInfo>
<RebootRequired>
<Description>Something caused a requirement that the computer needs to reboot.
Do you want the computer to reboot after the update completes?
</Description>
<PossibleValues>No=0; Yes=1</PossibleValues>
<Value>0</Value>
</RebootRequired>
</Configuration>
The list below describes the important Velocity Server/Client/Workstation Update use case scenarios.
Unattended Server Update
In the use case example below, the user indicates they want to update MS SQL server 2012, backing up the Database before the update and the user would like to restart the Velocity services after the update is applied.
Tag Names | Tag Value(s) | Tag Description |
<SQL2012NC> | Continue=0; Reboot=1; Note: “1” indicates reboot the machine at a later time and continue with Velocity Update and then restart your machine. “0” means to restart right away and re-run the update. | If Microsoft SQL Server 2012 Native Client - QFE is not installed Velocity updater will upgrade your system's SQL Connectivity to Microsoft SQL Server 2012 Native Client - QFE with TLS1.2 support. |
<BackupDB> | No=0; Yes=1 | ServerOnly: Would you like to backup the database before applying an update? |
<RestartServices> | No=0; Yes=1 | ServerOnly: Would you like to restart the services after applying the update? |
<RestartVelocity> | No=0; Yes=1 | Would you like to restart Velocity after applying the update? |
<ServiceInfo> | User Name and Password | Provide service information for the login account used |
Unattended Workstation Update
In the use case example below, the user indicates restarting Velocity after applying the update and providing service information for the account that is used.
Tag Names | Tag Value | Tag Description |
<RestartVelocity> | No=0; Yes=1 | Would you like to restart Velocity after applying update? |
<ServiceInfo > | User Name and Password | Provide service information for the login account used. |
Unattended Client Update
Note: Before the unattended client update, the Velocity server should be updated.
In the use case example below, the user indicates backing up the database before the update, restarting Velocity services and Velocity client after the update is applied.
Tag Names | Tag Value | Tag Description |
<BackupDB> | No=0; Yes=1 | ServerOnly: Would you like to back up the database before applying the update? |
<RestartServices> | No=0; Yes=1 | ServerOnly: Would you like to restart the services after applying the update? |
<RestartVelocity> | No=0; Yes=1 | Would you like to restart Velocity after applying the update? |