WI to open a .exe

To simply have Active Roles just run an EXE file, I would think this could be done via an Automation Workflow that calls the EXE from a PowerShell script. Delegate access for the Service Desk members to an Automation Workflow. Then from the WI they could browse to Directory Management -> Workflows and launch the workflow When executed, this workflow would start a PowerShell Script Module that kicks off the EXE file.

To simply have Active Roles just run an EXE file, I would think this could be done via an Automation Workflow that calls the EXE from a PowerShell script. Delegate access for the Service Desk members to an Automation Workflow. Then from the WI they could browse to Directory Management -> Workflows and launch the workflow When executed, this workflow would start a PowerShell Script Module that kicks off the EXE file.

Thanks mate. I was having a look at a script and then having a work flow kick off. I have since trashed the script but i was trying onInit and then a simple path to the .exe but nothing actually launched. 

I don't know that I would put my code in an OnInit since (as you may know) it is typically used for "staging" the runtime environment (by pre-loading parameters and library scripts for example).

Just put it in a simple function like "RunMyComandLine" and then permission for launch as Rich suggested.

Thanks. 

So  i have the code below. I have created a work flow but when i run the work flow i dont see the application open. The .exe is on the local server that its being run on. 

function ADAccountLock
{

Start-Process -filepath C:\AccountLockOut\ADLockouts.exe
}

And you won't...

At best, the application will be launched on the AR server that the user is connected to.

The user will not be able to interact with it.

So you will need to find a way to send any required parameters to the application (this can be done via workflow parameters) and to deal with its output (probably in the format of output re-directed to a file share on the AR server?)

 (this can be done via workflow parameters)

...which can be setup in such a way that they will prompt the user for input.

Thanks. Yeah they need to launch this and use the GUI of the application. Seems i am going to need to think of another way. was hoping to just keep them in ARS to launch stuff