Skip to content

Commit fa39dc3

Browse files
committed
Add more information about autconfirm
1 parent 1a3794e commit fa39dc3

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/iot-edge/iot-edge-for-linux-on-windows-updates.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -130,13 +130,13 @@ To migrate between EFLOW 1.1LTS to EFLOW 1.4LTS, use the following steps.
130130
131131
1. Get the latest Azure EFLOW 1.1LTS [(1.1.2112.1212.1)](https://aka.ms/AzEFLOWMSI-1_1_2212_12122) update. If you're using Windows Update, *Check Updates* to get the latest EFLOW update.
132132
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.
133-
1. [1.4.2.12122 Standalone MSI](https://aka.ms/AzEFLOW-Update-1_1-to-1_4_SA)
134-
1. [1.4.2.12122 Update MIS](https://aka.ms/AzEFLOW-Update-1_1-to-1_4_Update)
133+
- [1.4.2.12122 Standalone MSI](https://aka.ms/AzEFLOW-Update-1_1-to-1_4_SA)
134+
- [1.4.2.12122 Update MIS](https://aka.ms/AzEFLOW-Update-1_1-to-1_4_Update)
135135
1. Open an elevated PowerShell session
136136
1. Start the EFLOW migration
137137
138138
>[!NOTE]
139-
>You can migrate with one single cmdlet by using the `-autoConfirm` flag. If specified Confirm-EflowMigration doesnt needs to be called to proceed with 1.4 migration.
139+
>You can migrate with one single cmdlet by using the `-autoConfirm` flag with the ` Start-EflowMigration` cmdlet. If specified `Confirm-EflowMigration` doesnt needs to be called to proceed with 1.4 migration.
140140
141141
1. If you're using the auto-download migration option run the following cmdlet
142142
```powershell

0 commit comments

Comments
 (0)