- When submitting a job to a Control-M/Agent on a Microsoft Windows platform, the job fails with the following message in the Control-M Job Log:
  TR5167 The agent works in 'Logon As User' mode but the password for job owner '<user>' is not defined.

 

- The Microsoft Windows Control-M/Agent has a configuration parameter called Logon as User:
   When this parameter is set to N, jobs are submitted as the user account with which the Control-M/Agent Service is running, regardless of the Job Owner defined in the Job Editing Form.  
   When this parameter is set to Y,  the Control-M/Agent will attempt to log on as this job owner to load his profile, then execute the job script or command line. 

- To authenticate the user in Microsoft Windows, the Control-M/Agent must send a password in the login command which the Control-M/Server maintains the encrypted passwords for these users in the database.  These passwords are registered using the 'Run as' Users Authentication Settings in Control-M Configuration Manager (CCM).

The following video demonstrates this article:

Here are the steps to add/edit the password for the job owner user:

1. Run Control-M Configuration Manager(CCM) and click on Tools menu->Security->'Run as' Users Authentication Settings
2. At the 'Run as' Users Authentication Settings windows, click on + sign to add a new 'Run as' user(ie, job owner user)
3. Make sure to specify the agent machine name in the Host field(or leave the value as ALL if the user could be used for all agents, then specify the user's password or key to authenticate into agent machine(s).
4. Click on the Test button to check if the user can authenticate to the agent machine (ie if the user account is just for a single agent machine)
5. Click OK to save the new user definition into the Control-M Server database.

NOTE:
ctmsetown command at the Control-M Server functions like the above steps. Please refer to the Utilities Guide for more info on the ctmsetown command.

Additional note: 
The 'Run As' username in the job definition should match case sensitivity with the username stored in the Authentication Settings.