Privileged Identity for Batch Jobs (Windows only)

Prior to Infor Lawson System Foundation release 9.0.0.4, password expiration policies could cause Lawson batch jobs to fail. With release 9.0.0.4, new functionality caused this problem to become obsolete.

Your installer or system administrator performed the configuration to create a privileged user for batch jobs. The configuration performed was:

• Created a unique user on the Windows operating system

• Created a privileged identity on the Lawson system that was linked to the Windows user

• Configured a parameter, RUNUSERKEY, in the configuration file of Lawson Job Scheduler (lajs.cfg)

As a result, when a normal batch job user runs a job, ownership of the job is temporarily assigned to the privileged user for execution. Immediately upon execution, ownership of the job returns to the normal batch user so that the user can create print files and so that distribution groups execute as intended.

Lawson does not check passwords for normal batch users during execution so a password expiration or change for a normal user does not cause a job to fail.

Lawson does check the password of the privileged identity. Security administrators must follow Windows policies for this password.

For more information about the configuration that was performed to create the privileged identity, refer to the instructions in either the Lawson Core Technology Installation Guide (for customers installing 9.0.0.4 for the first time) or in the 9.0.0.4 Installation Guide Addendum (for customers installing 9.0.0.4 as an update to an earlier service pack).