--- sourceDocument: Australia IT Service Management sourceDocumentLink: https://www.servicenow.com/docs/r/it-service-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia IT Service Management ft:clusterId : - itsm bundleId : - itsm workflow : - Technology --- # DEX policies for Windows devices # DEX policies for Windows devices {#ariaid-title1} * Release version: Australia * * Updated March 12, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 Windows devices DEX policies for Windows devices enable ServiceNow customers to monitor application, network, and device performance metrics efficiently. These policies collect detailed data and send it to Metric Base or the ServiceNow instance for analysis. Proper setup requires the Agent Client Collector (ACC) to run as a local system account to access comprehensive metrics. Show full answer Show less ## Application Monitoring DEX provides policies to collect application metrics such as CPU usage, memory use, uptime, crashes, and I/O statistics every 5 minutes with a historical perspective. Specific policies are available for Microsoft System Center Configuration Manager with daily updates. Note that uptime monitoring requires the ACC to run as a local system account. ## Application Network Experience These policies monitor network performance metrics (latency, packet loss, jitter) for installed and web applications every 10 to 30 minutes. Requirements include ACC version 4.2+ and DEX browser extension version 2.5.0+. Limitations include inability to trace paths with domain URLs due to the use of the tracert command. ## Device Monitoring Device policies collect comprehensive system metrics such as uptime, antivirus/firewall status, disk and CPU details, battery and power info, stability, pending updates, network profiles, GPU usage, and more. Data is collected at intervals ranging from 5 minutes to 24 hours, depending on the metric. Some parameters (e.g., energy consumption, BitLocker details) require the ACC running as a local system account. ## Change Monitoring Policies * **Online Windows user on change:** Captures logged-in user data every 60 seconds upon changes. * **Device configuration on change:** Captures device configuration whenever changes occur, also every 60 seconds. ## Important Considerations * The ACC must run as a local system account to enable full metric collection for certain parameters. * Ensure ACC and browser plugin versions meet the minimum requirements for network monitoring. * Be aware of limitations in network path tracing for domain URLs. * If you experience policy update issues after upgrading the DEX Content Playbook plugin, consult the ServiceNow knowledge base article KB1586917 for troubleshooting guidance. 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](https://www.servicenow.com/docs/X1ylfmfdELFR1F6aqW3_Ng "To fetch the complete playbook content data for a Windows device, the Agent Client Collector (ACC) must run as a local system account."). ## Policies for Windows --- Application {#dex-policies-windows__section_lnp_r1b_bxb} DEX provides the following policies for applications.{#dex-policies-windows__table_hxg_t1b_bxb__entry__5} | 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. ||||| [Table 1. DEX Windows Apps Metrics] {#dex-policies-windows__table_hxg_t1b_bxb} ## Policies for Windows --- Application Network Experience {#dex-policies-windows__section_l42_23n_12c} 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: \/\ {#dex-policies-windows__ul_jmw_njn_12c} DEX provides the following policies for applications.{#dex-policies-windows__table_fjx_z3n_12c__entry__5} | 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 | [Table 2. DEX Windows Apps Domain Network Monitoring Metrics] {#dex-policies-windows__table_fjx_z3n_12c} ## Policies for Windows --- Device {#dex-policies-windows__section_x4q_2md_hwb} DEX provides the following policies for devices.{#dex-policies-windows__table_cj5_4yd_1fc__entry__5} | 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 3. DEX Windows Device Metrics] {#dex-policies-windows__table_cj5_4yd_1fc} {#dex-policies-windows__table_uvg_5zp_53c__entry__5} | 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 4. Policies for DEX Get online Windows user on change] {#dex-policies-windows__table_uvg_5zp_53c} {#dex-policies-windows__table_xrv_zzp_53c__entry__5} | 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 | [Table 5. Policies for DEX Get device configuration on change] {#dex-policies-windows__table_xrv_zzp_53c} 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\]](https://support.servicenow.com/kb_view.do?sysparm_article=KB1586917) article in the Now Support knowledge base.