For deploying the software en-mass, we offer two flavors of deployment script: a Powershell script and a batch file. Each script is custom made for your account. You can get to them any time from your builds page
Each time the script is ran, it first checks to see if the software is already installed and exits if it is. This means that you cannot use the scripts to update the software, only to install it. But it also means that you can just push the script out globally on a reoccurring basis without worrying about high resource consumption. If you want to know how to update the software en-mass refer to the auto update documentation.
If the script sees that the software is not installed, then it downloads the latest build from your account. This means that the same script that you used to deploy version 220.127.116.11 of the software will also deploy 18.104.22.168 without modification. To see which version of the software will be deployed, just look at which version you currently have built on the builds page.