> For the complete documentation index, see [llms.txt](https://docs.konnekt.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konnekt.io/installation.md).

# Deployment

This section takes IT admins from download to working drive letters: grant consent, install the MSI, push policies, and let users sign in. Each step links to the page with the full detail.

## Before you start

* Local administrator rights on the target devices
* An administrator who can grant tenant-wide admin consent in Microsoft Entra ID
* A KONNEKT license key. Without one, KONNEKT installs as an evaluation version
* A decision on how you deliver policies: Group Policy, Microsoft Intune, or the registry

Check the [System requirements](https://docs.konnekt.io/installation/system-requirements.md) first.

## Step 1: Grant admin consent

An administrator approves KONNEKT for the tenant once, before the first user signs in. KONNEKT uses delegated permissions only, so it never acts without a signed-in user. For the consent URL and the permission set, see [Grant tenant-wide admin consent](https://docs.konnekt.io/installation/security/grant-admin-consent-in-enterprise-applications.md).

## Step 2: Install the MSI

KONNEKT ships as one MSI per processor platform: x64, x86 and ARM64. On ARM64 devices, use the ARM64 package.

Distribute the MSI through Microsoft Intune as a Win32 app, or through your software distribution. The silent install command is:

```
msiexec /i konnekt.msi /quiet /qn /norestart LICENSE_KEY=<your-license-key>
```

{% hint style="warning" %}
KONNEKT installs a kernel-mode driver, so the device needs a restart before KONNEKT works. Restart, don't shut down: with Fast Startup enabled, a shutdown can leave the driver update unfinished.
{% endhint %}

For the interactive installer, see [Setup](https://docs.konnekt.io/installation/setup.md).

## Step 3: Push policies

Every KONNEKT policy exists for computers and for users. Computer policies win over user policies. Group Policy and Microsoft Intune use the same ADMX template, so the policies, their names and their options are identical in both.

| Channel          | How                                                                                                                                                                                                                      |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Group Policy     | Copy `Konnekt.admx` and `en-US\Konnekt.adml` into your PolicyDefinitions store. See [Settings via GPO](https://docs.konnekt.io/configuration/management-options/settings-via-gpo.md)                                     |
| Microsoft Intune | Import `Konnekt.admx` and `Konnekt.adml` as imported administrative templates. See [Settings for Intune-managed devices](https://docs.konnekt.io/configuration/management-options/setting-for-intune-managed-devices.md) |

For every setting and its registry value, see [Management options](https://docs.konnekt.io/configuration/management-options.md).

### Fallback: OMA-URI and registry

Use these only where the ADMX template can't be used:

* **Custom OMA-URI profiles in Intune**, for tenants that don't use imported administrative templates. See [Settings for Intune-managed devices (Legacy)](https://docs.konnekt.io/configuration/management-options/setting-for-intune-managed-devices-1.md).
* **Registry values written by a script**, for Windows multi-session hosts and for the few settings that have no ADMX policy. See [Deploy on session hosts and VDI](https://docs.konnekt.io/installation/deploy-on-session-hosts-and-vdi.md).

## Step 4: Users sign in

On Microsoft Entra joined devices, KONNEKT creates the first account from the Windows sign-in, silently where single sign-on allows it. Site discovery then takes one to three minutes, after which the drives appear.

To have users sign in themselves instead, see [Skip Account Wizard](https://docs.konnekt.io/configuration/system-settings/configure-konnekt-for-a-subset-of-users.md).

## In this section

{% content-ref url="/pages/-Manse1cD2s5Q0BfoS8Z" %}
[System requirements](https://docs.konnekt.io/installation/system-requirements.md)
{% endcontent-ref %}

{% content-ref url="/pages/-Manwi3yO7f-RwKgSMwV" %}
[Setup](https://docs.konnekt.io/installation/setup.md)
{% endcontent-ref %}

{% content-ref url="/pages/-Mao0rXuKpa0DTlVbn4P" %}
[Configure Office 365 account](https://docs.konnekt.io/installation/configure-office-365-account.md)
{% endcontent-ref %}

{% content-ref url="/pages/MFYRiuLFvSVi3Xxswvjd" %}
[Deploy on session hosts and VDI](https://docs.konnekt.io/installation/deploy-on-session-hosts-and-vdi.md)
{% endcontent-ref %}

{% content-ref url="/pages/-ManuC3REI\_Mq\_n9RNhI" %}
[Software updates](https://docs.konnekt.io/installation/software-updates.md)
{% endcontent-ref %}

## Related pages

* [Security](https://docs.konnekt.io/installation/security.md)
* [Management options](https://docs.konnekt.io/configuration/management-options.md)
* [Managed mappings](https://docs.konnekt.io/configuration/mappings/managed-mappings.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.konnekt.io/installation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
