24 X 7 Job Scheduling

Hallo ,
I'm a Newbee in Scheduling Jobs with 24X7.Our Idea was to install 24X7 on 2 Servers (master/Slave).The Master Server should be the central Point for scheduling in our Server Farm.
On the other servers i want to install 24X7 as Remote Agents.Now I have a some Questions :
How can I schedule the Jobs on those servers,which are installed with Remote Agents ? Is there a need to map the several drives of the servers ?
Or must i copy the Batch Files to the Master server and execute them via Remote Agent ?

Thanks for Info and Help.

On the master scheduler system you need to define remote agent profiles, basically a named set of connection settings. For each remote job, in the job properties use the Host drop-down list to choose one of the agent profiles. When the job is run, the master scheduler automatically pulls connection settings associated with the profile, connects to the agent and tells it what to do, in other words, submits the job for remote execution. There is no need to map any drive or change anything on the system level on the master and agent computers.

Of course, if a job is designed to run external files, you would need to have these files available on the system where you run them. In the job properties refer to these files as if they were local files to the agent. If you use script jobs instead of batch files, you don't need to worry about that, scripts are deployed automatically in job run time as internal job properties, no external files are involved unless they are referenced explicitly.

I start a Job from Server A (Master Scheduler) and want the Job to run on Server B (Remote Agent).That works fine.
But when i want to start a job on server B with the Filewatch Options (Move and rename File in another directory),it doesn't work.
I want the trigger to watch files on server B (Remote Agent).
The Job starts,but the file is not moved.
Whats wrong ?

Remote agents are used to run jobs remotely, basically to have jobs physically start and run on the remote machine. That's all.

File watching and checking other job related events and conditions is associated with the scheduler, not a remote agent. If you need to check files on the remote server, either make the scheduler to go and check them on that server using UNC files names and network shares, or run 24x7 on that remote server as a scheduler, not as an agent, and make a local file watch job to check files local to that server

It is also possible to convert the job schedule to a different type, and for example, make it run every 10 - 15 minutes on the remote agent and have that time-based job, not the scheduler, to check for files. If required files are present, make the job to do the next business step. There are tons of methods in 24x7 available for implementing this kind of processing.

Hope this helps.