If you are struggling with the setup of a new MID Server in that all integrations work fine except for orchestration workflow when pointing to a Power-shell activity then this may be a credential issue, configuration of the clients environment or even a ServiceNow issue.
Steps to reproduce:
1. Open Workflow Editor
2. Open workflow
3. Open the first "Run Powershell" activitity in workflow.
4. Configure "Hostname" to new MID-server.
5. Impersonate User
6. Go to service portal
7. Open item
8. Use default values and submit request.
9. Check in RITM that the orchestrations workflow fails.
Check if there are any credentials set up for the MID Server, otherwise, the MID Server is totally dependant on the Service credential on the MID Server service (right-click the service and select the Log On tab); you can also assign a tag to the Windows credential.
If you suspect this is more to do with the configuration of environment, when testing your scripts, you can run the same script from within Power-shell
- if it works in Power-shell and your workflow fails, then this will be a ServiceNow issue and you should log a call with Support
- if it fails in Power-shell then this is an environment issue