> 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-non-vdi-environment/installing-collector/installing-collector-on-windows.md).

# Installing Collector on Windows

This page describes the Collector installation and deployment process for Windows devices. The process covers three scenarios:

* Small-scale or proof-of-concept setups
* Medium to large-scale deployments on physical devices
* Deployments on VMs.

{% hint style="info" %}
Refer to [Installing Collector](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector.md) to identify the deployment path applicable to your infrastructure before starting.
{% endhint %}

## Before you begin

Ensure you have the following before starting:

* One or more Windows devices on which to install Collector.
* The URL of your Nexthink instance, including `data` in the path. Refer to [Connectivity requirements](/platform/configuring_nexthink/before-you-begin/technical-requirements/connectivity-requirements.md) for more information.
  * Example: `<instance>.data.<region>.nexthink.cloud`
* The customer key from the `Customer Key.txt` file received in your welcome email from Nexthink.
* The root certificate associated with your Nexthink instance.
* Administrator credentials in your Nexthink instance.
* Optional: A third-party deployment tool or Unified Endpoint Manager (UEM), for example, Microsoft Intune.
* Optional: An MSI editor, for example, Orca, when using the Windows Installer (MSI).

{% hint style="warning" %}
Ensure that no version of Nexthink Collector is running on the Windows device before starting. If Collector is already running, uninstall it before continuing.
{% endhint %}

{% hint style="warning" %}
Starting with Collector version 25.4.1, the **VDI Client Extension** is enabled automatically for all devices using VDI Experience. For older versions, Nexthink recommends upgrading to the most recent Collector version to ensure automatic enablement without redeployment.
{% endhint %}

## Installation flow

The following diagram shows the installation and deployment paths for all Windows scenarios. All paths share the same prerequisites.

```mermaid
%%{ init : { "theme" : "default", "flowchart" : { "curve" : "linear" }}}%%
flowchart TD
    Pre(["✅ Prerequisites met"]) --> Obt["📥 Obtain Collector"]
    Obt --> C{"Deployment<br/>scenario?"}
    C --> P["💻 Physical devices"]
    C --> V["🖥️ VMs"]

    P --> S["Small-scale or PoV"]
    S --> S1["⚙️ Configure Collector"]
    S1 --> S2["🖥️ Install on single device<br/>and verify"]
    S2 --> S3["🖥️ Install on remaining devices"]

    P --> P0["Medium or large-scale"]
    P0 --> P1["⚙️ Configure Collector"]
    P1 --> P2["🖥️ Install on single device<br/>and verify"]
    P2 --> P3["🚀 Deploy to all devices<br/>with GPO or ConfigMgr"]

    V --> V1["⚙️ Configure Collector<br/>with VM parameters"]
    V1 --> V2["🔌 Install virtualization connector"]
    V2 --> V3{"Non-persistent<br/>VDI?"}
    V3 -->|Yes| V4["Disable auto-updates"]
    V3 -->|No| V5["🚀 Deploy on all VMs"]
    V4 --> V5
    V5 --> V6["✔️ Verify deployment"]

    classDef start fill:#EEF3F7,stroke:#1046A8,color:#221F20;
    classDef decision fill:#0B1441,stroke:#0B1441,color:#FFFFFF;
    classDef path fill:#1046A8,stroke:#0B1441,color:#FFFFFF;
    classDef process fill:#3194F7,stroke:#1046A8,color:#FFFFFF;
    classDef verify fill:#00B1A9,stroke:#00B1A9,color:#FFFFFF;

    class Pre start;
    class C,V3 decision;
    class P,V,S,P0 path;
    class Obt,S1,S2,S3,P1,P2,P3,V1,V2,V4,V5 process;
    class V6 verify;
```

## Deployment steps

Follow the procedures in these sections in order:

1. [Obtaining Collector](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/installing-collector-on-windows/obtaining-collector.md)
2. For physical device deployments:
   1. [Configuring Collector for endpoint devices](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/installing-collector-on-windows/configuring-collector-for-endpoint-devices.md)
   2. [Installing Collector on a single device](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/installing-collector-on-windows/installing-collector-on-a-single-device.md)
   3. [Deploying Collector on Windows](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/installing-collector-on-windows/deploying-collector-on-windows-tp.md)
3. For VM deployments: [Configuring and deploying Collector for VMs](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/installing-collector-on-windows/configuring-and-deploying-collector-for-vms.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nexthink.com/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/installing-collector-on-windows.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.