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
As the IoT Edge for Linux on Windows (EFLOW) application releases new versions, you want to update your IoT Edge devices for the latest features and security improvements. This article provides information about how to update your IoT Edge for Linux on Windows devices when a new version is available.
17
+
When a new version of the IoT Edge for Linux on Windows (EFLOW) application is released, update your IoT Edge devices to get the latest features and security improvements. This article explains how to update your IoT Edge for Linux on Windows devices when a new version is available.
18
18
19
19
20
-
With IoT Edge for Linux on Windows, IoT Edge runs in a Linux virtual machine hosted on a Windows device. This virtual machine is preinstalled with IoT Edge, and has no package manager, so you can't manually update or change any of the VM components. Instead, the virtual machine is managed with Microsoft Update to keep the components up to date automatically.
20
+
With IoT Edge for Linux on Windows, IoT Edge runs in a Linux virtual machine hosted on a Windows device. This virtual machine comes preinstalled with IoT Edge and doesn't have a package manager, so you can't manually update or change any of the VM components. Instead, Microsoft Update manages the virtual machine to keep the components up to date automatically.
21
21
22
-
The EFLOW virtual machine is designed to be reliably updated via Microsoft Update. The virtual machine operating system has an A/B update partition scheme to utilize a subset of those to make each update safe and enable a roll-back to a previous version if anything goes wrong during the update process.
22
+
The EFLOW virtual machine is designed for reliable updates through Microsoft Update. The virtual machine operating system uses an A/B update partition scheme to make each update safe and lets you rollback to a previous version if something goes wrong during the update process.
23
23
24
-
Each update consists of two main components that may get updated to latest versions. The first one is the EFLOW virtual machine and the internal components. For more information about EFLOW, see [Azure IoT Edge for Linux on Windows composition](./iot-edge-for-linux-on-windows.md). This also includes the virtual machine base operating system. The EFLOW virtual machine is based on [Microsoft CBL-Mariner](https://github.com/microsoft/CBL-Mariner) and each update provides performance and security fixes to keep the OS with the latest CVE patches. As part of the EFLOW Release notes, the version indicates the CBL-Mariner version used, and users can check the [CBL-Mariner Releases](https://github.com/microsoft/CBL-Mariner/releases)to get the list of CVEs fixed for each version.
24
+
Each update has two main components that can be updated to the latest versions. The first is the EFLOW virtual machine and its internal components. For more information about EFLOW, see [Azure IoT Edge for Linux on Windows composition](./iot-edge-for-linux-on-windows.md). This also includes the virtual machine base operating system. The EFLOW virtual machine is based on [Microsoft CBL-Mariner](https://github.com/microsoft/CBL-Mariner), and each update provides performance and security fixes to keep the OS up to date with the latest CVE patches. The EFLOW release notes show the CBL-Mariner version used, and you can check the [CBL-Mariner Releases](https://github.com/microsoft/CBL-Mariner/releases)for the list of CVEs fixed for each version.
25
25
26
26
The second component is the group of Windows runtime components needed to run and interop with the EFLOW virtual machine. The virtual machine lifecycle and interop is managed through different components: WSSDAgent, EFLOWProxy service, and the PowerShell module.
27
27
28
-
EFLOW updates are sequential and you need to update to every version in order. In order to get to the latest version, you have to either do a fresh installation using the latest available version, or apply all the previous servicing updates up to the desired version.
28
+
EFLOW updates are sequential, and you need to update to every version in order. To get to the latest version, either do a fresh installation using the latest available version or apply all previous servicing updates up to the version you want.
29
29
30
30
> [!IMPORTANT]
31
-
> Upgrading from EFLOW 1.4 LTS to EFLOW 1.5 LTS is supported using any of the methods described in this article. No special steps are needed to upgrade from EFLOW 1.4 LTS to EFLOW 1.5 LTS.
31
+
> You can upgrade from EFLOW 1.4 LTS to EFLOW 1.5 LTS using any of the methods described in this article. No special steps are needed to upgrade from EFLOW 1.4 LTS to EFLOW 1.5 LTS.
32
32
33
33
To find the latest version of Azure IoT Edge for Linux on Windows, see [EFLOW releases](https://aka.ms/AzEFLOW-Releases).
34
34
35
35
## Update using Microsoft Update
36
36
37
-
To receive IoT Edge for Linux on Windows updates, the Windows host should be configured to receive updates for other Microsoft products. By default, Microsoft Updates is turned on during EFLOW installation. If custom configuration is needed after EFLOW installation, you can turn this option On/Off with the following steps:
37
+
To get IoT Edge for Linux on Windows updates, configure the Windows host to get updates for other Microsoft products. By default, Microsoft Updates is on during EFLOW installation. If you need a custom configuration after EFLOW installation, turn this option on or off with these steps:
38
38
39
39
1. Open **Settings** on the Windows host.
40
40
41
41
1. Select **Updates & Security**.
42
42
43
43
1. Select **Advanced options**.
44
44
45
-
1.Toggle the *Receive updates for other Microsoft products when you update Windows*button to **On**.
45
+
1.Turn the *Receive updates for other Microsoft products when you update Windows*option to **On**.
46
46
47
47
48
48
## Update using Windows Server Update Services (WSUS)
49
49
50
-
Onpremises updates using WSUS is supported for IoT Edge for Linux on Windows updates. For more information about WSUS, see [Device Management Overview - WSUS](/windows/iot/iot-enterprise/device-management/device-management-overview#windows-server-update-services-wsus).
50
+
On-premises updates using WSUS are supported for IoT Edge for Linux on Windows updates. For more information about WSUS, see [Device Management Overview - WSUS](/windows/iot/iot-enterprise/device-management/device-management-overview#windows-server-update-services-wsus).
51
51
52
52
53
53
## Offline manual update
54
54
55
-
In some scenarios with restricted or limited internet connectivity, you may want to manually apply EFLOW updates offline. This is possible using Microsoft Update offline mechanisms. You can manually download and install an IoT Edge for Linux on Windows updates with the following steps:
55
+
If you have restricted or limited internet connectivity, you can manually apply EFLOW updates offline. Use Microsoft Update offline mechanisms to manually download and install IoT Edge for Linux on Windows updates. Follow these steps:
56
56
57
57
1. Check the current EFLOW installed version. Open **Settings** then select **Apps** -> **Apps & features**. Search for *Azure IoT Edge*.
58
58
@@ -64,11 +64,11 @@ In some scenarios with restricted or limited internet connectivity, you may want
64
64
65
65
## Managing Microsoft Updates
66
66
67
-
As explained before, IoT Edges for Linux on Windows updates are serviced using Microsoft Update channel. To change receiving EFLOW updates, you have to manage Microsoft Updates. The following list includes ways to automate turning on or off Microsoft updates. For more information about managing OS updates, see [OS Updates](/windows/iot/iot-enterprise/os-features/updates#completely-turn-off-windows-updates).
67
+
IoT Edge for Linux on Windows updates are serviced using Microsoft Update channel. To change receiving EFLOW updates, you have to manage Microsoft Updates. The following list includes ways to automate turning on or off Microsoft updates. For more information about managing OS updates, see [OS Updates](/windows/iot/iot-enterprise/os-features/updates#completely-turn-off-windows-updates).
68
68
69
-
-**CSP Policies** - By using the **Update/AllowMUUpdateService** CSP Policy - For more information about Microsoft Updates CSP policy, see [Policy CSP - MU Update](/windows/client-management/mdm/policy-csp-update#update-allowmuupdateservice).
69
+
-**CSP Policies** - Use the **Update/AllowMUUpdateService** CSP policy. For more information about the Microsoft Updates CSP policy, see [Policy CSP - MU Update](/windows/client-management/mdm/policy-csp-update#update-allowmuupdateservice).
70
70
71
-
-**Manually manage Microsoft Updates** - For more information about how to Opt-In to Microsoft Updates, see [Opt-In to Microsoft Update](/windows/win32/wua_sdk/opt-in-to-microsoft-update).
71
+
-**Manually manage Microsoft Updates** - To opt in to Microsoft Updates, see [Opt-In to Microsoft Update](/windows/win32/wua_sdk/opt-in-to-microsoft-update).
72
72
73
73
## Migration between EFLOW 1.1LTS and EFLOW 1.4LTS
74
74
@@ -84,7 +84,7 @@ Migration between EFLOW 1.1LTS to EFLOW 1.4LTS was introduced as part of EFLOW 1
84
84
To migrate between EFLOW 1.1LTS to EFLOW 1.4LTS, use the following steps.
85
85
86
86
1. Get the latest Azure EFLOW 1.1LTS [(1.1.2212.12122)](https://aka.ms/AzEFLOWMSI-Update-1_1_2212_12122) update. If you're using Windows Update, *Check Updates* to get the latest EFLOW update.
87
-
1. For auto-download migration (needs Internet connection), skip this step. If the EFLOW VM has limited/no internet access, download the necessary files before starting the migration.
87
+
1. For auto-download migration (needs internet connection), skip this step. If the EFLOW VM has limited/no internet access, download the necessary files before starting the migration.
> If for any reason the migration fails, the EFLOW VM will be restored to its original 1.1LTS version.
116
-
> If you want to cancel the migration or manually restore the EFLOW VM to prior state, you can use the following cmdlets `Start-EflowMigration` and then `Restore-EflowPriorToMigration`.
115
+
> If the migration fails for any reason, the EFLOW VM is restored to its original 1.1LTS version.
116
+
> To cancel the migration or manually restore the EFLOW VM to its prior state, run the `Start-EflowMigration` cmdlet and then `Restore-EflowPriorToMigration`.
117
117
118
118
For more information, check `Start-EflowMigration`, `Confirm-EflowMigration` and `Restore-EflowPriorToMigration` cmdlet documentation by using the `Get-Help <cmdlet> -full` command.
119
119
120
120
## Next steps
121
121
122
122
View the latest [IoT Edge for Linux on Windows releases](https://github.com/Azure/iotedge-eflow/releases).
123
123
124
-
Read more about [IoT Edge for Linux on Windows security premises](./iot-edge-for-linux-on-windows-security.md).
124
+
Learn about [IoT Edge for Linux on Windows security premises](./iot-edge-for-linux-on-windows-security.md).
0 commit comments