AWS Thinkbox Discussion Forums

auto start launcher on slave startup

Does this require any manual setup on our part? We are finding that the launcher does not get started automatically on machine restart, at least in some cases

cheers,
laszlo

The client installer should be handling this automatically. You can check if it is properly set up in the registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

There should be a DeadlineLauncher entry here with the full path to the launcher executable.

Note that this is only if you are NOT installing the launcher as a service (which is off by default in the client installer). If you are installing it as a service, then the Windows service system handles that automatically.

One thing you could check to is if a log gets created by the launcher. Maybe it’s crashing on startup. The logs should be in %ProgramData%\Thinkbox\Deadline6\logs. If the launcher doesn’t start up and there is a log here, please post it and we’ll take a look!

Thanks!

  • Ryan

A lot of slaves were missing the registry entry, but a reinstall of the client fixed it. Thanks!

l

Privacy | Site terms | Cookie preferences