I finally worked out the Powershell command to run an external executable on a remote machine.
- Use the "Invoke-Command" commandlet
- Pass in the remote computer name ($computer)
- Pass in the credentials for the remote computer ($cred)
- Execute you script within -ScriptBlock { }
In the example below, I'm running a batch file on our Good Enterprise Server to add a user
Invoke-Command -ComputerName $computer -credential $cred -ScriptBlock {Set-Location -Path 'C:\Program Files (x86)\Good Technology\Good Mobile Control\jre\bin\'; $Out = cmd /c 2>&1 'GoodLinkAddUser.bat -Url=domain\username:password@https://localhost:19005 -GLS=servername -UserDisplayName="${workflow.scratchpad.uname}" -PolicySet="Policy name" -LogFile=GoodLinkAddUser.log' | Out-String; echo $Out}
Notes when running external executable within Powershell
- Powershell will interpret anything returned by the external executable/batch file as an error, which will cause the Run Powershell activity to always fail although the Scriptblock successfully added a user to Good.
- I worked around this by setting the output to a variable ($out) and then echoing the output at the end of the script.
- I could then do some further evaluation of the output in order to complete the workflow.
Sample from my Run Powershell Sensor Script:
workflow.scratchpad.results = output;
if(workflow.scratchpad.results.toString().toLowerCase().indexOf('successfully created user') > 0){
current.work_notes = 'The requester has been successfully setup for Good Messaging and notified of account setup.';
}
else if (workflow.scratchpad.results.toString().toLowerCase().indexOf('good messaging\nenabled') > 0) {
current.work_notes = 'The requester already Good Messaging enabled. Notifying Service Desk for further investigation';
}
else{
current.work_notes = 'The Good setup script encountered an error. Please investigate further. \n\nError Log: ' + output;
}
