By default, the agent starts automatic or operator-initiated commands under the user account that the agent itself is currently running under. However, you can configure an HTTPS agent to start commands under a different user account. You do this by setting the OVO_STD_USER parameter in the eaagt name space on the nodes. You can configure this parameter in the following ways:
ovconfchg
or ovconfpar
at a
command prompt.Specify the value of OVO_STD_USER in the format <user>/|<encrypted password>
Replace <user> with the name of the user. For a domain user, specify the domain and user name, for example EXAMPLE\AgentUser. For a local user, specify just the name, for example AgentUser.
opcpwcrpt <password>.
You can
start this command from a command prompt on the
management server.It is also possible to use the OVO_STD_USER when you configure or launch a tool. Specify the user name $OVO_STD_USER and leave the password blank.
You must test whether the user account has appropriate rights to run commands and tools correctly.
Caution:
If the agent fails to start a command or tool as the
OVO_STD_USER, the agent starts the command under the same
user account that the agent is currently running under. This can
happen, for example, if you specify an incorrect user or
password.
Related Topics: