Configuration guide: Windows 365 essentials

The configuration opions on this page are only accessible to administrators.

Refer to the Usage guide: Windows 365 essentials to use library content as a standard user.

Prerequisites

This library pack contains content from the following required expansion products:

• Nexthink VDI Experience.

Some of these products offer default access to their respective content and can still be used without expansion products.

Refer to the Nexthink Infinity thresholds and limits overview documentation for more information about default thresholds for expansion products.

Included content and dependencies

Some content in this pack is shared across Windows 365 and Azure Virtual Desktop (AVD). Shared objects may use AVD or VDI terminology in their installed names. These names should be kept as installed; the descriptions below explain how the objects apply to Windows 365 Cloud PCs.

Content type	Name	Description
Dashboards	Windows 365 monitoring	Monitor the health and availability of Windows 365 Cloud PCs by identifying performance issues, stale devices, agent registration issues, and reboot health indicators that impact user experience.
Applications	Microsoft AVD	A shared network application object that provides visibility into connectivity and network usage for Windows 365 Cloud PCs and Azure Virtual Desktop traffic.
Applications	Microsoft AVD client	A shared hybrid web and desktop application object that provides visibility into usage, performance, and stability of the client used to connect to Windows 365 Cloud PCs and Azure Virtual Desktop environments.
Monitors	High percentage of disconnected sessions per desktop pool	Identifies frequent or unexpected drops.
Monitors	High CPU usage per desktop pool	Flags potential performance bottlenecks.
Monitors	High average latency per VDI client location	Highlights network-related delays by region.
Monitors	High number of sessions per virtual machine	Prevents resource overutilization.
Remote actions	Invoke restart of session host	Restarts the host machine. For Windows 365, this restarts the Cloud PC. In shared or multi-session VDI environments, this can affect all user sessions on the host.
Remote actions	Invoke update GPO computer policy	Refreshes Group Policy settings on the host machine by executing the gpupdate command at the system level.
Remote actions	Invoke update GPO user policy	Triggers a user-level Group Policy refresh for the currently logged-in user using the command gpupdate /target:user /force.
Remote actions	Invoke end process	Can be used to terminate a process which is running within a user session on a Windows device.
Remote actions	Log off VDI session	Logs off an active VDI session. For Windows 365, this logs off the user's Cloud PC session.
Remote actions	Get Azure Virtual Desktop information	Retrieves VDI agent and Azure resource information used by the shared VDI content, including agent registration status, Azure resource identifier, top-level resource group, and desktop group or pool information. This action is scheduled for devices where the desktop broker is Azure Virtual Desktop or Windows 365.
Custom fields	AVD reboot health	Indicates the reboot health of a device based on the 'Days since last reboot'

Configuring Windows 365 essentials

Adapt these suggested configuration steps to edit and customize content according to your organizational needs.

Follow these steps to install and configure content:

• Before configuration - Install library pack content from Nexthink Library
• Step 1 - Configure remote actions
• Step 2 - Configure monitors
• Step 3 - Configure custom fields

Step 1 - Configure remote actions

1. From the main menu, navigate to the Remote Actions > Manage remote action page.
2. Review and edit your remote actions.

Nexthink recommends the following configurations for these remote actions:

Name	Trigger Schedule	Parameters to edit
Invoke restart of session host	Triggered on demand to resolve issues
Invoke update GPO computer policy	Triggered on demand to resolve issues
Invoke update GPO user policy	Triggered on demand to resolve issues
Invoke end process	Triggered on demand to resolve issues
Log off VDI session	Triggered on demand to resolve issues
Get Azure Virtual Desktop information	Scheduled locally on Windows 365 Cloud PCs and Azure Virtual Desktop session hosts	Device identification for schedule: devices | where virtualization.desktop_broker in [ azure_virtual_desktop, windows_365 ]

Step 2 - Configure monitors

To install and (partially) configure content:

1. From the main menu, navigate to the Alerts & Diagnostics > Manage alerts page.
2. Review and edit your monitors.
3. For each monitor:

   • The Scheduling frequency cannot be modified, like many other configuration fields.
   • If required, set additional Trigger conditions and refine the VDI monitor thresholds within the monitor configuration page. Refer to the table below.
   • Additionally, customize Filters, Priority, and Notifications for each VDI monitor.

Name	Scheduling Frequency	Trigger conditions to edit
High average latency per VDI client location	Real time	Average network latency (Default - moderate increase) Percentage of events with high latency (Default >= 20%)
High CPU usage per desktop pool	Real time	Average CPU queue length (Default - moderate increase) Percentage high queue length (Default >= 20%)
High number of sessions per virtual machine	Scheduled, 15 minutes	Sessions per virtual machine (Default >= 20)
High percentage of disconnected sessions per desktop pool	Scheduled, 15 minutes	Percentage of disconnected sessions (Default >= 40%)

Step 3 - Configure custom fields

1. From the main menu, navigate to the Administration > Custom fields page.
2. Check and customize the rule criteria for each custom field.
3. Edit the NQL queries if necessary to suit your environment and reboot policies.
4. Nexthink recommends the following settings:

Name	NQL ID	Rule name	Object	NQL query
AVD reboot health	avd_reboot_health	Good Average Poor	device	devices | where virtualization.desktop_broker in [ azure_virtual_desktop, windows_365 ] and ((virtualization.type in [shared, pooled] and boot.days_since_last_full_boot <= 1) or (virtualization.type in [personal] and boot.days_since_last_full_boot <= 5))

---