Creating and Configuring a Privileged Identity for Batch Jobs

This topic describes how to perform configuration to ensure that Windows batch jobs run properly. The configuration is necessary because some Windows password policies might cause users' jobs to fail if a password has expired or has been changed.

The configuration described here creates a privileged Lawson identity that is mapped to a Windows administrative user.

After configuration, 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.

With this setup, passwords for normal batch users do not expire. System administrators need to follow password policies for the operating system user that is linked to the privileged identity.