Creating an Interactive job to run in session '0'

Document ID : KB000029113
Last Modified Date : 14/02/2018
Show Technical Document Details

You can configure the agent that is installed on a Windows computer to submit jobs in interactive mode instead of in batch mode. Interactive mode lets users view and interact with jobs that invoke Windows Terminal Services or user interface processes, for example, Notepad.

We need to add this parameter to agentparm.txt to setup an interactive job.

oscomponent.interactive=true 

This tries to detect the user logged in session ID and runs the job in the user logged in session. This brings in two condition for the job to run.

1. The user that is specified to run the job must be logged in to the agent computer

2. Also, the user must be logged in to the agent computer exactly once.

If these conditions are not met then the job will fail with the error message as "EXITCODE: 20013 TEXT: <Unable to locate interactive logon session>".

Now if you have condition that the jobs should run irrespective of the user has logged in or not then we need to add the following parameter to the agentparm.txt.

oscomponent.interactive.sessionzero=true

This runs all the interactive jobs in session '0'.

When you log on to your Windows  2008 or later you now no longer login to Session 0 but into Session 1 or greater. This is called as session '0' isolation.

So in order to access the job running in session '0' you need to have the Interactive Services Detection Service running.

It will give a pop up window as follows

 

isd1.jpg

 

Select View the message and it will switch to session '0'.

 

isd2.jpg

 

Once you are done with your input in session '0', Click on return now to switch back to your logged in session.