Merge pull request #225727 from v-ksreedevan/31Jan-VDDK

v-ccolin · web-flow · commit e7304e88c711 · 2023-01-31T11:02:06.000Z
VDDK Version update
diff --git a/articles/migrate/how-to-set-up-appliance-vmware.md b/articles/migrate/how-to-set-up-appliance-vmware.md
@@ -5,7 +5,7 @@ author: vikram1988
 ms.author: vibansa
 ms.manager: abhemraj
 ms.topic: how-to
-ms.date: 12/12/2022
+ms.date: 01/31/2023
 ms.custom: engagement-fy23
 ---
 
@@ -17,19 +17,19 @@ The [Azure Migrate appliance](migrate-appliance.md) is a lightweight appliance t
 
 ## Set up the appliance
 
-You can deploy the Azure Migration appliance by using a couple of methods:
+You can deploy the Azure Migration appliance using these methods:
 
-- Create a server on a vCenter Server VM by using a downloaded OVA template. This method is described in this article.
+- Create a server on a vCenter Server VM using a downloaded OVA template. This method is described in this article.
 - Set up the appliance on an existing server by using a PowerShell installer script. You should [run a PowerShell script](deploy-appliance-script.md) if you can't use an OVA template or if you're in Azure Government.
 
-After you create the appliance, you check that the appliance can connect to Azure Migrate: Discovery and assessment, register the appliance with the project, and configure the appliance to start discovery.
+After you create the appliance, check if the appliance can connect to Azure Migrate: Discovery and assessment, register the appliance with the project, and configure the appliance to start discovery.
 
 ### Deploy by using an OVA template
 
-To set up the appliance by using an OVA template, you'll complete these steps, which are described in more detail in this section:
+To set up the appliance by using an OVA template, you'll complete these steps, which are described in detail in this section:
 
 1. Provide an appliance name and generate a project key in the portal.
-1. Download an OVA template file, and then import it to vCenter Server. Verify that the OVA is secure.
+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.
 1. Configure the appliance for the first time. 
 1. Register the appliance with the project by using the project key.
@@ -45,7 +45,7 @@ To set up the appliance by using an OVA template, you'll complete these steps, w
 
 #### Download the OVA template
 
-In **2: Download Azure Migrate appliance**, select the OVA file, and then select **Download**.
+In **2: Download Azure Migrate appliance**, select the OVA file, and select **Download**.
 
 ##### Verify security
 
@@ -58,22 +58,25 @@ Before you deploy the OVA file, verify that the file is secure:
     C:\>CertUtil -HashFile <file_location> <hashing_agorithm>
     ```
    
-    Example: `C:\>CertUtil -HashFile C:\Users\Administrator\Desktop\MicrosoftAzureMigration.ova SHA256`
+    For example: 
+    ```bash
+    C:\>CertUtil -HashFile C:\Users\Administrator\Desktop\MicrosoftAzureMigration.ova SHA256
+    ```
 
 1. Verify the latest hash value by comparing the outcome of above command to the value documented [here](./tutorial-discover-vmware.md#verify-security).
 
 #### Create the appliance server
 
-Import the downloaded file, and then create a server in the VMware environment:
+Import the downloaded file, and create a server in the VMware environment:
 
 1. In the vSphere Client console, select **File** > **Deploy OVF Template**.
-1. In the Deploy OVF Template Wizard, select **Source**, and then enter the location of the OVA file.
+1. In the **Deploy OVF Template** Wizard, select **Source**, and enter the location of the OVA file.
 1. In **Name**, enter a name for the server. In **Location**, select the inventory object in which the server will be hosted.
 1. In **Host/Cluster**, select the host or cluster on which the server will run.
 1. In **Storage**, select the storage destination for the server.
 1. In **Disk Format**, select the disk type and size.
 1. In **Network Mapping**, select the network the server will connect to. The network requires internet connectivity to send metadata to Azure Migrate.
-1. Review and confirm the settings, and then select **Finish**.
+1. Review and confirm the settings, and select **Finish**.
 
 #### Verify appliance access to Azure
 
@@ -88,22 +91,22 @@ To set up the appliance for the first time:
 > [!NOTE]
 > If you set up the appliance by using a [PowerShell script](deploy-appliance-script.md) instead of a downloaded OVA template, you can skip the first two steps.
 
-1. In vSphere Client, right-click the server, and then select **Open Console**.
+1. In vSphere Client, right-click the server, and select **Open Console**.
 1. Select or enter the language, time zone, and password for the appliance.
-1. Open a browser on any server that can connect to the appliance server. Then, open the URL of the appliance configuration manager: `https://appliance name or IP address: 44368`.
+1. Open a browser on any server that can connect to the appliance server. Navigate to the URL of the appliance configuration manager: `https://appliance name or IP address: 44368`.
 
      Or, you can open the configuration manager from the appliance server desktop by selecting the shortcut for the configuration manager.
 1. Accept the license terms and read the third-party information.
 
 #### Set up prerequisites and register the appliance
 
