> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-vdi-environment/installing-the-nexthink-vdi-client-extension.md).

# Installing Nexthink VDI Client Extension

Nexthink VDI Client Extension is a lightweight agent for personal employee devices and self-managed endpoint devices connected to virtual desktop environments (VDIs). The extension sends only relevant data to the Nexthink instance from devices on which Nexthink Collector cannot be installed.

{% hint style="info" %}
[Nexthink VDI Client Extension](#download-the-extension) is included as a component in Nexthink Collector; therefore you do not need to install it separately on company-managed devices accessing virtual environments.

For **company-managed devices**, see the [Installing Collector](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector.md) documentation to learn how to install Collector.
{% endhint %}

### Platform compatibility

Nexthink VDI Client Extension supports the following platforms:

* Citrix
* Microsoft Azure Virtual Desktop (AVD)
* Windows 365 Cloud PC (CPC)

It can only be installed on endpoints running Microsoft Windows.

The extension does not support the following platforms:

* Amazon Web Services (AWS)
* Omnissa Horizon (formerly known as VMware Horizon)

## Before you begin

Download the VDI Client Extension MSI file directly from Nexthink on the [Collector management](/platform/user-guide/administration/system-configuration/collector-management.md) dashboard under **Administration > Collector management > Downloads**.

## Installation procedure

{% stepper %}
{% step %}

### Install the extension

Choose between the following installation methods:

{% tabs %}
{% tab title="Manual installation" %}
This method highlights all steps during the process.

Run the MSI file like any other executable to launch the VDI Client Extension installer, and follow the steps. This starts the installation process with Windows Installer.
{% endtab %}

{% tab title="Silent installation" %}
This method runs the installation without user intervention.

Run the following command in a command-line interface (CLI) to install the extension without user interactions; replace `<VERSION>` with the version of the extension:

```powershell
msiexec /i NEXThink_VDI_Client_Extension_<VERSION>.x86_64.msi /qn
```

{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}

### Connect to a VDI session

Once the installation is complete, you are ready to reconnect to your VDI session, and Nexthink can start complementing the remote session information with relevant metrics from the client device.
{% endstep %}
{% endstepper %}

## FAQ

See the [VDI Experience FAQ](/platform/user-guide/vdi-experience/vdi-experience-faq.md) to find answers to common questions regarding, for example, deployment scenarios.


---

# 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.nexthink.com/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-vdi-environment/installing-the-nexthink-vdi-client-extension.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.