Merge pull request #188264 from fcabrera23/eflow-fixes

Add memory even and uninstall options

Author: laurabren

articles/iot-edge/how-to-provision-devices-at-scale-linux-on-windows-symmetric.md

@@ -197,6 +197,9 @@ You can verify that the group enrollment that you created in device provisioning
 
 When you create a new IoT Edge device, it will display the status code `417 -- The device's deployment configuration is not set` in the Azure portal. This status is normal, and means that the device is ready to receive a module deployment.
 
+<!-- Uninstall IoT Edge for Linux on Windows H2 and content -->
+[!INCLUDE [uninstall-iot-edge-linux-on-windows.md](../../includes/iot-edge-uninstall-linux-on-windows.md)]
+
 ## Next steps
 
 The device provisioning service enrollment process lets you set the device ID and device twin tags at the same time as you provision the new device. You can use those values to target individual devices or groups of devices using automatic device management. Learn how to [Deploy and monitor IoT Edge modules at scale using the Azure portal](how-to-deploy-at-scale.md) or [using Azure CLI](how-to-deploy-cli-at-scale.md).

articles/iot-edge/how-to-provision-devices-at-scale-linux-on-windows-tpm.md

@@ -265,6 +265,9 @@ Use the following commands on your device to verify that the IoT Edge installed
 :::moniker-end
 <!-- end 1.2 -->
 
+<!-- Uninstall IoT Edge for Linux on Windows H2 and content -->
+[!INCLUDE [uninstall-iot-edge-linux-on-windows.md](../../includes/iot-edge-uninstall-linux-on-windows.md)]
+
 ## Next steps
 
 The device provisioning service enrollment process lets you set the device ID and device twin tags at the same time as you provision the new device. You can use those values to target individual devices or groups of devices by using automatic device management.

articles/iot-edge/how-to-provision-devices-at-scale-linux-on-windows-x509.md

@@ -224,6 +224,9 @@ You can verify that the group enrollment that you created in device provisioning
 
 When you create a new IoT Edge device, it will display the status code `417 -- The device's deployment configuration is not set` in the Azure portal. This status is normal, and means that the device is ready to receive a module deployment.
 
+<!-- Uninstall IoT Edge for Linux on Windows H2 and content -->
+[!INCLUDE [uninstall-iot-edge-linux-on-windows.md](../../includes/iot-edge-uninstall-linux-on-windows.md)]
+
 ## Next steps
 
 The device provisioning service enrollment process lets you set the device ID and device twin tags at the same time as you provision the new device. You can use those values to target individual devices or groups of devices using automatic device management. Learn how to [Deploy and monitor IoT Edge modules at scale using the Azure portal](how-to-deploy-at-scale.md) or [using Azure CLI](how-to-deploy-cli-at-scale.md).

articles/iot-edge/how-to-provision-single-device-linux-on-windows-symmetric.md

@@ -201,6 +201,9 @@ Verify that IoT Edge for Linux on Windows was successfully installed and configu
 
 When you create a new IoT Edge device, it will display the status code `417 -- The device's deployment configuration is not set` in the Azure portal. This status is normal, and means that the device is ready to receive a module deployment.
 
+<!-- Uninstall IoT Edge for Linux on Windows H2 and content -->
+[!INCLUDE [uninstall-iot-edge-linux-on-windows.md](../../includes/iot-edge-uninstall-linux-on-windows.md)]
+
 ## Next steps
 
 * Continue to [deploy IoT Edge modules](how-to-deploy-modules-portal.md) to learn how to deploy modules onto your device.

articles/iot-edge/how-to-provision-single-device-linux-on-windows-x509.md

@@ -211,6 +211,9 @@ Verify that IoT Edge for Linux on Windows was successfully installed and configu
 
 When you create a new IoT Edge device, it will display the status code `417 -- The device's deployment configuration is not set` in the Azure portal. This status is normal, and means that the device is ready to receive a module deployment.
 
+<!-- Uninstall IoT Edge for Linux on Windows H2 and content -->
+[!INCLUDE [uninstall-iot-edge-linux-on-windows.md](../../includes/iot-edge-uninstall-linux-on-windows.md)]
+
 ## Next steps
 
 * Continue to [deploy IoT Edge modules](how-to-deploy-modules-portal.md) to learn how to deploy modules onto your device.

