When trying run discovery on few devices we may see the error as below in classification phase:
"Cannot read property "0" from undefined"
Sensor error when processing Windows - Classify: TypeError: Cannot read property "0" from undefinedStack: at discovery_sensor.b11453f50a0a0ba500a72547a687189e:158 (anonymous) at discovery_sensor.b11453f50a0a0ba500a72547a687189e:66 (anonymous) at discovery_sensor.b11453f50a0a0ba500a72547a687189e:45 (anonymous) at sys_script_include.778011130a0a0b2500c4595ad1d1d768.script:194 (anonymous) at sys_script_include.778011130a0a0b2500c4595ad1d1d768.script:149 (anonymous) at sys_script_include.778011130a0a0b2500c4595ad1d1d768.script:112 (anonymous) at sys_script_include.778011130a0a0b2500c4595ad1d1d768.script:25 (anonymous) at sys_script_include.d22e7bdbc0a8016500a18e024bfc9aa3.script:4 (anonymous) at discovery_sensor.b11453f50a0a0ba500a72547a687189e:1 at sys_script_include.78dfb2dd536002001f175f43911c087d.script:13 (anonymous) at sys_trigger.0dbd0d3a1b68d85c839d751bdd4bcb00:2 (sys_script_include.778011130a0a0b2500c4595ad1d1d768.script; line 56)
Release or Environment
There are a couple of reasons for this issue as defined below:
1) There could be some GPO (Group Policy Objects) that might be restricting the access for the scripts (.ps1) we run during the discovery.
2) You might have some kind of anti-virus software (with intrusion policies) that might be blocking the access.
- Check your GPO policies on the target device and see if any blocking policies exist. More details can be found in "the Issue with WMI/Powershell: Classify sensor".
There could be multiple software or applications related to security that might block access to run the classification scripts (ex: .ps1) on targets. Samples are given as below:
- Ivanti Application Control
Check on these application security restrictions and see if it is causing the issue. If yes, try disabling the policies and see if that works.