I can’t seem to install the Deadline 5 Launcher service. I can’t uninstall the 4 launcher service and I think it’s blocking the 5 launcher installer on the slaves. Ideas?
sc delete “Deadline Launcher Service”
“\path to installer\deadline” /mode silent …
In a bat file took care of it.
Next Problem:
First run of the deadlinelauncherservice doesn’t launch the slave. Since it doesn’t launch a slave (even if launch slave on startup = true) it won’t show up in the monitor for new installations.
Workaround:
SC stop “Deadline Launcher Service”
SC start “Deadline Launcher Service”
When a slave is first detected by the monitor it says it’s connected to pulse even if it isn’t. (Refresh of slave monitor updates correctly)
Thanks for reporting the launcher service problems. I should have time to look into them tomorrow.
I’ve already tracked down the “Connect To Pulse” problem. Thanks for reporting that too!
Cheers,
- Ryan
I was able to reproduce this, and we’ve implemented a fix that will be included in RC3.
This may have been a bug in the version 4 uninstaller. Testing with the Deadline 5 uninstaller seemed to uninstall the launcher service properly. Unfortunately, we can’t do anything about the v4 uninstaller, but at least this issue should be fixed going forward.
Cheers,
- Ryan
Maybe include an uninstall tool with V5 for v4? I imagine there are going to be quite a few others running into the same problem. Run a check for V4 and prompt to see if you want to replace the old service.
It’s unlikely we’ll have time to create this prior to the 5.0 release. 
I ran a couple of tests this morning, and here are the results:
- Install Deadline 4.1 as service and then uninstall:
This worked fine! I did have to run the uninstaller as administrator because it doesn’t automatically request elevation (just like the 4.1 installer).
Just an FYI that the elevation problem has already been fixed in the 5.0 installer.
- Install Deadline 4.1 as a service, and then install Deadline 5.0 as a service:
This worked fine too! The 4.1 service was replaced with the 5.0 service with no problems. That’s not entirely unexpected, since the service itself hasn’t really changed between these versions.
Have you had this problem on all of your client machines, or just one? I have seen instances where services become marked for deletion, but aren’t deleted right away, and often the only way to have the service go away is to reboot. This is a general service thing, and isn’t specific to the Deadline service. If the 4.1 service was marked for deletion, that could explain why you had problems in this case.
Cheers,
- Ryan
I tried on 3 machines but I don’t think I explicitly right clicked and ran the installer as an administrator. After those 4 I just ran my .bat file and none of those got hung up.
I bet that’s it. At least we fixed the whole “administrator” issue in the v5 installer.