DEX policies for Windows devices

  • Release version: Australia
  • Updated March 12, 2026
  • 3 minutes to read
  • Policy reference for DEX monitoring on Windows devices. Use this reference to understand available check instances, frequencies, and parameters for application, network, and device monitoring.

    To fetch the complete playbook data for a Windows device, the Agent Client Collector (ACC) must run as a local system account. For more details on how to set up the ACC service as a local system account, see Run ACC as a local system account user.

    Policies for Windows — Application

    DEX provides the following policies for applications.
    Table 1. DEX Windows Apps Metrics
    Check instance Description Frequency Historical or latest Check instance parameters*
    os.win.check-app-historical Collects the application metrics in the 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 theWindows 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 — Application Network Experience

    Before configuring the following policies, make sure that the Agent Client Collector is version 4.2 or higher to display the network path for applications. Additionally, the DEX browser extension plugin must be installed and should be version 2.5.0 or higher to fetch network metrics for web applications.
    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 applications.
    Table 2. DEX Windows Apps Domain Network Monitoring Metrics
    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
    os.win.check-app-dom-network-latest Collects Windows Web apps network monitoring metrics like latency, packet loss, and jitter and sends monitoring data to Metric Base and the ServiceNow instance. 30 mins Latest source_details, domain_network_route_details

    Policies for Windows — Device

    DEX provides the following policies for devices.
    Table 3. DEX Windows Device Metrics
    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, cpu_usage, memory_details, device_events, last_access_time, os_setup_details,bios_details, network_connection_profiles, network_adapter_details,gpu_usage, gpu_vram_usage,boot_details
    Important:
    * DEX Windows Device Metrics with the following check instance parameters runs only with a Local System account: energy_consumption, 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, io_usage_write, io_usage_read,cpu_usage, battery_charge_percentage, energy_consumption, memory_details,uptime, disk_details, cpu_performance_details, crashes, power_consumption, wifi_transmit_rate, wifi_receive_rate, wifi_signal_strength
    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
    Table 4. Policies for DEX Get online Windows user on change
    Check instance Description Frequency Historical or latest Check instance parameters
    os.win.check-system-custom-query-on-chan Gets a logged-in user's data on a Windows device whenever there’s a change. 60 secs Latest query,query_sys_id, query_type
    Table 5. Policies for DEX Get device configuration on change
    Check instance Description Frequency Historical or latest Check instance parameters
    os.all.check.internal.get-device-configu Gets a logged-in user's device configuration whenever there’s a change. 60 secs Latest Not applicable
    Note:
    If you upgrade the DEX Content Playbook plugin on an instance and encounter unexpected policy update issues, see the Troubleshooting: Policy update issues post DEX plugin upgrade [KB1586917] article in the Now Support knowledge base.