Most of our machines didn’t switch over to the autoconfig new license server info when we switched back to perament today. If I stop the service, remote desktop in, launch the slave on the desktop it all works perfectly. But if I just restart the service nothing happens it goes back to usage based and breaks. .
To confirm, you’re restarting the launcher service from the windows service interface? Or are you restarting the Slave via remote commands?
Really shouldn’t make a difference, should work either way, but just wanted to make sure we’re on the same page 
Also, once you started the slave manually via the desktop, did closing that slave and restarting the service again make it pick up the proper settings then? Or was the service still wrong after that?
After starting stopping from Desktop it would then run properly as a service.
Some of them this morning now say “Invalid License/Expired”. Which is different from yesterday when they were on the usage based so some of them now aren’t picking up the license server or something.
And now some clients simply won’t launch at all. No log, no process. Just nothing from the start menu and a “Failed to start in a timely fashion” from the service.
Strange… was there an auto-upgrade on those machines? I wonder if a failed / partial auto-upgrade could be the cause of that. Is the launcher running as a service, in the scenario that it fails to launch? Or are you getting this for non-service launchers as well? Does running the deadlineslave.exe/deadlinemonitor.exe directly work for you?
As a last ditch effort, if none of the above is helpful, I’d try re-installing the client on the affected machine – especially if there was an error auto-upgrading, might’ve done a weird partial update with incompatible binaries.