...
Unattended Update XML Configuration
The UnattendedUpdate XML configuration file for the Velocity unattended update setup is given:
...
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.
...