While the launcher is still handling one remote command, it cant accept new ones.
The problem with this is that if its not actually handling a remote command (but waiting for a process to quit that never will), we stop being able to send remote commands to our machines till be either reboot them, or restart the launcher manually.
Thanks! We’ve logged this as a bug.
Sadly the machines cant even accept “restart after current task completion” when in this state, so we will have a couple of angry wranglers on our hands when they have to manually restart 1800 machines now 
Actually, a maintenance job should work… we will try that
For Windows machines you can do most common operations (reboot, kill processes, etc.) remotely with PowerShell (example). And of course for Linux machines you can remotely execute any command with SSH (example). But I also like your idea of using a maintenance job.
We have admin shares turned off currently, so the remote tools don’t work. In any case, this is a deadline bug that’s made worse by our circumstance.
In that case, I can certainly empathize with your situation. I can’t imagine being responsible for 1800 machines without remote admin control.
Thankfully, we have deadline, right?!
It’s an interesting point. We are seeing Deadline increasingly used as a Config Management tool either directly or in conjunction with tools like Puppet.