Launcher FAQ

• 1 Launcher FAQ
  • 1.1 Why should the Launcher application be left running on the client machines?
  • 1.2 I don't want the Launcher to always be running, so how do I prevent it from loading during startup?

Why should the Launcher application be left running on the client machines?

Its main purpose is to provide a means of remote communication between the Slave and the Monitor / Configuration applications. If it's not running, the Slave wil have to be stopped and started manually.

In addition, whenever you launch the Monitor or Slave using the Deadline Launcher, it will check the Deadline Repository for updates and upgrade itself automatically if necessary before starting the selected application. If the Launcher is not running, updates will not be detected.

I don't want the Launcher to always be running, so how do I prevent it from loading during startup?

On Windows, you can remove this registry entry to stop the Launcher from loading at startup:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\DeadlineLauncher

Note though that the Launcher ensures this registry entry is set whenever it starts up, so if you start the Launcher again, you'll have to remove this key again.

On Linux, just configure your startup file to not start the Launcher.