MID Server parameters for PowerShell
Parameters control the behavior of a particular MID Server and have lower precedence than MID Server properties.
The following parameters are optional.
Note: After changing the setting for any parameter, be sure to restart the MID Server service.
|
Name |
Description |
|---|---|
|
mid.powershell_api.session_pool.max_size |
Specifies the maximum number of sessions allowed in the session pool. Note: Setting or changing this parameter requires restarting the MID Server.
|
|
mid.powershell_api.session_pool.target.max_size |
Specifies the maximum number of sessions allowed in the pool per target host. Note: Setting or changing this parameter requires restarting the MID Server.
|
|
mid.powershell_api.winrm.use_ssl |
Requires the use of SSL certificates for HTTPS connections using WinRM.- Type: True | False
|
|
mid.powershell_api.winrm.additional_pssesion_options |
Controls advanced options for a PSSession. For more information about advanced PSSession options, see https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/new-pssessionoption?view=powershell-6. |
|
mid.powershell_api.winrm.remote_https_port |
Configures the port for connecting to Windows servers using PowerShell over HTTPS. - Type: Integer
|
|
mid.powershell_api.winrm.remote_port |
Configures the port for connecting to Windows servers using PowerShell over HTTP. - Type: Integer
|
|
mid.powershell_api.winrm.skip_ssl_cert_check |
Skips the SSL certificate check when using WinRM for HTTPS connections.- Type: True | False
|
|
mid.powershell_api.winrm.skip_ssl_cert_check_options |
Skips specific SSL certificate checks when using WinRM for HTTPS connections. Configure the MID Server to skip checks for certificates from a Certification Authority (CA), from the Common Name (CN) that identifies the host associated with the certificate, and for revoked certificates.
|
|
mid.powershell_api.wmi.use_reverse_dns_lookup |
Enable this property to utilize Kerberos authentication when employing the WMI protocol to communicate with Windows target devices. When activated, the system performs a reverse DNS look-up of IP addresses, enabling the use of Fully Qualified Domain Names (FQDN) instead of IP addresses. This can facilitate Kerberos authentication. Note: Note: If the reverse DNS look-up fails, the system may revert to using the IP address. Additionally, performing reverse DNS look-ups on IP addresses may impact performance.
|
|
mid.powershell.prefer_7_plus |
Sets the MID Server to prefer PowerShell 7 or later, if available, when running File-based Discovery and Windows ADME scripts locally on the MID Server host.- Type: true | false
For more information, see Configure MID Server parameters for PowerShell 7. |
|
mid.powershell.prefer_7_plus_remote |
Sets the MID Server to prefer PowerShell 7 or later, if available, on remote target hosts when running File-based Discovery and Windows ADME.- Type: true | false
For more information, see Configure MID Server parameters for PowerShell 7. |
|
mid.powershell.use_credentials |
Determines the credentials to use for Discovery with PowerShell. A setting of true directs the MID Server to run probes with the Windows credentials from the credentials table. To run probes with the credentials of the user for the MID Server service, set this parameter to false.
|
|
mid.use_powershell |
Enables or disables PowerShell for Discovery. Restart the MID Server after changing the value. If PowerShell is not installed or the version installed is less than version 2.0, Discovery reverts to using WMIRunner.
|
|
mid.powershell.path |
Enables an administrator to point to a specific PowerShell on a MID Server in cases where more than one PowerShell is installed. Supply the path to the folder containing the PowerShell executable, for example, Note: On a 64-bit version of Windows XP, a Microsoft hotfix may be required to enable this. To discover applications running on a 64-bit Windows machine, the MID Server must be running on a 64-bit Windows host machine.
|
|
mid.powershell.enforce_utf8 |
Enable this parameter to force commands on a target Windows system to return UTF-8 encoded output. Disabling it allows the target system to use its default encoding. This parameter is only valid when PowerShell is enabled.Setting this value to false may result in incorrect values in the CMDB when non-ASCII characters are returned by a probe.
|
|
mid.powershell.local_mid_service_credential_fallback |
Specifies the login credentials the MID Server uses if all other credentials fail.- Type: True | False
|
|
mid.powershell_api.idle_session_timeout |
Specifies the timeout value of idle PowerShell sessions in seconds. Note: Setting or changing this parameter requires restarting the MID Server.
|
|
mid.powershell.command.parameter_passing |
Enable this parameter to allow passing PowerShell parameters from the command line.- Type: True | False
|
|
mid.powershell.command.script.parameter_passing |
Enable this parameter to allow passing PowerShell scripts from the command line.- Type: True | False
|
|
mid.windows.management_protocol |
Enables administrators to select the Windows management protocol used for device and process classification. Options include:
|
|
mid.windows.probe_timeout |
Sets the timeout interval for all Windows probes on a specific MID Server. This value is overridden by the values configured for individual probes with the wmi_timeout probe parameter.- Type: Integer
|
--- title: MID Server parameters for PowerShell description: Parameters control the behavior of a particular MID Server and have lower precedence than MID Server properties. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/it-operations-management/discovery/mid-server-parameter-powershell.html release: australia product: Discovery classification: discovery topic_type: reference last_updated: "2026-09-10" reading_time_minutes: 4 breadcrumb: [PowerShell for Discovery and Service Mapping, Advanced Discovery configuration, Configuring Discovery, Discovery, ITOM Visibility, IT Operations Management] --- # MID Server parameters for PowerShell Parameters control the behavior of a particular MID Server and have lower precedence than MID Server properties. The following parameters are optional. **Note:** After changing the setting for any parameter, be sure to restart the MID Server service. <table id="table_trv_b4r_pfb"><thead><tr><th> Name </th><th> Description </th></tr></thead><tbody><tr><td> mid.powershell\_api.session\_pool.max\_size </td><td> Specifies the maximum number of sessions allowed in the session pool. **Note:** Setting or changing this parameter requires restarting the MID Server. - Type: Integer - Default value: 25 </td></tr><tr><td> mid.powershell\_api.session\_pool.target.max\_size </td><td> Specifies the maximum number of sessions allowed in the pool per target host. **Note:** Setting or changing this parameter requires restarting the MID Server. - Type: Integer - Default value: 3 </td></tr><tr id="MIDServerPowershell_useSSL"><td> mid.powershell\_api.winrm.use\_ssl </td><td> Requires the use of SSL certificates for HTTPS connections using WinRM.- Type: True \| False - Default value: false </td></tr><tr id="MIDServerPowershell_additionalPSSessionOptions"><td> mid.powershell\_api.winrm.additional\_pssesion\_options </td><td> Controls advanced options for a PSSession. For more information about advanced PSSession options, see [https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/new-pssessionoption?view=powershell-6](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/new-pssessionoption?view=powershell-6). </td></tr><tr id="MIDServerPowershell_APIWinrmRemoteHttpsPort"><td> mid.powershell\_api.winrm.remote\_https\_port </td><td> Configures the port for connecting to Windows servers using PowerShell over HTTPS. - Type: Integer - Default value: 5986 </td></tr><tr id="MIDServerPowershell_APIWinrmRemotePort"><td> mid.powershell\_api.winrm.remote\_port </td><td> Configures the port for connecting to Windows servers using PowerShell over HTTP. - Type: Integer - Default value: 5985 </td></tr><tr id="MIDServerPowershell_skipSSLCertCheck"><td> mid.powershell\_api.winrm.skip\_ssl\_cert\_check </td><td> Skips the SSL certificate check when using WinRM for HTTPS connections.- Type: True \| False - Default value: false </td></tr><tr id="MIDServerPowershell_skipSSLCertCheckOptions"><td> mid.powershell\_api.winrm.skip\_ssl\_cert\_check\_options </td><td> Skips specific SSL certificate checks when using WinRM for HTTPS connections. Configure the MID Server to skip checks for certificates from a Certification Authority \(CA\), from the Common Name \(CN\) that identifies the host associated with the certificate, and for revoked certificates. - Type: String - Default value: -SkipCACheck -SkipCNCheck -SkipRevocationCheck </td></tr><tr><td> mid.powershell\_api.wmi.use\_reverse\_dns\_lookup </td><td> Enable this property to utilize Kerberos authentication when employing the WMI protocol to communicate with Windows target devices. When activated, the system performs a reverse DNS look-up of IP addresses, enabling the use of Fully Qualified Domain Names \(FQDN\) instead of IP addresses. This can facilitate Kerberos authentication. **Note:** Note: If the reverse DNS look-up fails, the system may revert to using the IP address. Additionally, performing reverse DNS look-ups on IP addresses may impact performance. - Type: True \| False - Default value: False </td></tr><tr><td> mid.powershell.prefer\_7\_plus </td><td> Sets the MID Server to prefer PowerShell 7 or later, if available, when running File-based Discovery and Windows ADME scripts locally on the MID Server host.- Type: true \| false - Default value: false For more information, see [Configure MID Server parameters for PowerShell 7](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/config-mid-params-ps7.md). </td></tr><tr><td> mid.powershell.prefer\_7\_plus\_remote </td><td> Sets the MID Server to prefer PowerShell 7 or later, if available, on remote target hosts when running File-based Discovery and Windows ADME.- Type: true \| false - Default value: false For more information, see [Configure MID Server parameters for PowerShell 7](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/config-mid-params-ps7.md). </td></tr><tr id="MIDServerPowershell_useCredentials"><td> mid.powershell.use\_credentials </td><td> Determines the credentials to use for Discovery with PowerShell. A setting of true directs the MID Server to run probes with the Windows credentials from the credentials table. To run probes with the credentials of the user for the MID Server service, set this parameter to false. - Type: true \| false - Default value: true </td></tr><tr id="MIDServerPowershell_UsePowerShell"><td> mid.use\_powershell </td><td> Enables or disables PowerShell for Discovery. Restart the MID Server after changing the value. If PowerShell is not installed or the version installed is less than version 2.0, Discovery reverts to using WMIRunner. - Type: true \| false - Default value: true </td></tr><tr id="MIDServerPowershell_Path"><td> mid.powershell.path </td><td> Enables an administrator to point to a specific PowerShell on a MID Server in cases where more than one PowerShell is installed. Supply the path to the folder containing the PowerShell executable, for example, `C:\mypowershell` or `C:\mypowershell\`. ServiceNow automatically appends the string powershell.exe to the path. Configure this parameter when both a 32-bit and 64-bit PowerShells are active on the same MID Server, and it becomes necessary to launch the correct PowerShell for the context. 64-bit Windows employs file system redirection and the MID Server runs as a 32-bit application. If trying to specify a path in %WinDir%\\System32, Windows automatically redirects to %WinDir%\\SysWOW64. To avoid redirection, specify the path as %WinDir%\\Sysnative. For example, instead of C:\\WINDOWS\\system32\\WindowsPowerShell\\v1.0\\, specify C:\\WINDOWS\\sysnative\\WindowsPowerShell\\v1.0\\. **Note:** On a 64-bit version of Windows XP, a Microsoft hotfix may be required to enable this. To discover applications running on a 64-bit Windows machine, the MID Server must be running on a 64-bit Windows host machine. - Type: string \(path\) - Default value: none </td></tr><tr id="MIDServerPowershell_enforceUTF8"><td> mid.powershell.enforce\_utf8 </td><td> Enable this parameter to force commands on a target Windows system to return UTF-8 encoded output. Disabling it allows the target system to use its default encoding. This parameter is only valid when PowerShell is enabled.Setting this value to false may result in incorrect values in the CMDB when non-ASCII characters are returned by a probe. - Type: true \| false - Default value: true </td></tr><tr><td> mid.powershell.local\_mid\_service\_credential\_fallback </td><td> Specifies the login credentials the MID Server uses if all other credentials fail.- Type: True \| False - Default value: true </td></tr><tr id="MIDServerPowershell_idleSessionTimeout"><td> mid.powershell\_api.idle\_session\_timeout </td><td> Specifies the timeout value of idle PowerShell sessions in seconds. **Note:** Setting or changing this parameter requires restarting the MID Server. - Type: Integer - Default value: 60 </td></tr><tr id="MIDServerPowershell_parameterPassing"><td> mid.powershell.command.parameter\_passing </td><td> Enable this parameter to allow passing PowerShell parameters from the command line.- Type: True \| False - Default value: false </td></tr><tr id="MIDServerPowershell_ScriptParameterPassing"><td> mid.powershell.command.script.parameter\_passing </td><td> Enable this parameter to allow passing PowerShell scripts from the command line.- Type: True \| False - Default value: false </td></tr><tr><td> mid.windows.management\_protocol </td><td> Enables administrators to select the Windows management protocol used for device and process classification. Options include: - WMI - WinRM - Type: String - Default value: WMI </td></tr><tr><td> mid.windows.probe\_timeout </td><td> Sets the timeout interval for all Windows probes on a specific MID Server. This value is overridden by the values configured for individual probes with the wmi\_timeout probe parameter.- Type: Integer - Default value: 600 </td></tr></tbody> </table>**Parent Topic:**[PowerShell for Discovery and Service Mapping](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/r_PowerShellForDiscovery.md)
| title | MID Server parameters for PowerShell |
| description | Parameters control the behavior of a particular MID Server and have lower precedence than MID Server properties. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/australia/it-operations-management/discovery/mid-server-parameter-powershell.html |
| release | australia |
| product | Discovery |
| classification | discovery |
| topic_type | reference |
| last_updated | 2026-09-10 |
| reading_time_minutes | 4 |
| breadcrumb | PowerShell for Discovery and Service MappingAdvanced Discovery configurationConfiguring DiscoveryDiscoveryITOM VisibilityIT Operations Management |