Skip to content

Commit a83259c

Browse files
committed
fixing broken xrefs
1 parent ad3ee44 commit a83259c

File tree

3 files changed

+6
-6
lines changed

3 files changed

+6
-6
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ The script described in this article is supported for the following Windows oper
4545

4646
## Download and run the script
4747

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.
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.
4949

5050
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.
5151

@@ -74,7 +74,7 @@ Files generated by the script include:
7474

7575
## Import device details
7676

77-
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**.
7878

7979
**To import device details to your sensor**:
8080

@@ -96,7 +96,7 @@ After having run the script as described [earlier](#run-the-script), import the
9696

9797
To preform offline WMI:
9898

99-
1. [Download the script](#download-the-script), then extract it.
99+
1. [Download the script](#download-and-run-the-script), then extract it.
100100

101101
1. Run `run.bat` as administrator directly on the Windows endpoint.
102102

articles/defender-for-iot/organizations/release-notes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,7 @@ To understand whether a feature is supported in your sensor version, check the r
101101

102102
**Supported until**: 03/2024
103103

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)
105105
- [Automatically resolved notifications for operating system changes and device type changes](how-to-work-with-the-sensor-device-map.md#device-notification-responses)
106106
- [UI enhancements when uploading SSL/TLS certificates](how-to-deploy-certificates.md#deploy-a-certificate-on-an-ot-sensor)
107107

articles/defender-for-iot/organizations/whats-new.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,9 +26,9 @@ Features released earlier than nine months ago are described in the [What's new
2626

2727
The WMI script can now be downloaded from the OT sensor console.
2828

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)
3030

31-
### Automatically resolved notifications for operating system changes
31+
### Automatically resolved OS notifications
3232

3333
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.
3434

0 commit comments

Comments
 (0)