Merge pull request #303302 from habibaum/25Jul-vmware-updates

VMware doc updates

Author: JillGrant615

articles/migrate/media/tutorial-migrate-vmware/appliance-name.png

@@ -140,14 +140,62 @@ Enable replication as follows:
 ## Track and monitor
 
 1. Track job status in the portal notifications.
-2. Monitor replication status by selecting on the numerical value next to **Azure VM** in **Migration and modernization**.
+2. Monitor replication status by selecting on the numerical value next to **Azure VM** in **Migration and modernization**. 
 
-     ![Monitor replication](./media/tutorial-migrate-vmware/replicating-servers.png)
+![Screenshot that shows monitor replication.](./media/tutorial-migrate-vmware/replicating-servers.png)
 
-Replication occurs as follows:
-- When the Start Replication job finishes successfully, the machines begin their initial replication to Azure.
-- During initial replication, a VM snapshot is created. Disk data from the snapshot is replicated to replica managed disks in Azure.
-- After initial replication finishes, delta replication begins. Incremental changes to on-premises disks are periodically replicated to the replica disks in Azure.
+Replication occurs as follows: <br /><br />
+- When the Start Replication job finishes successfully, the machines begin their initial replication to Azure. <br /><br />
+- During initial replication, a VM snapshot is created. Disk data from the snapshot is replicated to replica managed disks in Azure. <br /><br />
+- After initial replication finishes, delta replication begins. Incremental changes to on-premises disks are periodically replicated to the replica disks in Azure. <br /><br />
+
+3. Use PowerShell to view **Time Remaining** across **all stages of server migration** in Azure Migrate. This helps you monitor replication progress and plan cutover accurately.
+4. Open the **Azure portal**, then select the **Cloud Shell** at the top. Select **PowerShell** when prompted.
+5. Run this command in Azure Cloud Shell to monitor the migration status of the server you need.
+
+    ```powershell
+    
+    Get-AzMigrateServerMigrationStatus -ProjectName "<your-project-name>"   -ResourceGroupName "<your-resource-group>" -MachineName "<your-server-name>"
+
+    ```
+6. Replace `your-project-name`, `your-resource-group`, and `your-server-name` with the actual Azure Migrate project, resource group, and server name.
+7. You run this command and get the following output: 
+
+    :::image type="content" source="./media/tutorial-migrate-vmware/run-command.png" alt-text="Screenshot shows the output when you run the command." lightbox="./media/tutorial-migrate-vmware/run-command.png":::
+
+8. The output shows the server replication status, disk progress, time left, upload speed, and datastore details.
+9. You can run the command without `-MachineName` to view migration status and time remaining for all servers in the project. For example: 
+
+    ```powershell
+
+    Get-AzMigrateServerMigrationStatus -ProjectName "<your-project-name>" -ResourceGroupName "<your-resource-group>"
+    ```
+
+10. Replace `your-project-name` and `your-resource-group` with the actual Azure Migrate project and resource group names.
+11. You run this command and get the following output: <br /><br />
+
+    :::image type="content" source="./media/tutorial-migrate-vmware/replication-status.png"alt-text="Screenshot shows the overall replication status. "lightbox="./media/tutorial-migrate-vmware/replication-status.png":::
+
+12. If there is a problem with replication or cutover, the `-Health` flag shows **errors,   possible causes, and recommended actions** to troubleshoot the migration.
+
+```powershell
+    
+Get-AzMigrateServerMigrationStatus   -ProjectName "<your-project-name>"   -ResourceGroupName "<your-resource-group>"   -MachineName "<your-server-name>" -Health
+```
+13. You run this command and get the following output: <br /><br />
+
+:::image type="content" source="./media/tutorial-migrate-vmware/replication-complete.png" alt-text="Screenshot shows the replication complete status." lightbox="./media/tutorial-migrate-vmware/replication-complete.png":::
+
+14. You can also run the command with only `-ApplianceName` to view the migration status, time remaining, and health details for **all servers connected to that appliance**.
+
+```powershell
+ Get-AzMigrateServerMigrationStatus -ProjectName "<your-project-name>"   -ResourceGroupName "<your-resource-group>" -ApplianceName "<your-appliance-
+ ```
+15. Replace `your-project-name`, `your-resource-group`, and `your-appliance-name` with the actual values from your Azure Migrate setup.
+
+16. You run this command to get the following output: <br /><br />
+
+:::image type="content" source="./media/tutorial-migrate-vmware/appliance-name.png" alt-text="Screenshot shows azure migrate server migration status." lightbox="./media/tutorial-migrate-vmware/appliance-name.png":::
 
 ## Run a test migration
 
@@ -168,7 +216,7 @@ Do a test migration as follows:
     :::image type="content" source="./media/tutorial-migrate-vmware/test-migrate-inline.png" alt-text="Screenshot of Test migration." lightbox="./media/tutorial-migrate-vmware/test-migrate-expanded.png":::
 
 3. In **Test migration**, select the Azure VNet in which the Azure VM will be located during testing. We recommend you use a non-production VNet. 
-4. Choose the subnet to which you would like to associate each of the Network Interface Cards (NICs) of the migrated VM.
+4. Select the subnet to which you would like to associate each of the Network Interface Cards (NICs) of the migrated VM.
 
     :::image type="content" source="./media/tutorial-migrate-vmware/test-migration-subnet-selection.png" alt-text="Screenshot shows subnet selection during test migration.":::
 1. You have an option to upgrade the Windows Server OS during test migration. To upgrade, select the **Upgrade available** option. In the pane that appears, select the target OS version that you want to upgrade to and select **Apply**. [Learn more](./how-to-upgrade-windows.md).