Skip to content

Commit 0b46ea6

Browse files
authored
Merge pull request #196865 from yoninalmsft/clear-sensor-edits-screenshot
clear sensor steps and screenshot
2 parents d5ee623 + bbb67fa commit 0b46ea6

File tree

2 files changed

+16
-0
lines changed

2 files changed

+16
-0
lines changed

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

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -183,6 +183,22 @@ Audit logs record key information at the time of occurrence. Audit logs are usef
183183

184184
The exported log is added to the **Archived Logs** list. Select the :::image type="icon" source="media/how-to-troubleshoot-the-sensor-and-on-premises-management-console/eye-icon.png" border="false"::: button to view the OTP. Send the OTP string to the support team in a separate message from the exported logs. The support team will be able to extract exported logs only by using the unique OTP that's used to encrypt the logs.
185185

186+
## Clearing sensor data to factory default
187+
188+
In cases where the sensor needs to be relocated or erased, the sensor can be reset to factory default data.
189+
190+
> [!NOTE]
191+
> Network settings such as IP/DNS/GATEWAY will not be changed by clearing system data.
192+
193+
**To clear system data**:
194+
1. Sign in to the sensor as the **cyberx** user.
195+
1. Select **Support** > **Clear system data**, and confirm that you do want to reset the sensor to factory default data.
196+
197+
:::image type="content" source="media/how-to-troubleshoot-the-sensor-and-on-premises-management-console/warning-screenshot.png" alt-text="Screenshot of warning message.":::
198+
199+
All allowlists, policies, and configuration settings are cleared, and the sensor is restarted.
200+
201+
186202
## Next steps
187203

188204
- [View alerts](how-to-view-alerts.md)
Loading

0 commit comments

Comments
 (0)