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 details the various check instances, their frequencies, and parameters available for monitoring applications, network experience, and device health within persistent VDIs. These policies help ServiceNow customers effectively monitor and maintain the performance and stability of their Windows persistent VDI environments.

    Show full answer Show less

    Application Monitoring Policies

    • os.win.check-app-historical: Collects historical application metrics every 5 minutes, including CPU and memory usage, uptime, crashes, IO usage, and service status, sending data to Metric Base.
    • os.win.check-app-sccm-latest: Gathers latest metrics for Microsoft System Center Configuration Manager app every 24 hours. Note that uptime checks run only with Local System account.

    Application Network Experience (ANE) Policies

    These policies monitor network metrics such as latency, packet loss, and jitter for installed Windows apps and web apps. They run every 10 minutes and send data to Metric Base and the ServiceNow instance. Limitations include use of tracert command, which does not support domain URL paths.

    • os.win.check-app-dom-network-historical: Monitors network for Windows installed apps.
    • os.win.check-web-app-dom-net-historical: Monitors network for Windows web apps.

    Device Monitoring Policies

    • os.win.check-system-metrics-latest: Collects device metrics every 24 hours, including uptime, antivirus/firewall status, disk and CPU details, updates, network, and more, sending data to the ServiceNow instance. Certain parameters require Local System account.
    • os.win.check-system-metrics-historical: Runs every 30 minutes or 5 minutes depending on parameters, collecting detailed device metrics sent to Metric Base.
    • os.win.check-process-data: Gathers data on running processes every 24 hours.
    • os.win.check-sys-compliance-historical/latest: Collects device compliance metrics every 5 minutes or 24 hours, respectively.
    • os.win.check-system-executables-latest: Retrieves all executables on device volumes every 24 hours.
    • os.win.check-system-registry-latest: Collects registry data every 24 hours.

    Key Considerations

    • Several check instances with parameters such as uptime and bitlockerdetails require running under the Local System account for proper data collection.
    • Network path monitoring uses tracert command, which does not function for URLs with domain paths.

    By leveraging these DEX policies, ServiceNow customers can gain comprehensive visibility and monitoring capabilities for Windows persistent VDIs, enabling proactive management of application performance, network health, and device stability within their virtual desktop environments.

    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