Verify product license and feature entitlement state#

When to use this procedure#

Use for trial or registered-status, license-validation, edition, and feature-denied events.

Applies to#

This procedure applies to EventReporter.

Prerequisites#

  • Use an account that can read the product configuration and Windows diagnostic state.

  • Replace angle-bracket placeholders with values from the affected system.

Safety#

  • Never publish license files, signed payloads, keys, customer identifiers, or activation material.

  • Do not edit a signed license file.

Configuration path#

Configuration Client > General > License.

Procedure#

  1. Record product version, displayed license status, edition, and feature named in the event without copying the license payload.

    Expected result: The running product, version, edition, license mode, and required feature or client allowance are known without exposing license material.

    If it fails: Do not copy the license file or key; record only the product UI’s status and non-secret version information.

  2. Verify the running executable’s product and version, then compare the displayed entitlement with the state identified by the event. For a denial event, also compare the named module, feature, or client allowance.

    Get-Item -LiteralPath '<PRODUCT_EXECUTABLE>' | Select-Object -ExpandProperty VersionInfo | Format-List ProductName,ProductVersion,FileVersion

    Expected result: For a denial event, the authorized license targets the running product and version and includes the required feature or sufficient client capacity. For a status reminder, the displayed state matches the intended product and edition.

    If it fails: For a denial event, install authorized replacement license material or disable the unsupported configuration. For an unexpected status reminder, record the non-secret product version and displayed state before seeking license assistance; never edit signed data.

  3. For a denial event after changing license material, restart or reload only as required, then test the previously denied module or intended sender once. For a status reminder, do not change licensing; confirm the displayed state and that the service continues normally.

    Expected result: For a denial event, the service remains Running and the intended module or sender processes the test exactly once without a license-denial event. For a status reminder, the displayed license state is expected and the service remains Running.

    If it fails: Record the new license-status and denial events without sharing license data; do not repeatedly reinstall or alter the license.

Verify the result#

For a denial event, confirm the intended license mode in the product UI and prove the previously denied module or sender works once without exposing license material. For a status reminder, confirm that the displayed license mode and service state are expected.

Evidence to collect#

  • The complete Event Log entry and neighboring product events with timestamps.

  • Product name, executable version, displayed edition or license mode, and the non-secret feature or client allowance involved.

  • A redacted configuration export showing only the affected object; never collect license files, keys, signed payloads, activation data, or customer identifiers.