# Set license key

## License Key Storage

KONNEKT searches for license keys in two registry keys:

`HKEY_CURRENT_USER\SOFTWARE\GlueckKanja\Konnekt\License` (REG SZ)

`HKEY_LOCAL_MACHINE\SOFTWARE\GlueckKanja\Konnekt\License` (REG SZ)

{% hint style="info" %}
If a license key is set at machine level (HKLM), it will supersede a license key at user level (HKCU). 
{% endhint %}

## License Key Configuration

There are several options how you can configure the license key:

|         Option        |                                                                 Description                                                                |                                                                          Use Case                                                                          | Lic Key Storage Location |
| :-------------------: | :----------------------------------------------------------------------------------------------------------------------------------------: | :--------------------------------------------------------------------------------------------------------------------------------------------------------: | :----------------------: |
| **Interactive Setup** |                                                 Enter the key during the interactive setup                                                 |                                                   This option may be a good choice for a singular system.                                                  |           HKLM           |
|       **Policy**      |                                                Set the license key via GPO or Intune policy.                                               | <p>This is the recommended approach for managed environments. <br>See <a href="#set-license-key-via-registry-gpo-mdm">Set License Key</a> for details.</p> |       HKLM or HKCU       |
|   **MSI Parameter**   | <p>Sets the license key as a MSI-parameter <br>(e.g. with silent <a href="../../../installation/setup#silent-installation">Setup</a>).</p> |                                    This option may be a good choice for environments with a software deployment system.                                    |           HKLM           |
|  **Preferences Menu** |                                               Enter the license key in the preferences menu.                                               |                                                   This option may be used for single user systems, only.                                                   |           HKCU           |

Entering the license key in the preferences menu:

![](https://2727108687-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8zLVuKYctMIUr68_fs%2Fuploads%2FL2e802WbrQAboIv8ZTZy%2F2022-08-02%2016_32_15-Window.png?alt=media\&token=ab470fd7-9747-4b0c-820c-80d8aeaec65d)

{% hint style="danger" %}
The preference menu sets the license for the current user (HKCU), only. Other users logging into the same machine would also have to set the license.

If a license key is configured at HKLM, settings via preferences menu are not effective. (see [Set License Key](#license-key-storage) for details).&#x20;
{% endhint %}

## Set License Key via Registry/GPO/MDM

Key name: **License**\
Type: REG\_SZ (String Value).

Sets the license key.

We recommend to use our [ADMX template](https://docs.konnekt.io/management-options/settings-via-gpo#admx-file) to configure this setting.

## **There are several ways to apply the policy:**

* manually by adding the key in the registry under machine or user registry settings
* via GPO, see [settings via GPO](https://docs.konnekt.io/configuration/management-options/settings-via-gpo)
* pushing policies via Intune, see [settings for Intune Managed Devices](https://docs.konnekt.io/management-options/setting-for-intune-managed-devices-1/intune-other-settings#set-license-key)

**Policies** stored in:

`HKEY_CURRENT_USER\SOFTWARE\Policies\GlueckKanja\Konnekt`

`HKEY_LOCAL_MACHINE\SOFTWARE\Policies\GlueckKanja\Konnekt`