| Previous Topic (Installing) | Up (Contents) | Next Topic (Downgrading) |
Upgrading Your Installation
Important Notice if You are Upgrading from Version 2.7 to 3.0
Due to the large amount of internal changes to the client and repository structure and how data is stored, you need to reinstall the Deadline 3.0 client on all of your machines, and you need to install the Deadline 3.0 Repository to a new location. Once you are running Deadline 3.0, you will be able to upgrade to future 3.x releases by following the steps below.
Upgrade the Repository
Download the new installation package from the Frantic Films Software website, then run the repository installer on the computer where the Deadline Repository is installed. Select the directory where the Repository has been previously installed as the Destination Folder.
The Repository installer will automatically back up any files that it overwrites and store them in the Backup folder in the Repository root.
On Windows, at the end of the Repository upgrade, you can optionally run the Repository Configuration Wizard. If you have run the Repository Configuration Wizard previously, you do not have to run it now. You can modify the Repository Settings later from inside the Deadline Monitor while in Super User mode by selecting Tools -> Configure Repository Options.
Upgrade the Slaves
After the Repository has been upgraded, the Deadline Client can be upgraded on all the slaves on the network. By simply restarting the Deadline Slave application on each slave, Deadline will notice that the Repository has been upgraded and will automatically upgrade Deadline Client.
On Windows, select the slaves you want to upgrade in either Deadline Monitor (in Super User mode) or Deadline Configuration, then right click over the highlighted computers and select Remote Control -> Restart Slaves.
After restarting the slaves, several slaves may appear offline or a message may pop up saying the certain slaves did not respond. This may occur because all the slaves are trying to upgrade at once. Wait a little bit and click on the Refresh button to make sure that all the slaves have restarted properly.