Control-M/Agent post installation procedures

The following procedures describe the required and optional steps after you install Control-M/Agent on UNIX:

• Enabling Control-M/Agent for non-root mode
• Configuring the automatic startup procedure for Control-M/Agent on UNIX (optional)

  NOTE: If you installed Control-M/Agent on NFS, you can only use the Control-M/Agent user on the same host where Control-M/Agent was installed and you cannot install an Application Plug-in on a Control-M/Agent on NFS or VXFS. If you installed on AIX, you must update the OS path level, as described in 000111319.

  NOTE: To avoid performance issues, BMC recommends consulting with your IT/Security personnel and work with them to exclude the following from anti-virus scanning:

• All the files and sub-directories under the Control-M/Agent installation directory.
• All Control-M/Agent processes (for example p_ctmam) and binary programs.
• All communication ports used by Control-M/Agent processes and binary programs.

NOTE: (Windows only)

• If you want a different user to start up the Control-M/Agent Windows service, you must define that user as a member of the Local Administrative Group (<Domain>\<User>).
• The administrator selected as part of This Account, must have the Adjust memory quotas for a process, Replace a process level token, Act as Part of Operating System, Log on as a Batch Job, and Log on as a service permissions in the Local Security Settings window (see 000024690).
• If you changed the Control-M/Agent Windows service Log on as option to Local System account or This account, or modified its properties, you must terminate all Control-M/Agent processes before new jobs can run with the new Log On details.
• When the Control-M/Agent service is defined as This Account, the user that the Control-M/Agent is running with must have List Folder Contents permissions for the Control-M/Agent drive.