This is the scenario:

Environment: Machine1 with Test Studio and Machine2 with scheduling server.

Behavior: The user on the TS Machine1 decides to use the scheduling server to schedule tests during the night, for example.

He connects the project to the scheduling server - everything is O.K. with the connection, but when he tries to schedule a run, Machine1 is not available in the list of machines.

This is because when you connect to a scheduling server, Test Studio does not connect the local Runner to that server automatically. This behavior covers the cases when the user is using his machine only for tests development. But when the user wants to use the machine for execution as well, it is missing from the list. He should go to the Runner and connect it manually to the scheduling server, which is not intuitive and I doubt that most of the customers know that.

My proposition is to have one dialog, that appears after connecting to the scheduling server. That dialog asks the user if he wants to register this very machine also as an execution client for the same scheduling server. This should clear the confusion.