How is a "least busy" remote agent determined? I want to have the submission of a job bounce to whichever machine is not currently running a job but the master scheduler only wants to send it to the first machine in the host list. If that agent is running a job, shouldn't the next machine run the next one?

Thanks

The master finds the least busy machine by checking number of running jobs.
The first machine with the minimum jobs is used to run the job. In your scenario, if agent A is running 1 job and agent B is not running any jobs then the agent B is used. However, if agent B is not REACHABLE or it is running same number or more jobs than agent A, the agent A is used again.

: How is a "least busy" remote agent determined? I want to have the
: submission of a job bounce to whichever machine is not currently running a
: job but the master scheduler only wants to send it to the first machine in
: the host list. If that agent is running a job, shouldn't the next machine
: run the next one?

: Thanks

That's how I would expect it to run but it always submits jobs to the same remote agent even though it is currently running a job. The others wait in line for that resource. I test the connection to both agents and get successfull responses. I do want the jobs to run synchronously, 1 at a time on two different machines.

: The master finds the least busy machine by checking number of running jobs.
: The first machine with the minimum jobs is used to run the job. In your
: scenario, if agent A is running 1 job and agent B is not running any jobs
: then the agent B is used. However, if agent B is not REACHABLE or it is
: running same number or more jobs than agent A, the agent A is used again.

Are you running the same 24x7 version on all machines?
How log does it usually take for a sucessfull connection?
Do you have agent's security enabled?

: That's how I would expect it to run but it always submits jobs to the same
: remote agent even though it is currently running a job. The others wait in
: line for that resource. I test the connection to both agents and get
: successfull responses. I do want the jobs to run synchronously, 1 at a
: time on two different machines.

: Are you running the same 24x7 version on all machines?

Yes, it is a recently downloaded eval copy to see what 24x7 can do.

: How log does it usually take for a sucessfull connection?

Very quick response

: Do you have agent's security enabled?

No

One more question, are you sure the first agent is executing anything at that moment?
If you are running for instance a job that starts Windows Notepad asynchronously, the agent simply starts the program it and let it go considering the job done. If you are doing something like this you should change your test scenario. Here are two options? Submit some long running synchronous job to the first agent from another computer and while it is running try your job with the [Least busy] option. Another way is two use 2 job queues - the first queue to run the first job "synchronously" (for testing, of course) and then while it is running, run the second job using another job queue so both of them can run simultaneously.

: Yes, it is a recently downloaded eval copy to see what 24x7 can do.

: Very quick response

: No