articles/iot-edge/reference-iot-edge-for-linux-on-windows-functions.md

@@ -116,7 +116,7 @@ The **Deploy-Eflow** command is the main deployment method. The deployment comma
 | acceptEula | **Yes** or **No** | A shortcut to accept/deny EULA and bypass the EULA prompt. |
 | acceptOptionalTelemetry | **Yes** or **No** |  A shortcut to accept/deny optional telemetry and bypass the telemetry prompt. |
 | cpuCount | Integer value between 1 and the device's CPU cores |  Number of CPU cores for the VM.<br><br>**Default value**: 1 vCore. |
-| memoryInMB | Integer value between 1024 and the maximum amount of free memory of the device |Memory allocated for the VM.<br><br>**Default value**: 1024 MB. |
+| memoryInMB | Integer **even** value between 1024 and the maximum amount of free memory of the device |Memory allocated for the VM.<br><br>**Default value**: 1024 MB. |
 | vmDiskSize | Between 8 GB and 2 TB | Maximum logical disk size of the dynamically expanding virtual hard disk.<br><br>**Default value**: 16 GB. |
 | vswitchName | Name of the virtual switch |  Name of the virtual switch assigned to the EFLOW VM. |
 | vswitchType | **Internal** or **External** | Type of the virtual switch assigned to the EFLOW VM. |
@@ -136,7 +136,7 @@ The **Deploy-Eflow** command is the main deployment method. The deployment comma
 | acceptEula | **Yes** or **No** | A shortcut to accept/deny EULA and bypass the EULA prompt. |
 | acceptOptionalTelemetry | **Yes** or **No** |  A shortcut to accept/deny optional telemetry and bypass the telemetry prompt. |
 | cpuCount | Integer value between 1 and the device's CPU cores |  Number of CPU cores for the VM.<br><br>**Default value**: 1 vCore. |
-| memoryInMB | Integer value between 1024 and the maximum amount of free memory of the device |Memory allocated for the VM.<br><br>**Default value**: 1024 MB. |
+| memoryInMB | Integer **even** value between 1024 and the maximum amount of free memory of the device |Memory allocated for the VM.<br><br>**Default value**: 1024 MB. |
 | vmDiskSize | Between 21 GB and 2 TB | Maximum logical disk size of the dynamically expanding virtual hard disk.<br><br>**Default value**: 29 GB. <br><br>**Note**: Either _vmDiskSize_ or _vmDataSize_ can be used, but not both together. |
 | vmDataSize | Between 2 GB and 2 TB | Maximum data partition size of the resulting hard disk, in GB.<br><br>**Default value**: 10 GB. <br><br>**Note**: Either _vmDiskSize_ or _vmDataSize_ can be used, but not both together. |
 | vmLogSize | **Small** or **Large** | Specificy the log partition size. Small = 1GB, Large = 6GB.<br><br>**Default value**: Small.  |

includes/iot-edge-install-linux-on-windows.md

@@ -126,7 +126,7 @@ Install Azure IoT Edge for Linux on Windows on your device.
    | Setting | Default value |
    | ------- | ------------- |
    | Virtual disk size in GB | 16 |
-   | Memory in MB | 1024 |
+   | Memory in MB **(even number)** | 1024 |
    | Number of cores | 2 |
    | Azure IoT Edge version | 1.1 (LTS) |
 

includes/iot-edge-uninstall-linux-on-windows.md

@@ -0,0 +1,33 @@
+---
+ms.topic: include
+ms.date: 02/10/2022
+author: fcabrera
+ms.author: fcabrera
+ms.service: iot-edge
+services: iot-edge
+---
+
+## Uninstall IoT Edge for Linux on Windows
+
+If you want to remove the Azure IoT Edge for Linux on Windows installation from your device, use the following commands.
+
+<!-- 1.1 -->
+:::moniker range="iotedge-2018-06"
+
+1. Open Settings on Windows
+2. Select Add or Remove Programs
+3. Select _Azure IoT Edge LTS_ app
+4. Select Uninstall
+
+:::moniker-end
+<!-- end 1.1 -->
+
+<!-- 1.2 -->
+:::moniker range=">=iotedge-2020-11"
+
+1. Open Settings on Windows
+2. Select Add or Remove Programs
+3. Select _Azure IoT Edge_ app
+4. Select Uninstall
+:::moniker-end
+<!-- end 1.2 -->