Skip to content

Commit 4003d89

Browse files
Merge pull request #212817 from batamig/patch-242
adding "for example"
2 parents 8d3ffab + 8cbf194 commit 4003d89

File tree

1 file changed

+7
-8
lines changed

1 file changed

+7
-8
lines changed

articles/defender-for-iot/organizations/update-ot-software.md

Lines changed: 7 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ When downloading your update files from the Azure portal, you’ll see the optio
1919

2020
Make sure to select the file that matches your upgrade scenario.
2121

22-
Updates from legacy versions may require a series of software updates. For example, if you still have a sensor version 3.1.1 installed, you'll need to first upgrade to version 10.5.5, and then to a 22.x version.
22+
Updates from legacy versions may require a series of software updates: If you still have a sensor version 3.1.1 installed, you'll need to first upgrade to version 10.5.5, and then to a 22.x version. For example:
2323

2424
:::image type="content" source="media/update-ot-software/legacy.png" alt-text="Screenshot of the multiple download options displayed.":::
2525

@@ -97,13 +97,13 @@ This procedure describes how to manually download the new sensor software versio
9797

9898
1. On your sensor console, select **System Settings** > **Sensor management** > **Software Update**.
9999

100-
1. On the **Software Update** pane on the right, select **Upload file**, and then navigate to and select your downloaded `legacy-sensor-secured-patcher-<Version number>.tar` file.
100+
1. On the **Software Update** pane on the right, select **Upload file**, and then navigate to and select your downloaded `legacy-sensor-secured-patcher-<Version number>.tar` file. For example:
101101

102102
:::image type="content" source="media/how-to-manage-individual-sensors/upgrade-pane-v2.png" alt-text="Screenshot of the Software Update pane on the sensor." lightbox="media/how-to-manage-individual-sensors/upgrade-pane-v2.png":::
103103

104104
The update process starts, and may take about 30 minutes. During your upgrade, the system is rebooted twice.
105105

106-
Sign in when prompted, and then return to the **System Settings** > **Sensor management** > **Software Update** pane to confirm that the new version is listed.
106+
Sign in when prompted, and then return to the **System Settings** > **Sensor management** > **Software Update** pane to confirm that the new version is listed. For example:
107107

108108
:::image type="content" source="media/how-to-manage-individual-sensors/defender-for-iot-version.png" alt-text="Screenshot of the upgrade version that appears after you sign in." lightbox="media/how-to-manage-individual-sensors/defender-for-iot-version.png":::
109109

@@ -119,7 +119,7 @@ The sensor update process won't succeed if you don't update the on-premises mana
119119

120120
**To update several sensors**:
121121

122-
1. On the Azure portal, go to **Defender for IoT** > **Updates**. Under **Sensors**, select **Download** and save the file.
122+
1. On the Azure portal, go to **Defender for IoT** > **Updates**. Under **Sensors**, select **Download** and save the file. For example:
123123

124124
:::image type="content" source="media/how-to-manage-individual-sensors/updates-page.png" alt-text="Screenshot of the Updates page of Defender for IoT." lightbox="media/how-to-manage-individual-sensors/updates-page.png":::
125125

@@ -133,8 +133,7 @@ The sensor update process won't succeed if you don't update the on-premises mana
133133

134134
Also make sure that sensors you *don't* want to update are *not* selected.
135135

136-
Save your changes when you're finished selecting sensors to update.
137-
136+
Save your changes when you're finished selecting sensors to update. For example:
138137

139138
:::image type="content" source="media/how-to-manage-sensors-from-the-on-premises-management-console/automatic-updates.png" alt-text="Screenshot of on-premises management console with Automatic Version Updates selected." lightbox="media/how-to-manage-sensors-from-the-on-premises-management-console/automatic-updates.png":::
140139

@@ -169,7 +168,7 @@ This procedure is relevant only if you're updating sensors from software version
169168

170169
1. Select the site where you want to update your sensor, and then browse to the sensor you want to update.
171170

172-
1. Expand the row for your sensor, select the options **...** menu on the right of the row, and then select **Prepare to update to 22.x**.
171+
1. Expand the row for your sensor, select the options **...** menu on the right of the row, and then select **Prepare to update to 22.x**. For example:
173172

174173
:::image type="content" source="media/how-to-manage-sensors-on-the-cloud/prepare-to-update.png" alt-text="Screenshot of the Prepare to update option." lightbox="media/how-to-manage-sensors-on-the-cloud/prepare-to-update.png":::
175174

@@ -225,4 +224,4 @@ For more information, see:
225224
- [Manage sensors from the management console](how-to-manage-sensors-from-the-on-premises-management-console.md)
226225
- [Manage sensors with Defender for IoT in the Azure portal](how-to-manage-sensors-on-the-cloud.md)
227226
- [Manage the on-premises management console](how-to-manage-the-on-premises-management-console.md)
228-
- [Troubleshoot the sensor and on-premises management console](how-to-troubleshoot-the-sensor-and-on-premises-management-console.md)
227+
- [Troubleshoot the sensor and on-premises management console](how-to-troubleshoot-the-sensor-and-on-premises-management-console.md)

0 commit comments

Comments
 (0)