Skip to content

Commit 67d5211

Browse files
Merge pull request #221282 from dominicbetts/central-eflow
IoTCentral: update EFLOW
2 parents 2c39202 + 7a1ae5c commit 67d5211

File tree

1 file changed

+40
-29
lines changed

1 file changed

+40
-29
lines changed

articles/iot-central/core/howto-connect-eflow.md

Lines changed: 40 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,15 @@
11
---
2-
title: Azure IoT Edge for Linux on Windows (EFLOW) with IoT Central | Microsoft Docs
3-
description: Learn how to connect Azure IoT Edge for Linux on Windows (EFLOW) with IoT Central
2+
title: Connect Azure IoT Edge for Linux on Windows (EFLOW)
3+
titleSuffix: IoT Central
4+
description: Learn how to connect an Azure IoT Edge for Linux on Windows (EFLOW) device to an IoT Central application
45
author: dominicbetts
56
ms.author: dobett
67
ms.date: 10/11/2022
78
ms.topic: how-to
89
ms.service: iot-central
910
---
1011

11-
# Azure IoT Edge for Linux on Windows (EFLOW) with IoT Central
12+
# Connect an IoT Edge for Linux on Windows device to IoT Central
1213

1314
[Azure IoT Edge for Linux on Windows (EFLOW)](/windows/iot/iot-enterprise/azure-iot-edge-for-linux-on-windows) lets you run Azure IoT Edge in a Linux container on your Windows device. In this article, you learn how to provision an EFLOW device and manage it from your IoT Central application.
1415

@@ -27,22 +28,23 @@ To complete the steps in this article, you need:
2728

2829
* An [IoT Central application created](howto-create-iot-central-application.md) from the **Custom application** template. To learn more, see [Create an IoT Central application](howto-create-iot-central-application.md).
2930

30-
* A Windows device with the following minimum requirements:
31+
* A Windows device that meets the following minimum requirements:
3132

3233
* Windows 10<sup>1</sup>/11 (Pro, Enterprise, IoT Enterprise) or Windows Server 2019<sup>1</sup>/2022
3334
* Minimum free memory: 1 GB
3435
* Minimum free disk space: 10 GB
35-
* <sup>1</sup> Windows 10 and Windows Server 2019 minimum build 17763 with all current cumulative updates installed.
3636

