Notifications

621 views

Details

Applicable release

Orlando and later

Background

Discovery and Service Mapping using patterns to discover Windows previously used Windows Management Instrumentation (WMI) Collector. The WMI Collector service was a MID Server component that helped it to communicate with Windows servers.

In an effort to consolidate all the Windows discovery work inside the MID Server, we have removed the need to have a completely different service installed and running just to handle queries that we can perform directly, and much more easily. This also simplifies installation and configuration.

In the Orlando release, ServiceNow is deprecating WMI Collector and substituting it with PowerShell on the host machine. This change will be transparent as long as your MID Server is running PowerShell 3.0 up to 5.1.

Prior to Orlando

WMI Collector service [wmi_collector.exe] was used by Patterns to discover Windows servers.

https://docs.servicenow.com/bundle/newyork-it-operations-management/page/product/service-mapping/task/config-additional-wmi-collector.html

Upgrading to Orlando

When a MID Server upgrades to Orlando, it uninstalls the WMI Collector service. The Discovery and Service Mapping functionalities which previously used WMI Collector service [wmi_collector.exe] to query WMI are going to use PowerShell to query WMI. This setting is controlled by two MID Server properties, which both default to true:

  • mid.sa_prefer_powershell
  • mid.use_powershell

Additional Information

Requirements

  • Minimum PowerShell version 3.0
  • Maximum PowerShell version 5.1

Impacted products

Discovery and Service Mapping using Patterns

FAQ

If the same host has MID Servers for Orlando and New York instances, what happens?

  • The Orlando MID Server will use PowerShell.
  • The New York MID Server will use wmi_collector.exe.

 

Article Information

Last Updated:2020-01-06 06:41:50
Published:2020-01-06