Discover windows server with JEA configured but no TCP connections returnDescriptionDiscovery Windows server with JEA but "TCP connections" not being populated to windows server CI. Mid server log snippet show netstat cannot be run: 08/20/21 15:43:31 (209) Worker-Interactive:MultiProbe-da6dcb8a1b8ef41049f1631b274bcbbc DEBUG: execute(& { launchProcess -computer $computer -cred $cred -command 'netstat.exe -anop TCP' } | Out-String | ForEach-Object { [Console]::WriteLine($_) }), command id: d8bcc019-ef55-4a6a-a0a3-4d03f8e60e6b 08/20/21 15:43:31 (224) PowerConsole-da6dcb8a1b8ef41049f1631b274bcbbc>stderr DEBUG: STDERR d8bcc019-ef55-4a6a-a0a3-4d03f8e60e6b: -----START OF STDERR----- 08/20/21 15:43:31 (224) PowerConsole-da6dcb8a1b8ef41049f1631b274bcbbc>stdout DEBUG: STDOUT d8bcc019-ef55-4a6a-a0a3-4d03f8e60e6b: -----START OF STDOUT----- 08/20/21 15:43:31 (693) PowerConsole-da6dcb8a1b8ef41049f1631b274bcbbc>stderr DEBUG: STDERR d8bcc019-ef55-4a6a-a0a3-4d03f8e60e6b: The term 'cmd.exe' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. 08/20/21 15:43:31 (693) PowerConsole-da6dcb8a1b8ef41049f1631b274bcbbc>stderr DEBUG: STDERR d8bcc019-ef55-4a6a-a0a3-4d03f8e60e6b: + CategoryInfo : ObjectNotFound: (cmd.exe:String) [], CommandNotFoundException 08/20/21 15:43:31 (693) PowerConsole-da6dcb8a1b8ef41049f1631b274bcbbc>stderr DEBUG: STDERR d8bcc019-ef55-4a6a-a0a3-4d03f8e60e6b: + FullyQualifiedErrorId : CommandNotFoundException 08/20/21 15:43:31 (693) PowerConsole-da6dcb8a1b8ef41049f1631b274bcbbc>stderr DEBUG: STDERR d8bcc019-ef55-4a6a-a0a3-4d03f8e60e6b: + PSComputerName : xxx.xx.xx.xxx Steps to Reproduce Run discovery to Windows server with JEA configuredWorkaroundUpdated "WMI_ActiveConnections.ps1" (attached discovery_probe_parameter_7dfc5f870a000483000169d19b46c06d.xml) for workaroundRelated Problem: PRB1521657