37-
To follow the steps in this article, download the [EnvironmentalSensorManifest.json](https://raw.githubusercontent.com/Azure-Samples/iot-central-docs-samples/main/iotedge/EnvironmentalSensorManifest.json) file to your computer.
37+
<sup>1</sup> Windows 10 and Windows Server 2019 minimum build 17763 with all current cumulative updates installed.
38+
39+
To follow the steps in this article, download the [EnvironmentalSensorManifest-1-4.json](https://raw.githubusercontent.com/Azure-Samples/iot-central-docs-samples/main/iotedge/EnvironmentalSensorManifest-1-4.json) file to your computer.
3840

3941
## Import a deployment manifest
4042

4143
You use a deployment manifest to specify the modules to run on an IoT Edge device. IoT Central manages the deployment manifests for the IoT Edge devices in your solution. To import the deployment manifest for this example:
4244

4345
1. In your IoT Central application, navigate to **Edge manifests**.
4446

45-
1. Select **+ New**. Enter a name such as *Environmental Sensor* for your deployment manifest, and then upload the *EnvironmentalSensorManifest.json* file you downloaded previously.
47+
1. Select **+ New**. Enter a name such as *Environmental Sensor* for your deployment manifest, and then upload the *EnvironmentalSensorManifest-1-4.json* file you downloaded previously.
4648

4749
1. Select **Next** and then **Create**.
4850

@@ -66,7 +68,7 @@ In this section, you create an IoT Central device template for an IoT Edge devic
6668

6769
1. Select the **management** interface in the **SimulatedTemperatureSensor** module to view the two properties defined in the manifest:
6870

69-
:::image type="content" source="media/howto-connect-eflow/imported-manifest.png" alt-text="Device template created from IoT Edge manifest.":::
71+
:::image type="content" source="media/howto-connect-eflow/imported-manifest.png" alt-text="Screenshot that shows the device template created from IoT Edge manifest.":::
7072

7173
### Add telemetry to the device template
7274

@@ -106,7 +108,7 @@ To add the telemetry definitions to the device template:
106108

107109
The **management** interface now includes the **machine**, **ambient**, and **timeCreated** telemetry types:
108110

109-
:::image type="content" source="media/howto-connect-eflow/manage-interface.png" alt-text="Interface with machine and ambient telemetry types.":::
111+
:::image type="content" source="media/howto-connect-eflow/manage-interface.png" alt-text="Screenshot that shows the interface with machine and ambient telemetry types.":::
110112

111113
### Add views to template
112114

@@ -140,7 +142,7 @@ Before you can connect a device to IoT Central, you must register the device in
140142

141143
You now have a new device with the status **Registered**:
142144

143-
:::image type="content" source="media/howto-connect-eflow/new-device.png" alt-text="New Device.":::
145+
:::image type="content" source="media/howto-connect-eflow/new-device.png" alt-text="Screenshot that shows the new IoT Edge device in the registered state.":::
144146

145147
### Get the device credentials
146148

@@ -158,49 +160,58 @@ You've now finished configuring your IoT Central application to enable an IoT Ed
158160

159161
## Install and provision an EFLOW device
160162

163+
To install and provision your EFLOW device:
164+
161165
1. In an elevated PowerShell session, run each of the following commands to download IoT Edge for Linux on Windows.
162166

163-
```powershell
164-
$msiPath = $([io.Path]::Combine($env:TEMP, 'AzureIoTEdge.msi'))
165-
$ProgressPreference = 'SilentlyContinue'
166-
Invoke-WebRequest "https://aka.ms/AzEflowMSI" -OutFile $msiPath
167-
```
167+
```powershell
168+
$msiPath = $([io.Path]::Combine($env:TEMP, 'AzureIoTEdge.msi'))
169+
$ProgressPreference = 'SilentlyContinue'
170+
Invoke-WebRequest "https://aka.ms/AzEFLOWMSI_1_4_LTS_X64" -OutFile $msiPath
171+
```
172+
173+
> [!TIP]
174+
> The previous commands download an X64 image, for ARM64 use `https://aka.ms/AzEFLOWMSI_1_4_LTS_ARM64`.
168175
169176
1. Install IoT Edge for Linux on Windows on your device.
170177
171-
```powershell
172-
Start-Process -Wait msiexec -ArgumentList "/i","$([io.Path]::Combine($env:TEMP, 'AzureIoTEdge.msi'))","/qn"
173-
```
178+
```powershell
179+
Start-Process -Wait msiexec -ArgumentList "/i","$([io.Path]::Combine($env:TEMP, 'AzureIoTEdge.msi'))","/qn"
180+
```
174181
175-
You can specify custom IoT Edge for Linux on Windows installation and VHDX directories by adding `INSTALLDIR="<FULLY_QUALIFIED_PATH>"` and `VHDXDIR="<FULLY_QUALIFIED_PATH>"` parameters to the install command.
182+
> [!TIP]
183+
> You can specify custom IoT Edge for Linux on Windows installation and VHDX directories by adding `INSTALLDIR="<FULLY_QUALIFIED_PATH>"` and `VHDXDIR="<FULLY_QUALIFIED_PATH>"` parameters to the install command.
176184
177185
1. Create the IoT Edge for Linux on Windows deployment. The deployment creates your Linux VM and installs the IoT Edge runtime for you.
178186
179-
```powershell
180-
Deploy-Eflow
181-
```
187+
```powershell
188+
Deploy-Eflow
189+
```
182190
183191
1. Use the **ID scope**, **Device ID** and the **Primary Key** you made a note of previously.
184192
185-
```powershell
186-
Provision-EflowVm -provisioningType DpsSymmetricKey -scopeId <ID_SCOPE_HERE> -registrationId <DEVCIE_ID_HERE> -symmKey <PRIMARY_KEY_HERE>
187-
```
193+
```powershell
194+
Provision-EflowVm -provisioningType DpsSymmetricKey -scopeId <ID_SCOPE_HERE> -registrationId <DEVCIE_ID_HERE> -symmKey <PRIMARY_KEY_HERE>
195+
```
188196
189197
To learn about other ways you can deploy and provision an EFLOW device, see [Install and provision Azure IoT Edge for Linux on a Windows device](../../iot-edge/how-to-install-iot-edge-on-windows.md).
190198
191199
Go to the **Device Details** page in your IoT Central application and you can see telemetry flowing from your EFLOW device:
192200
193-
:::image type="content" source="media/howto-connect-eflow/telemetry.png" alt-text="Telemetry from the device.":::
201+
:::image type="content" source="media/howto-connect-eflow/telemetry.png" alt-text="Screenshot that shows a plot of telemetry from the device.":::
202+
203+
> [!TIP]
204+
> You may need to wait several minutes for the IoT Edge device to start sending telemetry.
194205
195206
## Clean up resources
196207
197-
If you want to remove the Azure IoT Edge for Linux on Windows installation from your device, use the following commands.
208+
If you want to uninstall EFLOW from your device, use the following commands.
198209
199210
1. Open **Settings** on Windows
200211
1. Select **Add or Remove Programs**
201212
1. Select **Azure IoT Edge LTS** app
202213
1. Select **Uninstall**
203214
204-
## Next Steps
215+
## Next steps
205216
206-
Now that you've learned how to connect Azure IoT Edge for Linux on Windows (EFLOW) with IoT Central, the suggested next step is to learn how to [Connect devices through an IoT Edge transparent gateway](how-to-connect-iot-edge-transparent-gateway.md).
217+
Now that you've learned how to connect an (EFLOW) device to IoT Central, the suggested next step is to learn how to [Connect devices through an IoT Edge transparent gateway](how-to-connect-iot-edge-transparent-gateway.md).

0 commit comments

Comments
 (0)