-In the configuration manager, select **Set up prerequisites**, and then complete these steps:
+In the configuration manager, select **Set up prerequisites**, and complete these steps:
 1. **Connectivity**: The appliance checks that the server has internet access. If the server uses a proxy:
     - Select **Setup proxy** to specify the proxy address (in the form `http://ProxyIPAddress` or `http://ProxyFQDN`, where *FQDN* refers to a *fully qualified domain name*) and listening port.
-    - Enter credentials if the proxy needs authentication.
+    - Enter the credentials if the proxy needs authentication.
     - If you have added proxy details or disabled the proxy or authentication, select **Save** to trigger connectivity and check connectivity again.
-    
-        Only HTTP proxy is supported.
+        > [!NOTE]
+        > Only HTTP proxy is supported.
 1. **Time sync**: Check that the time on the appliance is in sync with internet time for discovery to work properly.
 1. **Install updates and register appliance**: To run auto-update and register the appliance, follow these steps:
 
@@ -112,19 +115,19 @@ In the configuration manager, select **Set up prerequisites**, and then complete
     > [!NOTE]
     > This is a new user experience in Azure Migrate appliance which is available only if you have set up an appliance using the latest OVA/Installer script downloaded from the portal. The appliances which have already been registered will continue seeing the older version of the user experience and will continue to work without any issues.
 
-    1. For the appliance to run auto-update, paste the project key that you copied from the portal. If you don't have the key, go to **Azure Migrate: Discovery and assessment** > **Overview** > **Manage existing appliances**. Select the appliance name you provided when you generated the project key, and then copy the key that's shown.
+    1. For the appliance to run auto-update, paste the project key that you copied from the portal. If you don't have the key, go to **Azure Migrate: Discovery and assessment** > **Overview** > **Manage existing appliances**. Select the appliance name you provided when you generated the project key, and copy the key that's shown.
 	2. The appliance will verify the key and start the auto-update service, which updates all the services on the appliance to their latest versions. When the auto-update has run, you can select **View appliance services** to see the status and versions of the services running on the appliance server.
-    3. To register the appliance, you need to select **Login**. In **Continue with Azure Login**, select **Copy code & Login** to copy the device code (you must have a device code to authenticate with Azure) and open an Azure Login prompt in a new browser tab. Make sure you've disabled the pop-up blocker in the browser to see the prompt.
+    3. To register the appliance, you need to select **Login**. In **Continue with Azure Login**, select **Copy code & Login** to copy the device code (you must have a device code to authenticate with Azure) and open an Azure sign-in prompt in a new browser tab. Make sure you've disabled the pop-up blocker in the browser to see the prompt.
     
-        :::image type="content" source="./media/tutorial-discover-vmware/device-code.png" alt-text="Screenshot that shows where to copy the device code and log in.":::
+        :::image type="content" source="./media/tutorial-discover-vmware/device-code.png" alt-text="Screenshot that shows where to copy the device code and sign in.":::
     4. In a new tab in your browser, paste the device code and sign in by using your Azure username and password. Signing in with a PIN isn't supported.
 	    > [!NOTE]
         > If you close the login tab accidentally without logging in, refresh the browser tab of the appliance configuration manager to display the device code and Copy code & Login button.
-	5. After you successfully log in, return to the browser tab that displays the appliance configuration manager. If the Azure user account that you used to log in has the required permissions for the Azure resources that were created during key generation, appliance registration starts.
+	5. After you successfully sign in, return to the browser tab that displays the appliance configuration manager. If the Azure user account that you used to sign in has the required permissions for the Azure resources that were created during key generation, appliance registration starts.
 
-        After the appliance is successfully registered, to see the registration details, select **View details**.
+        After the appliance is successfully registered, select **View details** to see the registration 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, the default path is *C:\Program Files\VMware\VMware Virtual Disk Development Kit* as indicated in the *Installation instructions*.
+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 or 7.0 from VMware. Extract the downloaded zip file contents to the specified location on the appliance, the default path is *C:\Program Files\VMware\VMware Virtual Disk Development Kit* as indicated in the *Installation instructions*.
 
     The Migration and modernization tool uses the VDDK to replicate servers during migration to Azure.
 
@@ -141,10 +144,10 @@ The appliance must connect to vCenter Server to discover the configuration and p
 1. In **Step 1: Provide vCenter Server credentials**, select **Add credentials** to enter a name for the credentials. Add the username and password for the vCenter Server account that the appliance will use to discover servers running on vCenter Server.
     - You should have set up an account with the required permissions as described earlier in this article.
     - If you want to scope discovery to specific VMware objects (vCenter Server datacenters, clusters, hosts, folders of clusters or hosts, or individual servers), review the instructions to [set discovery scope](set-discovery-scope.md) to restrict the account that Azure Migrate uses.
