Skip to content

Commit 3830d6f

Browse files
authored
Merge pull request #216888 from yoninalmsft/clear-system-data-sensor
clear system data on sensor
2 parents 932094a + d6bbf99 commit 3830d6f

File tree

3 files changed

+26
-16
lines changed

3 files changed

+26
-16
lines changed

articles/defender-for-iot/organizations/how-to-manage-individual-sensors.md

Lines changed: 23 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -379,7 +379,7 @@ This procedure describes how to download a diagnostics log to send to support in
379379
This feature is supported for the following sensor versions:
380380

381381
- **22.1.1** - Download a diagnostic log from the sensor console
382-
- **22.1.3** - For locally-managed sensors, [upload a diagnostics log](how-to-manage-sensors-on-the-cloud.md#upload-a-diagnostics-log-for-support-public-preview) from the **Sites and sensors** page in the Azure portal. This file is automatically sent to support when you open a ticket on a cloud-connected sensor.
382+
- **22.1.3** - For locally managed sensors, [upload a diagnostics log](how-to-manage-sensors-on-the-cloud.md#upload-a-diagnostics-log-for-support-public-preview) from the **Sites and sensors** page in the Azure portal. This file is automatically sent to support when you open a ticket on a cloud-connected sensor.
383383

384384
[!INCLUDE [root-of-trust](includes/root-of-trust.md)]
385385

@@ -391,7 +391,28 @@ This feature is supported for the following sensor versions:
391391

392392
:::image type="content" source="media/release-notes/support-ticket-diagnostics.png" alt-text="Screenshot of the Backup & Restore pane showing the Support Ticket Diagnostics option." lightbox="media/release-notes/support-ticket-diagnostics.png":::
393393

394-
1. For a locally-managed sensor, version 22.1.3 or higher, continue with [Upload a diagnostics log for support](how-to-manage-sensors-on-the-cloud.md#upload-a-diagnostics-log-for-support-public-preview).
394+
1. For a locally managed sensor, version 22.1.3 or higher, continue with [Upload a diagnostics log for support](how-to-manage-sensors-on-the-cloud.md#upload-a-diagnostics-log-for-support-public-preview).
395+
396+
## Clearing sensor data
397+
398+
In cases where the sensor needs to be relocated or erased, the sensor can be reset.
399+
400+
Clearing data deletes all detected or learned data on the sensor. After clearing data on a cloud connected sensor, cloud inventory will be updated accordingly. Additionally, some actions on the corresponding cloud alerts such as downloading PCAPs or learning alerts will not be supported.
401+
402+
> [!NOTE]
403+
> Network settings such as IP/DNS/GATEWAY will not be changed by clearing system data.
404+
405+
**To clear system data**:
406+
407+
1. Sign in to the sensor as the **cyberx** user.
408+
409+
1. Select **Support** > **Clear data**.
410+
411+
1. In the confirmation dialog box, select **Yes** to confirm that you do want to clear all data from the sensor and reset it. For example:
412+
413+
:::image type="content" source="media/how-to-manage-individual-sensors/clear-system-data.png" alt-text="Screenshot of clearing system data on the support page in the sensor console.":::
414+
415+
A confirmation message appears that the action was successful. All learned data, allowlists, policies, and configuration settings are cleared from the sensor.
395416

396417
## Next steps
397418

articles/defender-for-iot/organizations/how-to-troubleshoot-the-sensor-and-on-premises-management-console.md

Lines changed: 3 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -242,22 +242,11 @@ Sometimes ICS devices are configured with external IP addresses. These ICS devic
242242
1. Generate a new data-mining report for internet connections.
243243
1. In the data-mining report, enter the administrator mode and delete the IP addresses of your ICS devices.
244244

245-
### Clearing sensor data to factory default
246-
247-
In cases where the sensor needs to be relocated or erased, the sensor can be reset to factory default data.
248-
249-
> [!NOTE]
250-
> Network settings such as IP/DNS/GATEWAY will not be changed by clearing system data.
251-
252-
**To clear system data**:
253-
1. Sign in to the sensor as the **cyberx** user.
254-
1. Select **Support** > **Clear system data**, and confirm that you do want to reset the sensor to factory default data.
255-
256-
:::image type="content" source="media/how-to-troubleshoot-the-sensor-and-on-premises-management-console/warning-screenshot.png" alt-text="Screenshot of warning message.":::
257-
258-
All allowlists, policies, and configuration settings are cleared, and the sensor is restarted.
245+
### Clearing sensor data
259246

247+
In cases where the sensor needs to be relocated or erased, all learned data can be cleared from the sensor.
260248

249+
For more information on how to clear system data, see [Clearing sensor data](how-to-manage-individual-sensors.md#clearing-sensor-data).
261250

262251
## Troubleshoot an on-premises management console
263252

168 KB
Loading

0 commit comments

Comments
 (0)