## Overview¶

WARNING - Check whether your license file needs to be updated BEFORE installing the new version of Deadline, as there may be a delay before you receive your new license file from Thinkbox Sales. Our release notes and forum build announcements always contain the license information, confirming what FEATURE version of Deadline, Draft and Balancer you require to run this specific version. Plan ahead!

If upgrading to a new major version (for example, Deadline 8 to 9), or downgrading from a new major version (for example, Deadline 9 to 8), you will need to install a NEW Repository and Database, and you will need to reinstall the Client software. This is necessary because there are often breaking changes between MAJOR releases. MINOR releases (including beta releases) such as Deadline 8.0.15 or 8.0.16 can happily be installed over the top of an existing Deadline 8.0 installation, but NOT Deadline 9.0.

Please note we do NOT officially support the archiving/importing workflow to transfer Deadline jobs from one MAJOR version to another. The reason for this is that MAJOR versions of Deadline allow us to carry out ‘breaking’ changes to our DB backend, so the dev team make no promises that the Deadline “job object” may or may not get touched. So, the official recommendation is always to let all jobs finish up rendering in one MAJOR version before moving over to the next. MINOR versions of Deadline are typically supported.

You should also reinstall your integrated submission scripts on your workstations, since it’s possible these were changed between major releases. If upgrading to Deadline 8 or later, it is absolutely necessary to reinstall these scripts. See the Application Plug-ins documentation for more information on how to set up the integrated submission scripts (where applicable).

The license server should also be upgraded to ensure it will work with newer releases in case there are incompatibilities with the previous version of the license server.

You can also enable Remote Administration in the Client Setup section of the Repository Configuration. This will make it easier to upgrade or downgrade your render nodes remotely.

To ensure Deadline’s Automatic Upgrade/Downgrade system works correctly; make sure the service account used to run Deadline Launcher has the ability to start and stop the service. This permission on Windows for example can be added to the service account by an Administrator user as follows:

setacl.exe \\computername\deadline9launcherservice /service /grant <serviceaccount> /start_stop


Launch the new Repository installer, and choose the existing Repository folder for the Installation Directory. Then choose the option to connect to an existing MongoDB database, and use the same Database Settings you used when installing the previous version (they should be pre-populated for you).

During the installation, all binaries, plug-ins, and scripts from the previous version will be backed up. You can find them in the backup folder in the Repository after the installation is complete. Note that any scripts or plugins in the ‘custom’ folder will not be affected when upgrading the Repository.

• Proxy Server
• Pulse
• Balancer
• Forwarder
• Web Service

If you don’t have Automatic Upgrades / Downgrades enabled, you will have to upgrade or downgrade these applications manually, which involves running the Client Installer on the appropriate machines. See the Client Installation Guide for more information.

If you have Automatic Upgrades / Downgrades enabled, all you have to do is restart the applications from the Monitor, providing that Remote Administration is enabled. The Client will notice that the Repository has been upgraded or downgraded, and will automatically upgrade or downgrade itself.

This process is actually identical for Pulse, Balancer, Proxy Server, and Forwarder, so let’s use the Pulse panel as an example. Right-click on the Pulse instance in the list and select Remote Control Pulse -> Pulse Commands -> Restart Pulse. Note that if you don’t see the Remote Control menu, you will have to enter Super User Mode from the Tools menu. This sends a remote command to the Launcher running on the remote machine to restart Pulse, which will trigger the upgrade. After Pulse has been restarted, you can check the Version column in the Pulse panel to confirm that it’s now running the new version.

You can repeat this process for the Balancer, Proxy Server, and Forwarder as necessary. For the Web Service though, you’ll notice that there isn’t a panel in the Monitor for it. Currently, the only way to update the Web Service is to run the Client Installer on the machine that it’s running on.

If you don’t have Automatic Upgrades / Downgrades enabled, you will have to upgrade or downgrade the Clients manually, which involves running the Client Installers on the machines. See the Client Installation Guide for more information.

If you have Automatic Upgrades / Downgrades enabled, all you have to do is restart the Slave application on each render node through the Launcher. The Client will notice that the Repository has been upgraded or downgraded, and will automatically upgrade or downgrade itself. In addition, the next time artists launch the Monitor on their workstations through the Launcher, their installation will also be upgraded or downgraded.

To restart the Slaves remotely, Remote Administration must be enabled. Select the Slaves you want to upgrade or downgrade in the Monitor while in Super User mode, then right click and select Remote Control -> Restart Slaves. If the slaves are currently rendering and you don’t want to disrupt them, you can choose the option to Restart Slaves After Current Task instead. This option will allow the Slaves to upgrade or downgrade after they finish rendering their current task to prevent the loss of any render time. See the Remote Control documentation for more information.

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 or downgrade at once. Wait a little bit and eventually all the Slaves should come back online. After the Slaves have been restarted, you can check the Version column in the Slave panel to confirm that they’re all now running the new version.

2. Note the location where you installed the Repository. This will be referred to as [REPOSITORY] for the remaining steps.
3. After the Repository installation has finished, navigate to [REPOSITORY]/backup/mostRecent. This folder contains everything that was backed up from the previous installation.
4. Copy the contents of [REPOSITORY]/backup/mostRecent/draft to [REPOSITORY]/draft, and overwrite the existing files. This will update the Draft libraries that are used.
5. Copy the contents of [REPOSITORY]/backup/mostRecent/submission/Draft to [REPOSITORY]/submission/Draft, and overwrite the existing files. This will update the Quick Draft options so that they match the version of Draft you’re using.