ExportXMLWordPrintable

    • Type: Incident report
    • Resolution: Unresolved
    • Priority: Trivial
    • None
    • Affects Version/s: 8.0.0
    • Component/s: Templates (T)
    • None

      I'll be blunt, this was summarised by AI but helped to get the proper layout/details. The human written TLDR; AVMA activated servers get flagged constantly as grace period running out due to a much shorter grace period for AVMA activated servers of 7 days.

      Summary:
      Windows by Zabbix agent active: "Windows: Activation grace period running out" fires permanently on licensed AVMA (Automatic Virtual Machine Activation) guests

      Template: Windows by Zabbix agent active, template version 8.0-2 (Zabbix 8.0)
      Agent: Zabbix agent 2 <version>, active checks
      Affected OS: Windows Server guests on Hyper-V hosts running Windows Server Datacenter, activated by AVMA

      Steps to reproduce:
      1. Activate a Windows Server VM with AVMA on a Datacenter Hyper-V host (slmgr /ipk <AVMA key>).
      2. Link "Windows by Zabbix agent active" to the host.
      3. Wait for "Windows activation: Get product info" to collect data.

      Result:
      "Windows: Activation grace period running out (less than 30d left, current: 4d 4h ...)" is raised and never clears.
      At the same time, the host is fully licensed:
        Description       : Windows(R) Operating System, VIRTUAL_MACHINE_ACTIVATION channel
        LicenseStatus     : 1 (Licensed)
        GracePeriodRemaining : ~6019 (minutes)
        Application log Event 12309, every 7 days: "The client has processed an Automatic VM activation response from the parent partition. Returned hr=0x00000000"
      "Windows: Is not licensed" correctly stays OK.


       

      Expected:
      No problem on a licensed host where activation renews normally.

      Cause:

      • activation.grace = SoftwareLicensingProduct.GracePeriodRemaining * 60.
      • For volume-licensed clients, Microsoft defines GracePeriodRemaining as "the remaining time before reactivation is required", not a grace period.
      • AVMA activation is valid for 7 days and the guest renews it from the host every 7 days, so on a healthy AVMA guest the value always cycles between ~7d and ~0.
      • The trigger is last(activation.grace)>0 and last(activation.grace)<{$WINDOWS.SECURITY.ACTIVATION.GRACE.MIN.WARN} (default 30d). It doesn't consider LicenseStatus or the activation channel, so it is always true on AVMA guests.
      • Because renewal happens right as the 7-day validity runs out, no macro value above 0 avoids false positives. The only workaround is setting the macro to 0, which turns the trigger off.
      • KMS clients are not affected (validity 180d), and retail/MAK clients report 0, which the ">0" condition excludes.

      References:

            Assignee:
            Zabbix Integration Team
            Reporter:
            Ross Fawcett
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: