> 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-and-deploying-collector-for-vms.md).

# Configuring and deploying Collector for VMs

This page covers the Nexthink Collector deployment process on VMs, including configuration, auto-update management for non-persistent environments, deployment, and verification.

{% hint style="info" %}
Before continuing with this procedure, ensure that:

* You have completed the general prerequisites described in the [Installing Collector on Windows](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/installing-collector-on-windows.md#before-you-begin) documentation.
* You have configured the required VDI Platform Connector for your virtualization platform to enable the ingestion of session metadata required by the VDI Experience module. Refer to [VDI platform-specific deployment scenarios](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-vdi-environment/vdi-platform-specific-deployment-scenarios.md).
  {% endhint %}

{% stepper %}
{% step %}

### Configure Collector for VMs

Configure Collector with the MSI parameters using the Windows Installer. Refer to the following pages for details:

* [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)
* [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)
* [Configuring Collector-level anonymization](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/configuring-collector-level-anonymization.md)

Then add the VM-specific optional parameters to the MST file as described below.

#### VM-specific optional parameters

Use the following parameters to control VDI platform detection and client latency collection on Windows-based VMs. Apply them in the MST file during installation or in the Windows registry after deployment.

{% tabs %}
{% tab title="Windows Installer (MST)" %}

| Parameter                        | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
| -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `VDI_PLATFORM_TYPE`              | <p>Forces detection of a specific VDI platform when multiple agents are present on a VM. Values:</p><ul><li><code>Auto</code>: Default; uses agent registry keys when available</li><li><code>AVD</code>: Forces Azure Virtual Desktop detection; prevents Windows 365 detection</li><li><code>AWS</code>: Forces AWS detection</li><li><code>Citrix</code>: Forces Citrix detection</li><li><code>Horizon</code>: Forces Horizon detection</li><li><code>Windows365</code>: Forces Windows 365/CloudPC detection</li><li>Missing or unknown value defaults to auto detection</li></ul> |
| `VDI_CLIENT_PLUGIN_PING_ADDRESS` | Sets the host to ping from the client to calculate ISP and WAN latency. The system pushes this information from the VM to the client. Populated NQL data model field: `client.network.wan_latency`                                                                                                                                                                                                                                                                                                                                                                                      |
| {% endtab %}                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |

{% tab title="Windows registry" %}

<table><thead><tr><th width="193.55560302734375">Key name</th><th>Description</th></tr></thead><tbody><tr><td><code>Platform</code></td><td><p>Controls the VDI platform type Collector detects or forces. Location: <code>HKEY_LOCAL_MACHINE\SOFTWARE\Nexthink\Collector\VDI</code>. Values:</p><ul><li><code>Auto</code></li><li><code>AVD</code></li><li><code>AWS</code></li><li><code>Citrix</code></li><li><code>Disabled</code></li><li><code>Horizon</code></li><li><code>Windows365</code></li></ul><p>Default (if not set): <code>Disabled</code>.</p></td></tr><tr><td><code>ClientPingAddress</code></td><td><p>Sets the IP address used by the connected plugin to calculate ISP and WAN latency.</p><p>Location: <code>HKEY_LOCAL_MACHINE\SOFTWARE\Nexthink\Collector\Sessions</code></p><p>Accepts any string</p><p>Examples: IPv4 <code>x.y.z.a</code>, IPv6 <code>::1</code>, domain <code>domain.com</code>.</p></td></tr></tbody></table>
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}

### Prevent automatic updates for non-persistent and pooled VDIs

Non-persistent and pooled virtual desktops are typically created from golden images and reset after each session. To prevent these devices from switching between Collector versions, navigate to **Administration > Collector management > Update configuration** and select **Do not update shared and pooled VDI devices**.

Refer to [Collector management](/platform/user-guide/administration/system-configuration/collector-management.md) for more information.
{% endstep %}

{% step %}

### Prepare a Windows reference image (pooled and shared VDIs only)

When including Collector in a Windows reference image, remove the UID that Collector may have generated to identify the device. Refer to [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#installingcollectoronwindows-deployingcollectorwithinawindowsreferenceimage) for more information.
{% endstep %}

{% step %}

### Deploy Collector on VMs

Deploy Nexthink Collector on all VMs in your virtual infrastructure using the applicable deployment method. Refer to [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) for deployment instructions using Active Directory Group Policy or Microsoft Configuration Manager.
{% endstep %}

{% step %}

### Verify the deployment

After deployment, verify that your tenant is receiving VDI metrics.

{% hint style="info" %}
Before verification, ensure that you have configured the required VDI Platform Connector for your virtualization platform.
{% endhint %}

* Navigate to **Investigations** to query the new tables and verify the installation. Refer to [VDI Experience NQL capabilities](/platform/user-guide/vdi-experience/desktop-virtualization-nql-capabilities.md).
* Verify that session data is available in the **Desktop Virtualization** dashboards.
  {% endstep %}
  {% endstepper %}


---

# 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-and-deploying-collector-for-vms.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.