I can tell you...
this identification detection its accuracy is chaos...
sometimes it's good, sometimes it's very bad...
I have tested various devices many times, e.g. android, windows
ASUS android phone: mostly "Other Network Device" type, bad good identification..
SONY xperia: as the same above ASUS phone
Windows 2012/2016 with LBFO enabled: obviously, "Other Network Device" type; it definitely can not recognize this device as "Windows device" type..
other windows devices which includes hyper-v vm, no LBFO/LACP enabled: good, almost Windows device type...
other android mobile devices: sometimes "Other Network Device" type, sometimes "android device " type; accuracy it's chaos...
I have not yet tested linux device, but I have Synology NAS devices based on linux: delete this from device list and re-detect it several times=> "Other Network Device" type...oops
older v5.2, this function is working fine...
but since v5.4, definitely it's bad for what fortinet change something...
about soc3 box:
The device identification active scan feature uses the port scanning feature provided by the VCM (Vulnerability and Compliance Management) feature. That implies that device active scanning is/was only supported on models that supported VCM.
The VCM feature was deprecated in FortiOS 5.4 and removed in FortiOS 5.6.
The SOC3 models went through the NPI process during that time and since VCM was being removed then no work was done to enable it to run on the SOC3.
It is by design of V5.6 that active scanning is not support on model which is using SOC3.