After setting up your scheduling server, even though things appear to be normal, it still may not work right due to network connectivity issues. For example, an Execution Server may be able to talk to the Scheduling server, but not the Test Studio IDE or vice versa. The Execution Server will show up as available when you go to schedule a test list, but when you try to schedule a test list, the IDE says it was successfully scheduled, then absolutely nothing happens. If you try to enable logging on the Execution Server, you might get an error in the IDE, but the error only says it failed to enable logging. There's no explanation why it couldn't leaving the user thoroughly confused how to fix this.
To over come this there needs to be a method that customers can use to verify connectivity between all the scheduling server components is fully working properly in both directions. Test Studio relies heavily on bidirectional communication between all components. When one direction is blocked and not the appear it appears to be fine at first until you actually try to schedule something.