Runtime User - 6.8.0.0

Runtime user ID, including an LDAP- or AD-formatted user ID, under which the job will be run. Maximum length is 100 characters.

If the user does not have a login shell, add a - character in front of the ID. The Controller will provide a shell for that user and strip the - character from the username.

When specifying a Windows account, be aware that the user must have the following privileges based upon the Universal Agent's configuration for the UAG logon option:

logon = Interactive (default)
- Not be in "Deny log on locally."
- Be a member of "Allow log on locally."
logon = Batch
- Not be in "Deny log on as a batch job"
- Be a member of "Allow log on as a batch job"

When specifying a local Windows account that may be used by an Agent running inside a Windows domain environment, be sure to use “.” as a placeholder for the domain name (for example, “.\<localuser>”).

This qualifies the account name and ensures that Windows will authenticate it against the local – and not the active directory – account database. If the “.” placeholder is missing, the account may be interpreted as a domain account in a domain environment, and a task using that credential may fail.

If none of your Agents execute on a Windows domain member or domain controller, the placeholder is optional.

If a domain account must be used, you may specify the account name using the user principal name (UPN) format (that is, “<domainuser>@<domainname>”) or the down-level logon name format (that is, “<domainname>\<domainuser>”).