Running Interactive jobs on Windows using WA Agent

Products

• CA Workload Automation AE - Business Agents (AutoSys)
• CA Workload Automation AE - Scheduler (AutoSys)
• Workload Automation Agent
• CA Workload Automation DE - System Agent (dSeries)
• CA Workload Automation AE - System Agent (AutoSys)
• CA Workload Automation DE - Business Agents (dSeries)

Issue/Introduction

The WA Agent can run jobs in interactive mode on Windows OS.  Interactive mode lets users view and interact with jobs that invoke Windows Terminal Services or user interface processes, for example, Notepad.

 

Environment

Release: ATSYHA99000-11.3.6-Workload Automation AE-High Availability Option
Component:

OS: Windows OS

Resolution

Following parameter must be added to agentparm.txt

oscomponent.interactive=true 

The user specified in the job must be logged in to the host where WA Agent is running.

If the user is not logged in, the job will fail with this error

EXITCODE: 20013 TEXT: <Unable to locate interactive logon session>

Some jobs may still not run, such as MS Excel.  The user Desktop path and the <drive:>/Program Files/System32 must be add to the PATH environment variable.

E.g.

echo %PATH%

c:\Program Files (x86)\CA\SC\CAWIN\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;
C:\Windows\System32\WindowsPowerShell\v1.0\;;C:\Users\Administrator\AppData\Local\Microsoft\WindowsApps;
C:\Windows\System32\config\systemprofile\Desktop

Note: The "C:\Windows\SysWOW64\" may also be added to the path.  Several MS Office binaries are 32 bit and will use DLLs from <drive>:\Windows\System32.

 

 

 

Additional Information

Note:  User may need/create to add this directory if it doesn't exist

C:\Windows\SysWOW64\config\systemprofile\Desktop

 

Please note that Microsoft has fully disabled Interactive Service Detection starting with Windows 10 Build 1803 and Windows Server 2016 and 2019. Starting with these versions, access to Session 0 is no longer possible.

https://docs.microsoft.com/en-us/answers/questions/27517/is-there-any-workaround-in-win10-to-allow-service.html