> 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/configuring-collector-for-endpoint-devices.md).

# Configuring Collector for endpoint devices

Configure Collector with your customer-specific data and settings to ensure a connection to your Nexthink instance. You can create multiple Collector configurations with different settings for different device groups.

Select the correct installer file type as described in [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), then follow the procedure in the relevant section below.

* [Nexthink Collector Installer](#nexthink-collector-installer)
* [Windows Installer](#windows-installer)

## Nexthink Collector Installer

The Nexthink Collector Installer is a graphical tool that produces a standalone executable for deployment.

{% stepper %}
{% step %}

### Launch the installer

Double-click the Nexthink Collector Installer executable. The tool generates either:

* A silent installer: `Nexthink_Collector_Installer_Silent.exe`
* A verbose installer that opens a command-line window: `Nexthink_Collector_Installer.exe`
  {% endstep %}

{% step %}

#### Configure Nexthink Appliance settings

Under **Nexthink Appliance settings**, specify the Nexthink instance settings:

<table><thead><tr><th width="172.2222900390625">Setting</th><th>Description</th></tr></thead><tbody><tr><td><strong>Address</strong></td><td>The URL of your Nexthink instance.</td></tr><tr><td><strong>Data over TCP</strong></td><td>Select this option to send data over a TCP channel.</td></tr><tr><td><strong>Ports (TCP)</strong></td><td><code>443</code></td></tr><tr><td><strong>Ports (UDP)</strong></td><td>Do not select this when using the Nexthink cloud platform.</td></tr><tr><td><strong>DNS</strong></td><td>If needed, select <strong>Prefer IPv6</strong> to have Collector favor IPv6 over IPv4 when communicating with the instance.</td></tr></tbody></table>
{% endstep %}

{% step %}

#### Configure General settings

Under **General settings**, configure the following options as needed:

* **Installation options**: Settings not shown in the dialog take their default value. Select **Install configuration tool** to modify these later using the [Collector configuration tool](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/windows-collector-references/collector-configuration-tool-for-windows.md). During an update, the system preserves values of non-visible settings from the previous installation.
* **Web and Cloud Data**: Select this if you have purchased the Web and Cloud product. Select **Settings** to [specify the domains](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/windows-collector-references/reporting-the-url-of-http-web-requests-classic.md) for which Collector stores full URL paths of web requests.
* **Use the assignment service**: Select this if you have activated rule-based assignment of Collectors.
* **Engage activation**: Select the behavior for launching campaigns on the target devices:
  * **Enable except on servers**: Collector launches campaigns on devices that do not run a server operating system.
  * **Enable on all devices**: Collector launches campaigns on all devices.
  * **Disable**: Collector ignores campaigns.
* **Script execution policy**: Select the policy for remote actions:
  * **Signed by a trusted publisher or by Nexthink** (default): Collector runs remote actions with PowerShell scripts signed by Nexthink or by a company in the Trusted Publishers certificate store.
  * **Signed by a trusted publisher**: Collector runs only remote actions with PowerShell scripts signed by a company in the Trusted Publishers certificate store.
  * **Disabled**: Collector does not run remote actions.
  * **Unrestricted**: Collector runs any remote action, regardless of the script digital signature.
* **Collector tag** (optional): An integer (0–2,147,483,647) that identifies a group of Collectors; useful for defining entities in hierarchies.
* **Collector string tag** (optional): A label (maximum 2,048 characters) that identifies a group of Collectors; useful for defining entities in hierarchies.
* **Customer Key file**: Your Customer Key file, provided by Nexthink, that protects the connection to the Nexthink instance.
* **Output directory**: Select **Browse** to choose the folder where the installer and uninstaller executables are created.
* **Logs directory** (optional): The network location where Collector saves installation logs.
  {% endstep %}

{% step %}

#### Configure proxy settings (optional)

If applicable, configure [proxy settings](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/windows-collector-references/windows-collector-proxy-support.md) under **Proxy configuration**:

* **Automatic proxy**: Type the URL of the PAC file in the **PAC address** field.
* **Manual proxy**: Type the proxy port number in the **Proxy port** field.
  {% endstep %}

{% step %}

#### Generate the installer files

Select **Create** to generate the following files:

* `NEXThink_Collector<Nexthink_Experience_FQDN>.exe`: Installer executable.
* `NEXThink_Collector_Uninstaller<Nexthink_Experience_FQDN>.exe`: Uninstaller executable.
* `NEXThink_Collector<Nexthink_Experience_FQDN>.exe.txt`: Text file listing the settings used.

Select **OK** to close the dialog.
{% endstep %}
{% endstepper %}

<details>

<summary>Installer exit codes</summary>

The installer generates one of the following exit codes:

| Exit code | Description                                                                                                                        |
| --------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| `0`       | Success; reboot is not required.                                                                                                   |
| `-1`      | Success; reboot is required.                                                                                                       |
| `3`       | Failure; the installation started but failed (`msiexec`).                                                                          |
| Other     | Failure; the value corresponds to a [Windows internal error code](https://docs.microsoft.com/en-us/windows/win32/msi/error-codes). |

</details>

<details>

<summary>Uninstaller exit codes</summary>

The uninstaller generates one of the following exit codes:

| Exit code | Description                                                                                                                        |
| --------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| `0`       | Success; reboot is not required.                                                                                                   |
| `-1`      | Success; reboot is required.                                                                                                       |
| `1`       | Success; Collector was not found and nothing was uninstalled.                                                                      |
| `3`       | Failure; the uninstallation started but failed (`msiexec`).                                                                        |
| Other     | Failure; the value corresponds to a [Windows internal error code](https://docs.microsoft.com/en-us/windows/win32/msi/error-codes). |

</details>

## Windows Installer

The Windows Installer (MSI) method requires an MST (transform) file for configuration. Use an MSI editor, for example, Orca, to create the MST file.

Refer to the documentation of your MSI editor.

### Create the MST file

For the complete list of installation parameters, refer to the [Collector MSI parameters reference table](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/windows-collector-references/collector-msi-parameters-reference-table.md).

The following parameters are mandatory:

<table><thead><tr><th width="227.22216796875">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><code>DRV_IP</code></td><td>The URL of your Nexthink instance. URL pattern: <code>&#x3C;customer_name>.data.eu.nexthink.cloud</code></td></tr><tr><td><code>CRD_PORT</code></td><td><code>443</code></td></tr><tr><td><code>CRD_KEY</code></td><td>Your Customer Key file provided by Nexthink. Open the key file in a text editor, copy the entire text, and paste it as the property value.</td></tr><tr><td><code>DATA_OVER_TCP</code></td><td>Enable to send end-user data over the TCP channel.</td></tr></tbody></table>

### VDI Client Extension

When installing Collector version 25.4.1 or higher, the VDI Client Extension is enabled automatically for all devices in your environment when using VDI Experience. For older Collector versions, Nexthink recommends upgrading to the most recent version.


---

# 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/configuring-collector-for-endpoint-devices.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.