Overview

MSP organizations sometimes are not sure how to identify users associated with issued licenses. This article explains how the "Reminder ID" can be used to track monthly license usage.

Solution

The Reminder ID is a unique identifier generated by each KerioControl instance. It is used for internal tracking and reporting purposes, and helps partners map KerioControl instances when there are no domain names available.

It can be found in the KerioControl configuration file using the steps below, as long as you have administrative access to the KerioControl device.

1. Log in to the KerioControl administration interface, navigate to System Health, and enable SSH. If needed, refer to Accessing Kerio Control's Shell Using SSH for details.
2. Open WinSCP or another SSH client and connect to the KerioControl device using its IP address and SSH credentials.
3. Navigate to the following location: cd /opt/kerio/winroute/ and open the winroute.cfg file, which contains the device configuration.
4. Search for the section in the configuration that includes the "ProductReminderId." The number next to `ProductReminderId` is the unique identifier you need. Example of the relevant section:

   ```xml
       <table name="Update">
          <variable name="ServerUrl">https://prod-update.kerio.com/checknew.php</variable>
          <variable name="ProductReminderId">1178778</variable>
          <variable name="ProductReminderAuth">1118081222</variable>
       </table>
       ```

5. Partners can use the Reminder ID to map KerioControl instances by filtering reports based on the Reminder ID - you can track monthly usage and associate it with specific instances of KerioControl.

Telemetry example:

[
  {
    "IDX": 1112211112,
    "Reminder_ID": 1178778,
    "Reminder_Auth": 1118081222,
    "License": "12345-6789Y",
    "Report_Version": 3,
    "Time_Inserted": "2024-09-02 22:04:21.000",
    "Prod_Code": "KWF",
    "OS_Timezone": "+0100",
    "OS_Name": "Kerio Control Box NG300 Series",
    "OS_Platform": "HWANG300W.X64",
    "OS_Langusr": "en_US",
    "OS_Langsys": "en_US",
    "OS_Major": 0,
    "OS_Minor": 0,
    "OS_Build": 0,
    "OS_Product": "LINUX",
    "OS_Suite": "",
    "Prod_Build": 4,
    "Prod_Major": 9,
    "Prod_Minor": 4,
    "Prod_Build_Number": 9174,
    "Prod_Lang": "en_US",
    "Install_Type": " ",
    "Users_Utilized": 29,
    "Users_Licensed": 10,
    "Client_StatisticsAS": "",
    "Client_StatisticsASVersion": 0,
    "Client_StatisticsCalDAV": "",
    "Client_StatisticsCalDAVVersion": 0,
    "Plugin_AV_Code": "avir_bitdefender",
    "Processed": false,
    "Client_Statistics": "",
    "Client_StatisticsVersion": 0
  }
]

Note: you can also see correlating usage data per KerioControl in GFI AppManager.

Summary

This article explains how MSP organizations can identify users associated with KerioControl licenses using the "Reminder ID." The Reminder ID is a unique identifier in the KerioControl configuration file that helps track monthly license usage. It can be found by accessing the winroute.cfg file on the KerioControl device via SSH. The Reminder ID allows partners to map KerioControl instances and filter reports for usage tracking.

FAQ

1. How can I locate the Reminder ID in a KerioControl device?
   To find the Reminder ID, log in to the KerioControl administration interface, enable SSH under System Health, and access the device via an SSH client. Then, navigate to /opt/kerio/winroute/ and open the winroute.cfg file. Search for the "ProductReminderId" section in the configuration.
2. What is the purpose of the Reminder ID in KerioControl?
   The Reminder ID is used for internal tracking and reporting. It helps MSPs map KerioControl instances when domain names are unavailable, enabling them to track license usage on a monthly basis.
3. Can the Reminder ID be used to track usage across multiple KerioControl instances?
   Yes, the Reminder ID can be used to filter reports and track license usage across different KerioControl instances, making it easier to manage and monitor multiple devices.