Batami's feedback

Author: Shereen-Bhar

articles/defender-for-iot/organizations/detect-windows-endpoints-script.md

@@ -9,7 +9,7 @@ ms.topic: how-to
 
 In addition to detecting OT devices on your network, use Defender for IoT to discover Microsoft Windows workstations and servers. Same as other detected devices, detected Windows workstations and servers are displayed in the Device inventory. The **Device inventory** pages on the sensor and on-premises management console show enriched data about Windows devices, including data about the Windows operating system and applications installed, patch-level data, open ports, and more.
 
-This article describes how to configure Defender for IoT to survey Windows workstations and servers which cannot be polled by WMI over the network. This local surveying is performed by distributing and running a script on each device. While you can use [active scanning](configure-active-monitoring.md) and [scheduled WMI scans](configure-windows-endpoint-monitoring.md) to obtain this data, working with local scripts bypasses the risks of running WMI polling on an endpoint. Running a local script is also useful for regulated networks that have waterfalls and one-way elements.
+This article describes how to use a Defender for IoT Windows-based WMI tool to get extended information from Windows devices, such as workstations, servers, and more. Run the WMI script on your Windows devices to get extended information, increasing your device inventory and security coverage. While you can also use [active scanning](configure-active-monitoring.md) and [scheduled WMI scans](configure-windows-endpoint-monitoring.md) to obtain this data, working with a local WMI script bypasses the risks of running WMI polling on an endpoint. Running a local script is also useful for regulated networks that have waterfalls and one-way elements.
 
 The script described in this article returns the following details about each detected device: