Should 'Command' topic probes be used to run Powershell scripts on MID Servers?<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Quick answer: No. The 'Command' topic probe is just a DOS Command prompt on Windows (or a shell command on Linux). It's handy for debugging, but no out-of-box features use this because there are much better ways. The Powershell Probe (or SSH probe) could be used instead, but ideally the higher level Integration Hub step or Orchestration activity should be used. The benefits of using Integration Hub or Orchestration are: The MID Server platform's own Powershell execution framework will be used. This is robust and secure. The script will be wrapped in servicenow powershell scripts to manage the execution and data passing to/from the instance.The script can be run on remote hosts, in addition to the MID Server host.Credentials to run the script as, or Encrypted Parameters such as usernames and passwords or other confidential data, can be safely passed directly into the script, avoiding them appearing in plaintext in task manager, the ecc_queue or mid server logs.Timeouts can be implemented, to avoid stuck threads when the scripts go wrong, avoiding performance issues such as reduced or blocked processing, or CPU and memory issues of out of control scripts.In the case of timeouts, or other connection/network/certificate/authentication errors, the MID server can cleanly kill the script execution, and return meaningful errors to the instance.Automatic MID Selection can be used, so that individual MID Server outages don't cause an outage for the integration.You will have Visibility of the execution of the script, including any error messages during the execution of the powershell script, and authentication and connection logging, in the MID Server agent logs.Avoids syntax errors for the command line, due to XML, DOS command line, and Powershell command line escaping, such as for special characters, spaces in file/folder names, nested quotation marks, etc. Given that better safer alternatives exist, PowerShell is not supported for Command probe, and should be executed on MID Servers only via PowerShell and IPaaSActionProbe probes.