Property reference

mid.windows.management_protocol

Sets the Windows management protocol a MID Server uses to communicate with remote Windows hosts. The default is WMI; choosing WinRM changes Windows discovery and classification to use WinRM, including for Just Enough Administration.

Default
Not stated
Type
Not stated
Application
Not stated

Key questions about this property

The answers below summarize the purpose, scope, default effect, and review scenarios for this property.

What does it do? Sets the MID Server’s protocol for Windows device and process classification to either WMI or WinRM; the default is WMI.
What area does it affect? MID Server Windows Discovery
What does the default mean? No default value is stated in the ServiceNow documentation.
When should you review it? Review when configuring Windows Discovery with WinRM or Just Enough Administration, or when changing the protocol used by a MID Server.

Property record

Facts stated in the ServiceNow documentation. No out of the box record has been read from an instance yet.

Property name mid.windows.management_protocol
Type Not stated
Application Not stated
Default value Not stated
Description Not stated

Sources

Official references and nearby text excerpts where this property appears.

Context preview Snippet 1
... Select a MID Server to configure from the list of MID Servers. 7. Select the Configuration Parameters related list. 8. Set the following MID Server config parameters as indicated: a. mid.windows.management_protocol: This parameter is required for Discovery with JEA. Its default value is WMI, but it must be set to WinRM on MID Servers using Discovery with JEA. b. mid.powershell.jea.endpoint: This ...
Context preview Snippet 2
... name goes down after failing the GetMIDInfo.do requests for ECCSenderCache MID Server PRB2022588 Windows Discovery takes ~3 minutes due to inefficient PowerShell module existence check using Get-Module -List when setting mid.windows.management_protocol=WinRM MID Server PRB2061457 App node reporting older build version causes the 'MID Server Version' job to assign incorrect Zurich packages, causing all MIDs to downgrade MID Server PRB1783689 The 'SWITCH' ...
Context preview Snippet 3
... on multiple factors: Create a “scripted” resource. ◦Expanding: Anything in { } is replaced by the system or MID Server property with that name. Logical operators are allowed, for example, "{mid.windows.management_protocol}".toLowerCase() == "winrm" ? 1:0 ◦Scripted: the script is evaluated. The return value is expanded. Procedure 1. Create a new resource. a. Navigate to Discovery Definition > Limited Resources> Simple Value ...

More in mid

Other properties in the same namespace.

All 257 properties in mid →