Support

Configuring VDI Experience

Overview

To successfully deploy VDI Experience, you must install and configure several components across various nodes of your virtual infrastructure. These components include:

  • Inbound connectors: Integration components that allow external systems to send data to the Nexthink platform. Their purpose is to enrich the existing data collected by Nexthink by bringing in additional context, typically from third-party tools or enterprise systems.

  • Collector: An agent that provides the full range of VDI metrics, giving you everything from virtual infrastructure insights, to comprehensive information about your Nexthink instance. This agent is intended for company-managed client devices and VMs, which enables comprehensive visibility into user experience.

  • VDI Client Extension: A lightweight agent that offers a limited set of metrics. It is designed for personal or self-managed employee devices where full Collector installation is not feasible.

The following figure shows a simplified representation of typical on-premises and cloud-hosted VDI infrastructures, highlighting which components to install on each node.

The numbers indicate the order in which you should install components on nodes in your virtual infrastructure. Nexthink recommends following this sequence for a smooth and consistent setup, and to ensure that data is sent correctly from each node to the next.

The connection lines show the path of metrics collected in the vdi_session and vdi_event tables, specific to VDI Experience. To learn about these metrics, refer to the VDI Experience NQL capabilities and NQL data model documents.

Example of an on-prem hosted VDI
Example of a cloud-hosted VDI

Depending on what components you install, the system will collect different metrics. To learn what metrics are provided by each installation scenario, refer to the VDI Experience NQL capabilities documentation.

Deployment scenarios

To understand how to install and configure components for your specific virtual infrastructure, continue with reading the topic that is applicable to your VDI platform:

Last updated

Was this helpful?