The Velocity Installer and Updater have been modified to work with deployment software such as Microsoft's System Center Configuration Manager (SCCM), PDQ Deploy, etc.
You may also use home-grown deployment scripts using 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 that the updater would normally present to the user.
The second part is the set of files that make up the update itself.
Note: The unattended Velocity installation process only supports Server, Client, and Workstation installations.
For split-server installations, you must manually run the Velocity Installer on the SQL Server computer and select the “Data” (database only) install option. Then you may install the Velocity application server using the unattended installation package.
Note: The unattended Velocity installation or update is NOT supported on a split server configuration (remote SQL Server). The user should manually go through the installation/update process with the database machine name edited in the respective server and client XML configuration files. Also, the unattended method does NOT support Velocity Web Services Client (VWSC) installation/update.