"Windows - ADM" Probe not getting launchedIssue On San Diego, if no Powershell access or Admin Share access is detected, Windows discovery does not launch ADM.As a result, no Application Patterns are being launched for running processes.Prior to the upgrade, the ADM probe would still be launched without Powershell access or Admin Share access.CauseThe Condition script on "Windows - ADM" Probe for Windows Server Classifiers is failing for win_protocol = wmi and the Probe is not being triggered. Check the "WMI: Classify" input probe of the Discovery Status for the following parameters:<parameter name="win_protocol" value="wmi"/><parameter name="admin_share_access" value="false"/><parameter name="target_powershell_access" value="false"/> The 'win_protocol' should be "wmi" and either one of the 'admin_share_access' or 'target_powershell_access' should be false so that the condition will fail and the probe will not be launched.ResolutionWorkaround: Modify the Condition script on the "Windows - ADM" Probe for the Windows Classifier Probes:https://<instance_name>.service-now.com/discovery_classifier_probe_list.do?sysparm_query=child%3Dedae4993ef31010098d5925495c0fb6c&sysparm_first_row=1&sysparm_view=fromDiscoveryADMEConditions.shouldTriggerADM(discovery_source) && (g_probe.getParameter("win_protocol") == "winrm" || (g_probe.getParameter("admin_share_access") == "true" && g_probe.getParameter("target_powershell_access") == "true"))toDiscoveryADMEConditions.shouldTriggerADM(discovery_source) Adjust the condition script as described above and try running Discovery.