Which must be configured to allow a MID Server to access servers using WinRM?

To configure a MID Server to use Windows Remote Management (WinRM) instead of the default Windows Management Instrumentation (WMI) protocol for Discovery, administrators must add and configure a specific MID Server parameter. Specifically, the parameter 'mid.windows.management_protocol' needs to be explicitly created or modified within the MID Server's configuration properties and assigned the value 'WinRM'. This configuration instructs the specific MID Server agent to leverage the WinRM protocol for executing commands and fetching data from target Windows hosts, fulfilling modern security and network transport requirements without requiring architectural protocol changes directly inserted into the registry of every target by the ServiceNow platform.

[Option A] The configuration is pushed centrally via the MID Server parameters in ServiceNow, not by adding a tool-specific parameter physically on every target server. [Option C] The Discovery source strictly identifies the system that created the CI; it has no relationship to network protocols or enabling WinRM transport. [Option D] JIRA properties relate exclusively to the integration of Atlassian JIRA and have absolutely no function in ServiceNow's MID Server Windows discovery processes.

ServiceNow Product Documentation, IT Operations Management, "Windows Remote Management (WinRM) for Discovery" (Section: Configure WinRM properties).

ServiceNow Knowledge Base, KB0723821: "Configuring WinRM for Discovery and Orchestration".