CONTROL-M/Agents and remote hosts

In earlier releases of CONTROL-M/Server, each computer on which you planned to
run jobs required installation of a CONTROL-M/Agent. Beginning with version
6.3.01, CONTROL-M/Server supports agentless job submission. This method enables
submitting and executing jobs on computers that do not have a resident

CONTROL-M/Agent installed. These agentless computers are referred to as remote
hosts.
Although remote host computers do not require a resident CONTROL-M/Agent,
remote hosts come under the control of CONTROL-M/Agents on other computers, as
follows:

■ When you install CONTROL-M/Server in UNIX, a CONTROL-M/Agent is
   automatically installed on the same account. When you install
  CONTROL-M/Server in Windows, a CONTROL-M/Agent is automatically
 installed on the same computer, unless one already exists or you are performing a
cluster install. This automatically installed CONTROL-M/Agent is known as the
<Local> agent and is, by default, the agent that is used to connect to remote hosts.

■ You can place remote hosts under the control of any other CONTROL-M/Agents
   installed on computers under the same CONTROL-M/Server.
You will need to define the following information for each remote host:

■ host communication settings
You can define specific settings for a host, or use the default settings. For more
information, see “Configuring and managing remote hosts”

■ owner authentication settings
These settings specify the owners of the jobs that are running on the remote host,
and owner authentication parameters that are used for connecting to the remote
host. In a CONTROL-M job that is destined to be run on a remote host, you must
define each job owner that is specified.