Configuring Collector for VMs

Perform the following steps to configure Collector for VMs:

1

Configure Collector with your customer-specific data and settings using the Windows Installer

2

See and, if necessary, add the Configuring Collector for VMs to the MST file

3

Proceed by reading the VM-specific considerations

4

Install Collector on VMs

5

Verify the installation and VDI metrics

VM-specific optional parameters

Windows installer (MST)

Parameter	Description
VDI_PLATFORM_TYPE	Force the detection of Citrix or Azure Virtual Desktop (AVD) / Cloud PC (CPC) if there are multiple agents in a given VM. Values: Auto: Auto detection using agent registry keys when available AVD: Forces AVD detection; prevents Windows365 detection AWS: Forces AWS detection Citrix: Forces Citrix detection Horizon: Forces Horizon detection Windows365: Forces Windows 365 / CloudPC detection Missing or unknown value: Auto detection using agent registry keys when available
VDI_CLIENT_PLUGIN_PING_ADDRESS	Set the host to ping from the client to calculate ISP and WAN latency. This information is pushed from the VM to the client. Populated NQL data model field: client.network.wan_latency

Windows registry

Key name	Description
Platform	Controls the VDI platform type that the Collector detects or forces to use. Location: HKEY_LOCAL_MACHINE\SOFTWARE\Nexthink\Collector\VDI Possible values: Auto: Auto detection using agent registry keys when available AVD: Forces AVD detection; prevents Windows365 detection AWS: Forces AWS detection Citrix: Forces Citrix detection Disabled: Detection disabled Horizon: Forces Horizon detection Windows365: Forces Windows 365 / CloudPC detection If not set, the default value is Disabled. Missing or unknown value: Auto detection using agent registry keys when available.
ClientPingAddress	Selects which IP address will be used by the connected plugin to calculate ISP and WAN latency. Location: HKEY_LOCAL_MACHINE\SOFTWARE\Nexthink\Collector\Sessions Any string is a valid value. Examples: IPv4: x.y.z.a IPv6: ::1 Domain: domain.com

Considerations

Connectors

Install the appropriate virtualization connector for your environment to complement the data that comes from VMs and VDI clients. See the following documentation for installation instructions:

• AWS AppStream connector

• AWS WorkSpaces connector

• Citrix Virtual Apps and Desktops connector

• Citrix DaaS connector

• Microsoft Azure Virtual Desktop connector

• Omnissa Horizon connector

Collector automatically detects your VDI vendor. However, you can optionally override this setting.

Preventing automatic updates for non-persistent and pooled VDIs

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

Refer to the Collector management documentation for more information on Collector management.