AWS Thinkbox Discussion Forums

AutoStart DL Launcher issue?

Somehow I have some issues to get the launcher to start automatically without using it as a service.

I simply make a shortcut and place it in the Startup folder on win7 pro (64bits) but the application doesn’t start up at all…
If I check it in the msconfig it’s listed, if I click it manually from the startup folder it works, but just not after a reboot.

Somehow I have this with 8 out of 10 machines.
Coincidently those 8 machines also had 2 instances of DL6 installed
One in the default installation folder, the other in my preferred custom folder (c:\software instead of program files)
I suspect the double copy came there due to having the auto-update on with the slaves… but that’s only a guess at this point as both copies have been removed.

I tried installing DL7 on the default location and on the preferred location, but in both cases it doesn’t want to auto-run the launcher.

anything else i can do/check?

-----update

just tried it as scheduled task and got a 0x800704DD back as error code.
Which would indicated it doesn’t have administration rights.

the only way I can get it starting if I launch deadline ~15 seconds after startup…

no idea how this came to happen… but now it works…

ok, today it at the first boot of the machines non of the deadline launcher loaded.

second boot they did.

how can i make this more reliable?

Is it possible to set it as service after it’s already installed?

You can set up the Launcher to run as a service after it has already been installed:
thinkboxsoftware.com/deadlin … er_Service

However, it might just be quicker/easier to run the client installer again and choose the option to install it as a service. You don’t have to uninstall the Client first to do this.

Cheers,
Ryan

okay… with the 0.26 beta i’ve removed all previous DL installs from the custom location (c:\software\thinkbox\deadline 7) and did a silent installation on it’s default location (C:\Program Files\Thinkbox\Deadline7)

now all works properly.

somehow i did have to kill the firewall to let the monitor communicate remotely with the slave’s launchers, but that’s no problem

Privacy | Site terms | Cookie preferences