Merge pull request #278771 from v-sreedevank/20Jun-VMwareChanges

Updates and fixes

Author: ttorble

articles/migrate/common-questions-appliance.md

@@ -7,7 +7,7 @@ ms.manager: abhemraj
 ms.service: azure-migrate
 ms.topic: conceptual
 ms.custom: engagement-fy24
-ms.date: 05/02/2024
+ms.date: 06/20/2024
 ---
 
 # Azure Migrate appliance: Common questions
@@ -111,6 +111,10 @@ A project can have multiple appliances registered to it. However, one appliance
 1. In the Azure Migrate project, select **Overview** from the Azure Migrate: Discovery & assessment.
 1. In **Overview**, select **Appliances** in left menu to see the appliances registered with the project and the connectivity status of the agents on the appliance.
 
+## Can I change the Azure user account from the Azure Migrate appliance once registered with the project?
+If you registered the appliance to Migrate project using a particular user account, it cannot be changed. You can try re-registering the appliance with the new project using another user account via PowerShell script but it will break all the operations in the old project.
+
+
 ## Can the Azure Migrate appliance/Replication appliance connect to the same vCenter?
 
 Yes. You can add both the Azure Migrate appliance (used for assessment and agentless VMware migration), and the replication appliance (used for agent-based migration of servers running in VMware) to the same vCenter server. But make sure that you are not setting up both appliances on the same server and that is currently not supported.

articles/migrate/how-to-scale-out-for-migration.md

@@ -6,7 +6,7 @@ ms.author: ajaypar
 ms.manager: roopesh.nair
 ms.service: azure-migrate
 ms.topic: how-to
-ms.date: 03/12/2024
+ms.date: 06/20/2024
 ms.custom: engagement-fy24
 ---
 
@@ -141,25 +141,28 @@ In the configuration manager, select **Set up prerequisites**, and then complete
 
         After the appliance is successfully registered, to see the registration details, select **View details**.
 
-         #### Import appliance configuration from primary appliance
+#### Import appliance configuration from primary appliance
 
-         To complete the registration of the scale-out appliance, click **import** to get the necessary configuration files from the primary appliance.
+To complete the registration of the scale-out appliance, click **import** to get the necessary configuration files from the primary appliance.
 
-         1. Clicking **import** opens a pop-up window with instructions on how to import the necessary configuration files from the primary appliance.
+1. Clicking **import** opens a pop-up window with instructions on how to import the necessary configuration files from the primary appliance.
 
-            :::image type="content" source="./media/how-to-scale-out-for-migration/import-modal-scale-out.png" alt-text="Screenshot of the Import Configuration files modal.":::
+    :::image type="content" source="./media/how-to-scale-out-for-migration/import-modal-scale-out.png" alt-text="Screenshot of the Import Configuration files modal.":::
 
-         1. Login (remote desktop) to the primary appliance and execute the following PowerShell commands:
+1. Login (remote desktop) to the primary appliance and execute the following PowerShell commands:
 
-            `PS cd 'C:\Program Files\Microsoft Azure Appliance Configuration Manager\Scripts\PowerShell' `
+    `PS cd 'C:\Program Files\Microsoft Azure Appliance Configuration Manager\Scripts\PowerShell' `
 
-            `PS .\ExportConfigFiles.ps1 `
+    `PS .\ExportConfigFiles.ps1 `
 
-         1. Copy the zip file created by running the above commands to the scale-out appliance. The zip file contains configuration files needed to register the scale-out appliance.
+    > [!Note] 
+    > Install PowerShell 7.x in the appliance and execute the script ExportConfigFiles.ps1. The script execution is only supported with PowerShell 7.x. 
 
-         1. In the pop-up window opened in the previous step, select the location of the copied configuration zip file and click **Save**.
+1. Copy the zip file created by running the above commands to the scale-out appliance. The zip file contains configuration files needed to register the scale-out appliance.
 
-         Once the files have been successfully imported, the registration of the scale-out appliance will complete and it will show you the timestamp of the last successful import. You can also see the registration details by clicking **View details**.
+1. In the pop-up window opened in the previous step, select the location of the copied configuration zip file and click **Save**.
+
+    Once the files have been successfully imported, the registration of the scale-out appliance will complete and it will show you the timestamp of the last successful import. You can also see the registration details by clicking **View details**.
 1. **Install the VDDK**: The appliance checks that VMware vSphere Virtual Disk Development Kit (VDDK) is installed. If the VDDK isn't installed, download VDDK 6.7 from VMware. Extract the downloaded zip file contents to the specified location on the appliance, as indicated in the *Installation instructions*.
 
     The Migration and modernization tool uses the VDDK to replicate servers during migration to Azure.

articles/migrate/toc.yml

@@ -186,7 +186,7 @@ items:
           href: prepare-for-agentless-migration.md
     - name: Hyper-V migration architecture
       href: hyper-v-migration-architecture.md
-    - name: VMware agent-based migration architecture
+    - name: VMware/Physical agent-based migration architecture
       href: agent-based-migration-architecture.md
     - name: Web apps migration support
       href: concepts-migration-webapps.md

articles/migrate/vmware/how-to-set-up-appliance-vmware.md

@@ -6,7 +6,7 @@ ms.author: vibansa
 ms.manager: abhemraj
 ms.topic: how-to
 ms.service: azure-migrate
-ms.date: 04/19/2024
+ms.date: 06/20/2024
 ms.custom: vmware-scenario-422, engagement-fy23
 ---
 
@@ -35,6 +35,9 @@ To set up the appliance by using an OVA template, you'll complete these steps, w
 > [!NOTE]
 > OVA templates are not available for soverign clouds.
 
+> [!NOTE]
+> Do not clone or create a VM template out of an appliance deployed using OVA template. This scenario is unsupported and may result in deployment failures within the Migrate Service.
+
 1. Provide an appliance name and generate a project key in the portal.
 1. Download an OVA template file, and import it to vCenter Server. Verify that the OVA is secure.
 1. Create the appliance from the OVA file. Verify that the appliance can connect to Azure Migrate.

articles/migrate/vmware/toc.yml

@@ -33,7 +33,7 @@ items:
     items:
   - name: Agent-based migration
     items:
-    - name: VMware agent-based migration architecture
+    - name: VMware/Physical agent-based migration architecture
       href: agent-based-migration-architecture.md
     - name: Migrate VMware vSphere VMs with agent-based migration
       href: tutorial-migrate-vmware-agent.md