Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-4566

Microsoft Server identification confuses Standard and Datacenter Edition on Servers

Details

    • Vendor Bug
    • Resolution: Won't Fix
    • Major
    • None
    • Professional Edition
    • OS
    • None

    Description

      hi, it appears that observium is mis-identifying Windows Server editions.  I have many examples of observium listing a microsoft server as being Datacenter edition when it is in fact standard.  this seems to be centered around whether the server is a domain controller or not. 

      it seems to be a problem on all versions of server (ie: 2012r2, 2016, 2019, 2022)

      thanks

      Attachments

        Activity

          [OBS-4566] Microsoft Server identification confuses Standard and Datacenter Edition on Servers
          landy Mike Stupalov added a comment - - edited

          Detect Standard and Datacenter edition for Windows is simple (by sysObjectID):

          • .1.3.6.1.4.1.311.1.1.3.1.2 - for Standard
          • .1.3.6.1.4.1.311.1.1.3.1.3 - for Datacenter

          your host report sysObjectID as .1.3.6.1.4.1.311.1.1.3.1.3

          Not possible for improve on observium side.
          Probably you can report issue to Windows support, but I know that Microsoft abandoned any SNMP support.

          landy Mike Stupalov added a comment - - edited Detect Standard and Datacenter edition for Windows is simple (by sysObjectID): .1.3.6.1.4.1.311.1.1.3.1. 2 - for Standard .1.3.6.1.4.1.311.1.1.3.1. 3 - for Datacenter your host report sysObjectID as .1.3.6.1.4.1.311.1.1.3.1. 3 Not possible for improve on observium side. Probably you can report issue to Windows support, but I know that Microsoft abandoned any SNMP support.
          tonyg Tony Guadagno added a comment -

          here you go, thanks

          tonyg Tony Guadagno added a comment - here you go, thanks
          landy Mike Stupalov added a comment -

          General questions and device support can be discussed in our Discord channel, click here to join.

          Please make and attach additional information about the device:

          • full snmp dump from device: 

            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk
            		 
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

            If device not support SNMP version 2c, replace -v2c with -v1.

          • If you have problems with discovery or poller processes, please do and attach these debugs: 

            ./discovery.php -d -h <device>
            		 
            ./poller.php -d -h <device>

          • additionally attach device and/or vendor specific MIB files
          landy Mike Stupalov added a comment - General questions and device support can be discussed in our Discord channel, click here to join . Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files

          People

            landy Mike Stupalov
            tonyg Tony Guadagno
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: