Uploaded image for project: 'ZABBIX FEATURE REQUESTS'
  1. ZABBIX FEATURE REQUESTS
  2. ZBXNEXT-6848

Get exact Windows Build number and patch level via Zabbix agent

XMLWordPrintable

    • Icon: New Feature Request New Feature Request
    • Resolution: Fixed
    • Icon: Major Major
    • 6.4.0beta6, 6.4 (plan)
    • 5.4.3
    • Agent (G)
    • None
    • Windows 10 since Feature level 1607 aka Windows Server 2016
    • Sprint 94 (Nov 2022), Sprint 95 (Dec 2022)
    • 1

      Since Windows 10 or Windows Server 2016, it's possible to identify the exact version and patch level of any Windows, by looking at it's build number, for example: Start -> Run -> winver.exe


      With the help of this number, and the very good reference documentation from Microsoft, this can make very good inventory values and can make very good patch level monitoring values.
      Example list for Windows Server 2019 build numbers and patch levels: https://support.microsoft.com/en-us/help/4464619
      2016: https://support.microsoft.com/en-us/help/4000825

      It's easy to get this value with a UserParameter, but it's important enough to work out of the box IMHO.

      I suggest an item key similar to: system.sw.os which currently only works on Linux agents, but not on Windows agents.

      The return value should look like this: 17763.2114

        1. image-2021-08-23-10-58-41-468.png
          16 kB
          Marco Hofmann
        2. image-2021-08-23-10-59-22-178.png
          15 kB
          Marco Hofmann
        3. image-2022-11-08-16-53-30-901.png
          66 kB
          Michael Veksler
        4. screenshot-1.png
          777 kB
          Sergejs Maklakovs
        5. ZBXNEXT-6848-mini-spec_1_2.pdf
          56 kB
          Alex Kalimulin
        6. ZBXNEXT-6848-mini-spec.pdf
          56 kB
          Alex Kalimulin

            kprutkovs Konstantins Prutkovs (Inactive)
            starko Marco Hofmann
            Team C
            Votes:
            3 Vote for this issue
            Watchers:
            20 Start watching this issue

              Created:
              Updated:
              Resolved: