Velocity Unattended Installation and Unattended Update

The Velocity Installer and Updater have been modified to work with deployment software such as Microsoft's System Center Configuration Manager (SCCM) and PDQ Deploy.

You can also use home-grown deployment scripts, such as Windows Batch files or PowerShell scripts, to install and update Velocity.

The Velocity Unattended Installer and Velocity Unattended Updater packages contain two parts:

The first part is the XML file (UnattendedInstall.xml, see below for more info), which controls how to automatically answer any questions the updater presents, typically to the user.
The second part consists of the files that comprise the update itself.

The unattended Velocity installation process only supports installations on Server, Client, and Workstation.

For split-server installations, you must manually run the Velocity Installer on the SQL Server computer and select the “Data” (database only) install option. You can then install the Velocity application server using the unattended installation package.

The unattended Velocity installation or update is NOT supported on a split server configuration (remote SQL Server). The user must manually complete the installation/update process, editing the database machine name in the server and client XML configuration files. Additionally, the unattended method does not support the installation or update of the Velocity Web Services Client (VWSC).