DEX policies for persistent VDIs

  • Release version: Australia
  • Updated April 2, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of DEX policies for persistent VDIs

    This document provides a reference for Digital Experience (DEX) monitoring policies specifically designed for Windows persistent Virtual Desktop Infrastructures (VDIs). It helps ServiceNow customers understand the available check instances, their frequencies, and parameters used for monitoring applications, network experience, and device health on persistent VDI environments.

    Show full answer Show less

    Application Monitoring Policies

    • os.win.check-app-historical: Collects historical application metrics from persistent VDI Windows devices every 5 minutes, sending data such as CPU usage, memory usage, uptime, crashes, and IO operations to MetricBase. Requires running with the Local System account for uptime metrics.
    • os.win.check-app-sccm-latest: Gathers latest metrics specifically for Microsoft System Center Configuration Manager on persistent VDIs once every 24 hours.

    Application Network Experience Policies

    These policies monitor network metrics like latency, packet loss, and jitter for Windows installed applications and web apps every 10 minutes. Limitations include using tracert for network path discovery, which does not support domain URL paths.

    • os.win.check-app-dom-network-historical: Collects historical network metrics for installed Windows apps, sending data to MetricBase and ServiceNow instances.
    • os.win.check-web-app-dom-net-historical: Captures historical network metrics for Windows web applications, also sending data to MetricBase and ServiceNow.

    Device Monitoring Policies

    • os.win.check-system-metrics-latest: Collects latest Windows device metrics every 24 hours, including uptime, antivirus status, disk details, CPU and memory usage, network profiles, and more. Certain parameters (e.g., bitlockerdetails, pendingupdates, userprofiles) require running under the Local System account.
    • os.win.check-system-metrics-historical: Available in two variants collecting historical device metrics every 30 minutes (network profiles) and every 5 minutes (disk usage, CPU usage, memory details, GPU usage, crashes, etc.), sending data to MetricBase.
    • os.win.check-process-data: Collects running Windows process data once daily, sending to the ServiceNow instance.
    • os.win.check-sys-compliance-historical and os.win.check-sys-compliance-latest: Collect Windows device compliance metrics every 5 minutes (historical) and 24 hours (latest), reporting to ServiceNow.
    • os.win.check-system-executables-latest: Retrieves all executable files on Windows volumes once daily.
    • os.win.check-system-registry-latest: Gathers Windows registry data daily.

    Key Outcomes

    By implementing these DEX policies, ServiceNow customers can gain comprehensive visibility into application performance, network experience, and device health on persistent Windows VDIs. This enables proactive monitoring and timely remediation to improve end-user experience and maintain VDI environment stability.

    Policy reference for DEX monitoring on Windows persistent Virtual Desktop Infrastructures (VDI). Use this reference to understand available check instances, frequencies, and parameters for application, network, and device monitoring.

    Policies for Windows persistent VDIs — Application

    DEX provides the following policies for persistent VDI applications.
    Check instance Description Frequency Historical or latest Check instance parameters*
    os.win.check-app-historical Collects the application metrics in the persistent VDI Windows device and sends the metric data to Metric Base. 5 mins Historical

    cpu_usage, memory_usage, uptime, last_access_time, crashes, io_usage_read, io_usage_write, is_running, freezes, zscaler_service_status
    os.win.check-app-sccm-latest Collect application-specific metrics for the Microsoft System Center Configuration Manager app on the persistent VDI Windows device. 24 hours Latest Not applicable
    Important:
    * DEX Windows Apps Metrics with the uptime check instance parameter only runs with the Local System account.

    Policies for Windows persistent VDIs — Application Network Experience

    Note:
    These policies have the following limitations:
    • A tracert command is used to get the network path.
    • ANE doesn't work for path in the domain URL. Example: <domain>/<path>
    DEX provides the following policies for persistent VDIs applications.
    Check instance Description Frequency Historical or latest Check instance parameters
    os.win.check-app-dom-network-historical Collects Windows installed apps network monitoring metrics like latency, packet loss, and jitter and sends monitoring data to Metric Base and the ServiceNow® instance. 10 mins Historical domain_network_details
    os.win.check-web-app-dom-net-historical Collects Windows Web apps network monitoring metrics like latency, packet loss, and jitter and sends monitoring data to Metric Base and the ServiceNow instance. 10 mins Historical domain_network_details

    Policies for Windows persistent VDIs — Device

    DEX provides the following policies for persistent VDI devices.
    Check instance Description Frequency Historical or latest Check instance parameters*
    os.win.check-system-metrics-latest Collects Windows device metrics and sends the metric data to the ServiceNow instance. 24 hours Latest uptime, logged_in, antivirus_enabled, firewall_enabled, disk_details, device_details, battery_details, bsod_details, cpu_details, os_details, power_plan, stability_index, pending_updates, network_details, bitlocker_details, user_profiles, antimalware_details, hard_drive_status, peripheral_devices_details, device_events, last_access_time, os_setup_details, cpu_usage, memory_details, bios_details, network_connection_profiles, network_adapter_details, boot_details, reboot_details
    Important:
    * DEX Windows Device Metrics with the following check instance parameters runs only with a Local System account: bitlocker_details, last_access_time, pending_updates, user_profiles.
    os.win.check-system-metrics-historical Collects Windows device metrics and sends the metric data to MetricBase. 30 mins Historical network_connection_profiles
    os.win.check-system-metrics-historical Collects Windows device metrics and sends the metric data to MetricBase. 5 mins Historical disk_usage, disk_available, io_usage_write, io_usage_read, memory_details, cpu_usage, battery_charge_percentage, energy_consumption, wifi_transmit_rate, wifi_receive_rate, wifi_signal_strength, uptime, disk_details, cpu_performance_details, crashes, power_consumption, gpu_usage, gpu_vram_usage
    os.win.check-process-data Collects data for running Windows processes and sends the data to the ServiceNow instance. 24 hours Not applicable Not applicable
    os.win.check-sys-compliance-historical Collects Windows device metrics and sends the metric data to the ServiceNow instance. 5 mins Historical Not applicable
    os.win.check-sys-compliance-latest Collects Windows device metrics and sends the metric data to the ServiceNow instance. 24 hours Latest Not applicable
    os.win.check-system-executables-latest Collects all the executables present on all volumes of a Windows device. 24 hours Latest config_file_read
    os.win.check-system-registry-latest Gets registry data on Windows device. 24 hours Latest config_file_read