2 issues:
You cant start new slave instances when having multiple machines selected (means a grinding 20 minute job to start them all, instead of a group select, go 
)
the result is not logged into a console, so i dont know if it worked or not (if the launcher is dead for example)
re: - the result is not logged into a console, so i dont know if it worked or not (if the launcher is dead for example) disregard this. Its logged properly to the remote commands panel.
The other issue still stands
That’s a holdover from v5 where you had to give the full name of the secondary slave, which you didn’t want to do on multiple slaves.
In v6, since you just specify a post fix (which is appended to the actual machine name), there is no longer an issue with starting instances on multiple machines at once. We’ll remove this limitation in beta 8, and change the dialog text a bit to make it clear you’re specifying a post fix. We’ll also add a confirmation message as well.
GLory, thanks! (i just added 150 secondaries, half had missing launcher, oh the joy lol)