Microsoft Windows 365

Microsoft Windows 365 is a fully cloud-based service that runs entirely in Azure. Virtual desktops are provisioned and managed in the cloud, allowing organizations to centralize control without maintaining on-premises infrastructure. It is commonly used by enterprises that want to simplify desktop management, support remote work, and scale resources quickly while reducing reliance on traditional data centers.

You do not need to install an inbound connector for Microsoft Windows 365.

1

Install Collector on VMs

Install Collector as a standard agent during provisioning or onboarding of the persistent desktop.

Perform the procedures described in the following documentations:

1. Configuring Collector for VMs

2. Installing Collector on VMs

3. Deploying Collector

2

Test Collector on VMs

If needed, contact Nexthink support or your Nexthink representative.

Verify consistent reporting of Device ID, Assigned User and system uptime across Reboots and Logons.

To do this, run the following query in the Investigations module:

Verify the consistent reporting of the following:

• Device ID and Assigned User

• System uptime across Reboots and Logons

To check this, run the following query:

devices
| where virtualization.desktop_broker == windows_365 and virtualization.type == personal
| with session.vdi_events during past 168h
| compute number_of_sessions = vdi_session.count(), time_since_session_last_seen = end_time.last().time_elapsed(), last_user = user.name.last()
| include device_performance.boots during past 168h
| compute number_of_restarts = number_of_boots.sum()
| include session.logins during past 168h
| compute time_since_last_login = time.last().time_elapsed(), number_of_logons = number_of_logins.sum()
| list name, last_user, number_of_sessions, time_since_session_last_seen, number_of_logons, time_since_last_login, number_of_restarts, boot.last_full_boot_time.time_elapsed(), last_seen.time_elapsed()
| sort time_since_session_last_seen desc

For more information about running queries, see the Investigations documentation.

3

Install endpoint agents on client devices

Install Collectors on corporate-managed devices

For client devices that are centrally managed by your organization, distribute Collector across all applicable devices using your preferred software deployment tools.

Perform the procedure described in the Installing Collector documentation.

The VDI Client Extension is built into Collector; you do not need to install it separately.

Install VDI Extension on personal or self-managed devices

For personal or self-managed client devices, make VDI Client Extension available for installation. This lightweight agent provides limited yet valuable client-side metrics without requiring full Collector deployment.

Perform the procedure described in the Installing Nexthink VDI Client Extension documentation.

4

Test client devices

Corporate-managed devices

For sessions launched from managed client devices, confirm visibility into fields such as:

• Round-Trip Time

• Client CPU usage

• Wi-Fi Signal Strength

• Link Speed

While the network RTT is available even if Collector is installed only on the VM, full client performance information requires Collector to be installed on the endpoint. To validate the installation, check that client metrics are reported for the sessions.

If the client device is running Collector and reporting data to your Nexthink instance, its name appears as a link to the Device View, where you can access detailed information and activity.

To check this, run the following query:

vdi_sessions
| with session.vdi_events during past 168h
| compute average_network_rtt = network_rtt.avg(), average_wifi_signal_strength = client.network.wifi_signal_strength.avg(), average_link_speed = client.network.wired_link_speed.avg(), average_client_cpu_usage = client.cpu.normalized_usage.avg(), last_client_plugin_version = client.plugin_version.last()
| list vdi_session.name, device.name, user.name, name, last_client.device.name, last_client_plugin_version, average_network_rtt, average_wifi_signal_strength, average_link_speed, average_client_cpu_usage
| sort last_seen desc

Partner-managed or bring your own devices

For sessions launched from externally-managed client devices, confirm visibility into fields such as:

• Round-Trip Time

• Wi-Fi Signal Strength

• Link Speed

While the network RTT is available even if the Collector is installed only on the VM, full network performance information requires either Collector or VDI Client Extension to be installed on the client device. To validate the installation, check that networking metrics are reported for the sessions.

If VDI Client Extension is installed, no additional device data is captured, and therefore, no Device View is available for the client device. In this case, client-related performance information is reported only within the VDI sessions.

To check this, run the following query:

vdi_sessions
| with session.vdi_events during past 168h
| compute average_network_rtt = network_rtt.avg(), average_wifi_signal_strength = client.network.wifi_signal_strength.avg(), average_link_speed = client.network.wired_link_speed.avg(), average_client_cpu_usage = client.cpu.normalized_usage.avg(), last_client_plugin_version = client.plugin_version.last()
| list vdi_session.name, device.name, user.name, name, last_client.device.name, last_client_plugin_version, average_network_rtt, average_wifi_signal_strength, average_link_speed, average_client_cpu_usage
| sort last_seen desc