JEA Discovery classify probe error 'Cannot read property "0" from undefined'Issue Please note that this KB is for JEAv1 and not for V2. JEA Discovery classify probe error 'Cannot read property "0" from undefined'. Review of MID server logs, with mid parameter mid.log.level = debug, reveal root cause error: PowerConsole-8949379cdbf29010c7694c95b996193d>stderr DEBUG: STDERR: The syntax is not supported by this runspace. This can occur if the runspace is in no-language mode. PowerConsole-8949379cdbf29010c7694c95b996193d>stderr DEBUG: STDERR: + CategoryInfo : ParserError: (function printV...me|format-list;:String) [], ParseException PowerConsole-8949379cdbf29010c7694c95b996193d>stderr DEBUG: STDERR: + FullyQualifiedErrorId : ScriptsNotAllowed PowerConsole-8949379cdbf29010c7694c95b996193d>stderr DEBUG: STDERR: + PSComputerName : 10.110.80.193 PowerConsole-8949379cdbf29010c7694c95b996193d>stderr DEBUG: STDERR: PowerConsole-8949379cdbf29010c7694c95b996193d>stdout DEBUG: STDOUT: {} PowerConsole-8949379cdbf29010c7694c95b996193d>stdout DEBUG: STDOUT: PowerConsole-8949379cdbf29010c7694c95b996193d>stdout DEBUG: STDOUT: MI8D_COMMAND_COMPLETE Note: 'Cannot read property "0" from undefined' error is seen when the input from the windows classify probe is empty. Such error is a symptom, not the root cause. The MID server logs need to be reviewed for more information. Here, the true root cause is error "The syntax is not supported by this runspace. This can occur if the runspace is in no-language mode."CauseJEA session configuration.ResolutionUpdate JEA session configuration file parameters "LanguageMode" and "SessionType" like so: # Modules that will be importedLanguageMode = 'FullLanguage'# Initial state of this session configurationSessionType = 'Default' Re-register the session configuration file: Register-PSSessionConfiguration -name <endpoint_name> -path "C:\Windows\System32\WindowsPowerShell\v1.0\Modules\<jea_folder_name>\jea_disco.pssc" Note: Edit the command above according to the environment being worked on, file locations, etc. Replace the <endpoint_name> with the name of your endpoint. For example, the command Register-PSSessionConfiguration -name JEA_DISCO -path "C:\Windows\System32\WindowsPowerShell\v1.0\Modules\<jea_folder_name>\jea_disco.pssc" creates an endpoint named JEA_DISCO. The setting affects the entire MID Server, including any WinRM remote session created by Discovery on the MID Server which go to that endpoint.Related LinksMicrosoft Just Enough Administration (JEA) for DiscoveryMicrosoft JEA Profiles for Discovery