TerranceBrennan603235

Getting PowerShell to work as an external interpreter

Discussion created by TerranceBrennan603235 on Feb 14, 2017
Latest reply on Feb 15, 2017 by Daniel_Hausdorf_6982

I have found some documents about configuring the UC_EXT_INTERPRETERS_WINDOWS variable in client 0 for PowerShell.

I have configured it this way:

Key: POWERSHELL

Value 1: .ps1

Value 2: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -File <FILE>

This is the correct path to powershell on the Automation Engine server and target servers.  I have tried several variations for Value 2 as well but always get the same error when I try to run a simple get-process command.

 

FAULT_OTHER - Start impossible. Other error.

 

 

U00010009 Runtime error in object 'POWERSHELL.TEST' (RunID '0008234257'): Interpreter definition for interpreter 'POWERSHELL' not found in variable 'UC_EXT_INTERPRETERS_WINDOWS'

The error seems to indicate the external interpreter is not configured correctly; but, I can not figure out where my mistake is.

Outcomes