Remote Control PC Tied up while job runs

On the Remote Control PC when you manually run a job it ties up the PC until the job is done running, even though you are executing the job on the server.

Why is that? Doesn't make sense if the job is executing remotely. What is it waiting for and how do I change it so it becomes immediately available when a job is manually run remotely?

It depends on the job executuon mode. Which option do you choose in the Remote Control when you are prompted for how to run the job?

As stated I select Remote to execute the job remotely.

Please set the job to run asynchronous.

No, that doesn't work.

Even with that set when I execute a job from the remote control PC using the "remote" to run it on the server the 24x7 Remote Control interface stops responding until the job is done executing.

Detached doesn't work either.

Got it. End user didn't uncheck the box after clicking "Run Now" that overrides the Asynchronous setting so it was waiting for it to end.

All set.