Deploying Nexthink in VDI environment
This page provides an overview of how to deploy and configure Nexthink in a virtual desktop infrastructure (VDI) environment.
VDI environments introduce specific technical considerations when deploying endpoint agents and capturing user session data. As such, some steps in this guide focus on integrating your VDI environment with Nexthink, while others outline general configuration tasks applicable to all Nexthink deployments.
Refer to Deploying Nexthink in VDI environment on this page to get an overview of VDI-specific deployment path.
Refer to Step-by-step deployment procedure on this page that includes both VDI-specific and general Nexthink configuration tasks.
Understanding VDI infrastructure components
The following figure shows a simplified representation of typical on-premises and cloud-hosted VDI infrastructures, highlighting which components to install on each node.
Determining your VDI Deployment path
The chart below outlines the available VDI deployment paths based on your desktop broker, desktop type, and the method used to deploy Nexthink Collector on virtual machines.
*For Microsoft Remote Desktop Session Host (RDSH) and other desktop brokers not outlined in this chart, Nexthink recommends using features available in the basic Nexthink license, such as Desktop virtualization (classic) in the Alerts and Diagnostics module.
Step-by-step deployment procedure
This section describes the high-level sequence for installing and configuring Nexthink components in a VDI environment, including VDI-specific and general Nexthink configuration tasks.
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.
For more detailed guidelines specific to your VDI platform, refer to one of the following deployment scenarios outline in the VDI platform-specific deployment scenarios documentation.
Set up the VDI Platform-specific inbound connector
Install the appropriate Inbound connector for your VDI Platform, when applicable:
Configure Collector for Virtual Machines (VMs)
If needed use Nexthink Collector Installer (MST) to include VM-specific MST parameters
The VDI Client Extension component of Collector is included by default.
Deploy Collector on Virtual Machines (VMs)
The method for Collector deployment on VMs depends on the type of desktop:
Persistent desktops: Deploy Collector with UEM or VDI platform-specific tool.
Non-persistent desktops: Prepare golden image and deploy Collector with your VDI platform-specific tool.
Shared desktops: Deploy Collector with VDI platform-specific tool.
Once both Connector and Collector on VMs are set, use the Investigations module to verify if related VDI data is available in Nexthink.
Configure Collector for client devices
Configure Collector using Nexthink Collector Installer (MST) or Windows Installer.
The VDI Client Extension component of Collector is included by default.
Deploy endpoint agents on client devices
Deploy Nexthink Collector on employee devices using your preferred method (UEM, MECM, GPO)
Optionally, deploy VDI Client Extension on private or unmanaged devices where you cannot install Collector.
Once Collector and VDI Client Extension are deployed, use the Investigations module to verify if related VDI client data are available in Nexthink.
Deploy browser extensions on client devices
Deploy the Nexthink browser extension on employee devices.
If you have purchased Amplify, deploy the Amplify browser extension:
Configure other inbound connectors according to your IT infrastructure and Nexthink license
Configure other Inbound connectors, such as Microsoft Entra ID or Salesforce, to enrich data from endpoint agents and browser extensions with additional context from external vendors.
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?