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/configure-sensor-settings-portal.md
+18Lines changed: 18 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -217,6 +217,24 @@ Add the range of IP addresses to configure the DHCP settings that can apply to a
217
217
1. Select **Next: Review**.
218
218
1. Review the details and select **Save and assign** to add the range of addresses to the DHCP range list.
219
219
220
+
## Configure a backup server
221
+
222
+
Your OT sensor can have a backup server setup during its initially deployment or later on. In both cases, follow this procedure to confirm that the backup server is correctly configured once it's setup.
223
+
224
+
A misconfigured backup server might falsely recognize traffic as malware and trigger a [Malware engine alert](alert-engine-messages.md#malware-engine-alerts). If you think a **Suspicion of Malicious Activity** malware alert was triggered falsely, consider following this procedure to check the backup server configuration.
225
+
226
+
**To configure the backup server:**
227
+
228
+
1. Sign into your OT sensor console and select **System settings** > **Sensor management** > **Advanced configurations**.
229
+
230
+
1. Select the **Global** category. Ensure the parameter **is_reduce_backup_malware_enabled** is set to **1** or **true**.
231
+
232
+
1. Select the **Vulnerability assessment** category. Ensure **backup_servers** lists the backup server device's IP address.
233
+
234
+
1. Select the **Ports** category. Ensure that **backup_known_ports** lists the port(s) that the backup server uses.
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/how-to-manage-individual-sensors.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
@@ -416,7 +416,7 @@ After clearing data on a cloud-connected sensor:
416
416
417
417
**To clear system data**:
418
418
419
-
1. Sign in to the OT sensor as the *admin* user. For more information, see [Default privileged on-premises users](roles-on-premises.md#default-privileged-on-premises-users).
419
+
1. Sign into the OT sensor as the *admin* user. For more information, see [Default privileged on-premises users](roles-on-premises.md#default-privileged-on-premises-users).
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/how-to-troubleshoot-sensor.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -247,7 +247,7 @@ When signing into a pre-configured sensor for the first time, you'll need to per
247
247
1. Select **Next**, and your user, and a system-generated password for your OT sensor will then appear.
248
248
249
249
> [!NOTE]
250
-
> When you sign in to a sensor for the first time, it's linked to your Azure subscription, which you'll need if you need to recover the password for the *admin* user. For more information, see [Recover privileged access to a sensor](manage-users-sensor.md#recover-privileged-access-to-a-sensor).
250
+
> When you sign in to a sensor for the first time, it's linked to your Azure subscription, which you need if you need to recover the password for the *admin* user. For more information, see [Recover privileged access to a sensor](manage-users-sensor.md#recover-privileged-access-to-a-sensor).
251
251
252
252
## Investigate a lack of traffic
253
253
@@ -257,7 +257,7 @@ An indicator appears at the top of the console when the sensor recognizes that t
257
257
258
258
When a new sensor is deployed or a sensor is working slowly or not showing any alerts, you can check system performance.
259
259
260
-
1. Sign in to the sensor and select **Overview**. Make sure that **PPS** is greater than 0, and that **Devices** are being discovered.
260
+
1. Sign in to the sensor and select **Overview**. Make sure that **PPS** is greater than 0, and that **Devices** are being discovered.
261
261
1. In the **Data Mining** page, generate a report.
262
262
1. In the **Trends & Statistics** page, create a dashboard.
263
263
1. In the **Alerts** page, check that the alert was created.
@@ -289,7 +289,7 @@ For more information, see:
289
289
290
290
## Connect the sensor to NTP
291
291
292
-
You can configure a standalone sensor and a OT sensor console, with the sensors related to it, to connect to NTP.
292
+
You can configure a standalone sensor and an OT sensor console, with the sensors related to it, to connect to NTP.
293
293
294
294
> [!TIP]
295
295
> When you're ready to start managing your OT sensor settings at scale, define NTP settings from the Azure portal. Once you apply settings from the Azure portal, settings on the sensor console are read-only. For more information, see [Configure OT sensor settings from the Azure portal (Public preview)](configure-sensor-settings-portal.md).
@@ -319,7 +319,7 @@ For more information on how to clear system data, see [Clear OT sensor data](how
319
319
320
320
## Export logs from the sensor console for troubleshooting
321
321
322
-
For further troubleshooting, you may want to export logs to send to the support team, such as database or operating system logs.
322
+
For further troubleshooting, you might want to export logs to send to the support team, such as database or operating system logs.
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
@@ -2,7 +2,7 @@
2
2
title: What's new in Microsoft Defender for IoT
3
3
description: This article describes new features available in Microsoft Defender for IoT, including both OT and Enterprise IoT networks, and both on-premises and in the Azure portal.
4
4
ms.topic: whats-new
5
-
ms.date: 04/06/2025
5
+
ms.date: 05/05/2025
6
6
ms.custom: enterprise-iot
7
7
---
8
8
@@ -20,7 +20,7 @@ Features released earlier than nine months ago are described in the [What's new
20
20
21
21
## On-premises management console retirement
22
22
23
-
The legacy on-premises management console won't be available for download after **January 1st, 2025**. We recommend transitioning to the new architecture using the full spectrum of on-premises and cloud APIs before this date. For more information, see [on-premises management console retirement](ot-deploy/on-premises-management-console-retirement.md).
23
+
The legacy on-premises management console isn't available for download after **January 1st, 2025**. We recommend transitioning to the new architecture using the full spectrum of on-premises and cloud APIs before this date. For more information, see [on-premises management console retirement](ot-deploy/on-premises-management-console-retirement.md).
0 commit comments