Discovery and Wyse/Thin Clients

Droid101
Kilo Explorer

‎11-10-2010 12:50 PM

I'm having trouble finding our terminals when doing a discovery on an IP range.

Is it able to find these types of devices and list all their information as it does for PC's?

Labels:
0 Helpfuls
  • 4,968 Views
10 REPLIES 10

doug_schulze
ServiceNow Employee
ServiceNow Employee

‎11-10-2010 01:52 PM

If you find the right type of query I'm sure you could, but it has to be found through the local OS...perhaps a SSH command or wmi query?


0 Helpfuls

nortonxnorris
Giga Expert
In response to doug_schulze

‎08-25-2014 07:08 AM

Hello Doug,


I tried a scan using ssh only and wmi only. No results were returned from the probe for either. When i try the same without defining a behavior, it uses SNMP.


0 Helpfuls

doug_schulze
ServiceNow Employee
ServiceNow Employee
In response to nortonxnorris

‎09-09-2014 01:04 PM

So it does respond with SNMP?   If so Watch this..



https://www.youtube.com/watch?v=6ULRbpGOSB4


0 Helpfuls

christopherluca
Kilo Contributor
In response to doug_schulze

‎10-15-2014 10:44 AM

Hey Doug - Norton and I are working together on this project.   From our scans of a thin client - the sysdesc OID in the SNMP-Classify input log is "1.3.6.1.4.1.311.1.1.3.3" classifying the device/asset as "Microsoft Windows CE Version 4.20" (likely the thin O/S running on the WYSE).   WYSE MIB's start with 1.3.6.1.4.1.714.x and I'm not seeing any references to this or similar in the SNMP-Classify input log.  



Just for kicks, I made a new Classifier with that basic WYSE MIB to see if it would at least grab that and then walk down the appropriate table to reveal the specific MFR/MODEL/Serial objects, but no dice.   How do we tell our SNMP identity probe to call the actual device OID's and not default to the thin O/S for identification?


0 Helpfuls