-    - If you want to add multiple credentials at once, click on **Add more** to save and add more credentials. Multiple credentials are supported for discovery of servers across multiple vCenter Servers using a single appliance.
-1. In **Step 2: Provide vCenter Server details**, select **Add discovery source** to add the IP address or FQDN of a vCenter Server. You can leave the port as the default (443) or specify a custom port on which vCenter Server listens. Select the friendly name for credentials you would like to map to the vCenter Server and click **Save**.
+    - If you want to add multiple credentials at once, select **Add more** to save and add more credentials. Multiple credentials are supported for discovery of servers across multiple vCenter Servers using a single appliance.
+1. In **Step 2: Provide vCenter Server details**, select **Add discovery source** to add the IP address or FQDN of a vCenter Server. You can leave the port as the default (443) or specify a custom port on which vCenter Server listens. Select the friendly name for credentials you would like to map to the vCenter Server and select **Save**.
 
-    Click on **Add more** to save the previous details and add more vCenter Server details. **You can add up to 10 vCenter Servers per appliance.**
+    Select on **Add more** to save the previous details and add more vCenter Server details. **You can add up to 10 vCenter Servers per appliance.**
 
     :::image type="content" source="./media/tutorial-discover-vmware/add-discovery-source.png" alt-text="Screenshot that allows to add more vCenter Server details.":::
 
@@ -175,14 +178,14 @@ To add server credentials:
 
     If you choose to use domain credentials, you also must enter the FQDN for the domain. The FQDN is required to validate the authenticity of the credentials with the Active Directory instance in that domain.
 1. Review the [required permissions](add-server-credentials.md#required-permissions) on the account for Step 3: Provide server credentials to perform software inventory, agentless dependency analysis, discovery of SQL Server instances and databases and discovery of ASP.NET web apps.
-1. To add multiple credentials at once, select **Add more** to save credentials, and then add more credentials.
+1. To add multiple credentials at once, select **Add more** to save credentials, and add more credentials.
     When you select **Save** or **Add more**, the appliance validates the domain credentials with the domain's Active Directory instance for authentication. Validation is made after each addition to avoid account lockouts as the appliance iterates to map credentials to respective servers.
 
 To check validation of the domain credentials:
 
 In the configuration manager, in the credentials table, see the **Validation status** for domain credentials. Only domain credentials are validated.
 
-If validation fails, you can select a **Failed** status to see the validation error. Fix the issue, and then select **Revalidate credentials** to reattempt validation of the credentials.
+If validation fails, you can select a **Failed** status to see the validation error. Fix the issue, and select **Revalidate credentials** to reattempt validation of the credentials.
 
 :::image type="content" source="./media/tutorial-discover-vmware/add-server-credentials-multiple.png" alt-text="Screenshot that shows providing and validating multiple credentials.":::
 
@@ -207,8 +210,8 @@ To start vCenter Server discovery, in **Step 3: Provide server credentials to pe
 
 * It takes approximately 20-25 minutes for the discovery of servers across 10 vCenter Servers added to a single appliance.
 * If you have provided server credentials, software inventory (discovery of installed applications) is automatically initiated when the discovery of servers running on vCenter Server(s) is finished. Software inventory occurs once every 12 hours.
-* [Software inventory](how-to-discover-applications.md) identifies the SQL Server instances that are running on the servers. Using the information it collects, the appliance attempts to connect to the SQL Server instances through the Windows authentication credentials or the SQL Server authentication credentials that are provided on the appliance. Then, it gathers data on SQL Server databases and their properties. The SQL Server discovery is performed once every 24 hours.
-* [Software inventory](how-to-discover-applications.md) identifies the web server role on the servers. Using the information it collects, the appliance attempts to connect to the IIS web server through the Windows authentication credentials that are provided on the appliance. Then, it gathers data on web apps. The web app discovery is performed once every 24 hours.
+* [Software inventory](how-to-discover-applications.md) identifies the SQL Server instances that are running on the servers. Using the information it collects, the appliance attempts to connect to the SQL Server instances through the Windows authentication credentials or the SQL Server authentication credentials that are provided on the appliance. It gathers data on SQL Server databases and their properties. The SQL Server discovery is performed once every 24 hours.
+* [Software inventory](how-to-discover-applications.md) identifies the web server role on the servers. Using the information it collects, the appliance attempts to connect to the IIS web server through the Windows authentication credentials that are provided on the appliance. It gathers data on web apps. The web app discovery is performed once every 24 hours.
 * Discovery of installed applications might take longer than 15 minutes. The duration depends on the number of discovered servers. For 500 servers, it takes approximately one hour for the discovered inventory to appear in the Azure Migrate project in the portal.
 * During software inventory, the added server credentials are iterated against servers and validated for agentless dependency analysis. When the discovery of servers is finished, in the portal, you can enable agentless dependency analysis on the servers. Only the servers on which validation succeeds can be selected to enable agentless dependency analysis.
 * SQL Server instances and databases data and web apps data begin to appear in the portal within 24 hours after you start discovery.
