Discovery messages: WMI collector failed. Unable to restart WMI collectorIssue According to "WMI Collector deprecation details" documentation, it has been updated that starting Orlando release the WMI collector will be depreciated and using Powershell for Discovery & Service Mapping will be Mandatory. In case of using Powershell is not approved or having environmental issues for the Discovery and Service Mapping, the workaround is to reinstall the WMI according to "Reinstall the WMI Collector for Orlando" It has been observed that post upgrading to Orlando the PowerShell fails with the below error while executing ServiceMapping Discovery. Discovery messages: WMI collector failed. Unable to restart WMI collector: exit code 2 [SC] StartService FAILED 2: The System cannot find the file specified. ReleaseInstance upgraded to Orlando.CauseThe error during ServiceMapping discovery was regarding not being able to start up the WMI Collector Service. According to the changes in Orlando, ServiceMapping should not be the case since we should be using PowerShell.The issue is because of multiple MID Server Properties on the instance for "mid.sa.prefer_powershell". One specific for MID LCC which has a value "true" and one global (for every MID) with value "false" https://<Instancename>.service-now.com/ecc_agent_property_list.do?sysparm_query=name%3Dmid.sa.prefer_powershell&sysparm_first_row=1&sysparm_view= There is part of the known issue "PRB1402706", with the "mid.sa.prefer_powershell" property overriding each other.ResolutionAs a workaround Reinstall the WMI Collector "Reinstall the WMI Collector for Orlando"If want to use the Powershell but not WMI, suggest deleting all MID property "mid.sa.prefer_powershell" because it will default to true anyway and the OOB property is deleted after Orlando upgrade. Follow the below procedure, if there is only 1 MID server host shared between multiple instances or 1 MID server host have 2 MID servers configured for the same instance. Below procedure considering one MID host configured for 2 Instances. Make sure to configure both the MID services use unique ports, refer below Create a dedicated WMI Collector service for MID Servers running on the same server On the MID host, download an Orlando Patch 4 MID zip: Download Orlando P4 MID Server Package Stop the DEV MIDNavigate to the MID agent folder and make a backup copy of the lib folderOpen the downloaded zip file and extract the entire lib folder to the DEV MID agent folder (to replace the existing lib folder)Make sure there is only one MID property "mid.sa.prefer_powershell" that applies to all MIDs (field MID Server has an empty value) and its value is true (default)Make sure no WMI Runner services are running in the instance.Start the MID ServicesExecute Discovery on Servicemapping and observe the Discovery work as expected.