1) The user who starts the agent needs to explicitly have the following permissions (Found under "User Rights Assignment" in the "Local Security Settings on Windows):
*Act as part of the operating system
*Replace a process level token
*Logon as a service
*Logon as a batch job
*Restore files and directories
*Adjust memory quotas for a process
PLEASE NOTE: These cannot be implied through the group the user belongs to having the rights, the user itself must have the rights explicitly.
2) Be sure that the logon= setting in the Agent's ini file is set to logon=1
3) Be sure that UAC (User Account Control) is turned off (NOTE: Changing your UAC setting in Windows will require a restart of the Windows Server). From the Automic documentation:
Currently, the Automic Operations Manager does not support UAC. If you intend to open programs which require "Elevation" (a higher authorization) via Automic Jobs, you may do so selecting the option "log on as batch user". The Job is automatically elevated if it requires more authorization. The user specified in the Login object must have the required authorizations. Keep in mind that all processes of the relevant Automic Job are executed with these rights. If the user does not have one or several of the required rights, the Agent cannot execute all processes. Windows aborts with the error 740 (elevation required).
If the above steps were tried and the error still persists, please contact Support and send the following:
*) A screenshot of the User Rights Assignments for the user starting the Agent (show each Windows OS Rights above)
*) The Agent log from startup and with the error reproduced
*) A screenshot showing that UAC is turned off