Upgrading deadline client wierd bug?

Deadline
1

Hi,
We have deadline clients running on windows 10 and we are upgrading from deadline 10.0 to 10.2 as well as upgrading the repo path, etc. So our plan is to uninstall deadline client from the workers completely and then install with the new settings.
We have a Batch script that we use to uninstall the old client and it looks like this:

sc.exe delete deadline10launcherservice
taskkill /f /im deadline*

“C:\Program Files\Thinkbox\Deadline10\uninstall.exe” --mode unattended

RD /S /Q C:\ProgramData\Thinkbox

RD /S /Q %LOCALAPPDATA%\Thinkbox
RD /S /Q %APPDATA%\Thinkbox

cd C:\Users
for /r /d %%a in (*) do if exist “%%a\Thinkbox” rd %%a\Thinkbox /s /q

which basically stops the deadline launcher, and processes. uninstall deadline and then deletes all the appdata and programdata foldeers for thinkbox.

After all that, we install the new one like this:
“\network-share-mount\Deadline-10\DeadlineClient-10.2.1.1-windows-installer.exe” --mode unattended --repositorydir “\network-share-mount\deadline\10.2\repository” --serviceuser “render” --servicepassword “password” --launcherservice “true”

When we do this, the new deadline is installed but the default repo is still pointing to the old repository. Even when we edit the deadline.ini in programdata with the new repository path, it still points to the old one. Why is it doing this ?
How do we go about doing this properly?
Thanks

2

Hello,

Did you check to see if Auto Configuration had been set previously and is still overriding the client cfgs with old repo path?

3

Hello @Stan

Thanks for reaching out, as jarak mentioned please check if you have any repository path set in Auto Configuration path that is overriding the client configuration. As a part of your batch script you are deleting user-level deadline.ini file available at %LOCALAPPDATA% path, can you please check and ensure no flags related to repository path are set in user-level deadline.ini file as it overrides system level client configuration file.

Also, are you making changes to deadline.ini file on correct client machines ?

Try connecting to new repository using ChangeRepository deadlinecommand which also can be added to your batch script if it works, in order to make it effective for all the clients.

Please try and update on how it goes!

Thanks.

4

thanks for the help but only the new repo is set in the Auto Config.

also my workaround or fix for this was to use a redhat 8.6 server instead of a windows one. somehow the clients behaved fine with the redhat server instead of windows

1 Like