Agent Installation FAQ

Product Availability and Compatibility

Agent System Requirements for Linux

Configuring a User Account on UNIX

The Agent name field can only contain the letters and digits A–Z, a–z, and 0–9, and the special characters - _ :.

Verifying Operating System Levels and Patches

Yes you can. However, you need to verify that the Linux OS system commands return English messages. For more information, see Configuring Western European Language Support on Linux.

The <user_shell> account must be defined as one of the following:

• /bin/csh
• /bin/tcsh
• /bin/sh
• /bin/ksh
• /bin/bash

Yes, with the following requirements:

• Each Agent is installed under a different user account.

• Each Agent has a unique name.

No, the Agent name is unique for the entire tenant A Helix Control-M environment that is segregated, secured, and located on a cloud infrastructure..

Configuring the Automatic Startup/Shutdown Procedure for Agent on Solaris

Yes. See Agent Post-installation Procedures.

Yes. You can switch to root user before you install the Agent by using the su command. After the installation completes, the Agent starts up in root mode which enables the Agent to execute all submitted jobs without the Run as User An OS account name that is used to execute jobs on the host. password. You do not need to run the set_Agent_mode utility. The Agent processes run under the user root.

To switch to non-root mode or Sudo mode, use the set_agent_mode utility.

The Agent communicates with the Server using https protocol (port 443). If your organization blocks access to the Internet, contact your Network administrator to grant outgoing access to the following:

• *.controlm.com:443 (https protocol) (outgoing only)

• *.amazonaws.com:443 (outgoing only)

The Agent works in one of the following modes:

• Root Mode: Enables the Agent to execute all submitted jobs without the need for the Run as User password.
• Non-Root Mode: Enables the Agent processes to run with the Agent account permissions. To run a job with a different Run as User, you need to define the Run as User authentication settings, as described in Adding a Run as User.

• Sudo Mode: Enables the Agent processes to run with the Agent account permissions. To run a job with a different Run as User, you need to define the Run as User in the operation system sudoers file. See Agent modes for more information.

  BMC recommends using non-root mode.

To set the Agent mode, you need to log in as root and run the set_agent_mode script, as described in Running the set_agent_mode Utility.

Product Availability and Compatibility

Agent System Requirements for Windows

Yes, but each Agent must have a unique name.

The Agent name field can only contain the letters and digits A–Z, a–z, and 0–9, and the special characters - _ :.

The Agent service starts up automatically.

Yes. See Agent Post-installation Procedures.

The Agent communicates with the Server using https protocol (port 443). If your organization blocks access to the Internet, contact your Network administrator to grant outgoing access to the following:

• *.controlm.com:443 (HTTPS protocol) (outgoing only)

• *.amazonaws.com:443 (outgoing only)

By default, jobs are executed using the Agent service privileges. If you want jobs to execute with the Run as User, you need to set the LOGON_AS_USER Agent system parameter to Y, and your Administrator needs to add the relevant users, as described in Adding a Run as User.

By default, the Windows Agent creates the Agent service using the Local system account. You can change the Agent service account after the installation to a different account, as described in Agent Post-installation Procedures.