You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/detect-windows-endpoints-script.md
+8-16Lines changed: 8 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,26 +43,18 @@ The script described in this article is supported for the following Windows oper
43
43
- Windows 10
44
44
- Windows Server 2003/2008/2012/2016/2019
45
45
46
-
## Download the script
46
+
## Download and run the script
47
47
48
-
In order to run the script, you first need to download it from the OT sensor console.
48
+
This procedure describes how to deploy and run a script on the Windows workstation and servers that you want to monitor in Defender for IoT.
49
+
50
+
The script detects enriched Windows data, and is run as a utility and not an installed program. Running the script doesn't affect the endpoint. You may want to deploy the script once, or using ongoing automation, using standard automated deployment methods and tools.
49
51
50
52
1. Sign into your OT sensor console, and select **System Settings** > **Import Settings** > **Windows Information**.
51
53
52
-
1. Select **Download script**.
54
+
1. Select **Download script**. For example:
53
55
54
56
:::image type="content" source="media/detect-windows-endpoints-script/download-wmi-script.png" alt-text="Screenshot of where to download WMI script." lightbox="media/detect-windows-endpoints-script/download-wmi-script.png":::
55
57
56
-
## Run the script
57
-
58
-
This procedure describes how to deploy and run the script on the Windows workstation and servers that you want to monitor in Defender for IoT.
59
-
60
-
The script you run to detect enriched Windows data is run as a utility and not as an installed program. Running the script doesn't affect the endpoint.
61
-
62
-
1. Deploy the script once, or using ongoing automation, using standard automated deployment methods and tools.
63
-
64
-
1. Download the WMI script as described [earlier](#download-the-script).
65
-
66
58
1. Copy the script to a local drive and unzip it. The following files appear:
67
59
68
60
-`start.bat`
@@ -74,15 +66,15 @@ The script you run to detect enriched Windows data is run as a utility and not a
74
66
75
67
After the script runs to probe the registry, a CX-snapshot file appears with the registry information. The filename indicates the system name, date, and time of the snapshot with the following syntax: `CX-snaphot_SystemName_Month_Year_Time`
76
68
77
-
Files generated by the script:
69
+
Files generated by the script include:
78
70
79
71
- Remain on the local drive until you delete them.
80
72
- Must remain in the same location. Don't separate the generated files.
81
73
- Are overwritten if you run the script again.
82
74
83
75
## Import device details
84
76
85
-
After having run the script as described [earlier](#run-the-script), import the generated data to your sensor to view the device details in the **Device inventory**.
77
+
After having run the script as described [earlier](#download-and-run-the-script), import the generated data to your sensor to view the device details in the **Device inventory**.
86
78
87
79
**To import device details to your sensor**:
88
80
@@ -104,7 +96,7 @@ After having run the script as described [earlier](#run-the-script), import the
104
96
105
97
To preform offline WMI:
106
98
107
-
1.[Download the script](#download-the-script), then extract it.
99
+
1.[Download the script](#download-and-run-the-script), then extract it.
108
100
109
101
1. Run `run.bat` as administrator directly on the Windows endpoint.
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/release-notes.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -101,7 +101,7 @@ To understand whether a feature is supported in your sensor version, check the r
101
101
102
102
**Supported until**: 03/2024
103
103
104
-
-[Download WMI script from OT sensor console](detect-windows-endpoints-script.md#download-the-script)
104
+
-[Download WMI script from OT sensor console](detect-windows-endpoints-script.md#download-and-run-the-script)
105
105
-[Automatically resolved notifications for operating system changes and device type changes](how-to-work-with-the-sensor-device-map.md#device-notification-responses)
106
106
-[UI enhancements when uploading SSL/TLS certificates](how-to-deploy-certificates.md#deploy-a-certificate-on-an-ot-sensor)
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/whats-new.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,9 +26,9 @@ Features released earlier than nine months ago are described in the [What's new
26
26
27
27
The script used to configure OT sensors to detect Microsoft Windows workstations and servers is now available for download from the OT sensor itself.
28
28
29
-
For more information, see [Download the script](detect-windows-endpoints-script.md#download-the-script).
29
+
For more information, see [Download the script](detect-windows-endpoints-script.md#download-and-run-the-script)
30
30
31
-
### Automatically resolved notifications for operating system changes
31
+
### Automatically resolved OS notifications
32
32
33
33
After updating your OT sensor to version 22.3.8, no new device notifications for **Operating system changes** are generated. Existing **Operating system changes** notifications are automatically resolved if they aren't dismissed or otherwise handled within 14 days.
0 commit comments