Merge pull request #105412 from Vikram1988/migrateGA

PRMerger19 · web-flow · commit fc7d3caaedaa · 2020-02-24T23:53:20.000-08:00
Changes to the appliance related articles and VMware migration privil…
diff --git a/articles/migrate/how-to-set-up-appliance-hyper-v.md b/articles/migrate/how-to-set-up-appliance-hyper-v.md
@@ -44,12 +44,8 @@ Check that the zipped file is secure, before you deploy it.
 2. Run the following command to generate the hash for the VHD
     - ```C:\>CertUtil -HashFile <file_location> [Hashing Algorithm]```
     - Example usage: ```C:\>CertUtil -HashFile C:\AzureMigrate\AzureMigrate.vhd SHA256```
-3.  For appliance version 2.19.11.12, the generated hash should match these settings.
+3.  For appliance version 2.19.11.12, the generated hash should match these [settings](https://docs.microsoft.com/azure/migrate/tutorial-assess-hyper-v#verify-security).
 
-  **Algorithm** | **Hash value**
-  --- | ---
-  MD5 | 29a7531f32bcf69f32d964fa5ae950bc
-  SHA256 | 37b3f27bc44f475872e355f04fcb8f38606c84534c117d1609f2d12444569b31
 
 
 
diff --git a/articles/migrate/how-to-set-up-appliance-physical.md b/articles/migrate/how-to-set-up-appliance-physical.md
@@ -13,9 +13,6 @@ ms.author: raynew
 
 This article describes how to set up the Azure Migrate appliance if you're assessing physical servers with the Azure Migrate: Server Assessment tool.
 
-> [!NOTE]
-> If features are mentioned here that you don't yet see in the Azure Migrate portal, hang on. They will appear over the next week or so.
-
 The Azure Migrate appliance is a lightweight appliance, used by Azure Migrate Server Assessment to do the following:
 
 - Discover on-premises servers.
@@ -40,7 +37,7 @@ Download the zipped file for the appliance.
 2. In **Discover machines** > **Are your machines virtualized?**, click **Not virtualized/Other**.
 3. Click **Download** to download the zipped file.
 
-    ![Download VM](./media/how-to-set-up-appliance-hyper-v/download-appliance-hyperv.png)
+    ![Download VM](./media/tutorial-assess-physical/download-appliance.png)
 
 
 ### Verify security
@@ -51,17 +48,11 @@ Check that the zipped file is secure, before you deploy it.
 2. Run the following command to generate the hash for the VHD
     - ```C:\>CertUtil -HashFile <file_location> [Hashing Algorithm]```
     - Example usage: ```C:\>CertUtil -HashFile C:\AzureMigrate\AzureMigrate.ova SHA256```
-3.  For the latest appliance version, the generated hash should match these settings.
-
-  **Algorithm** | **Hash value**
-  --- | ---
-  MD5 | 96fd99581072c400aa605ab036a0a7c0
-  SHA256 | f5454beef510c0aa38ac1c6be6346207c351d5361afa0c9cea4772d566fcdc36
+3.  For the latest appliance version, the generated hash should match these [settings](https://docs.microsoft.com/azure/migrate/tutorial-assess-physical#verify-security).
 
 
 
 ## Run the Azure Migrate installer script
-=
 The installer script does the following:
 
 - Installs agents and a web application for physical server discovery and assessment.
@@ -77,13 +68,16 @@ Run the script as follows:
 1. Extract the zipped file to a folder on the server that will host the appliance.
 2. Launch PowerShell on the above server with administrative (elevated) privilege.
 3. Change the PowerShell directory to the folder where the contents have been extracted from the downloaded zipped file.
-4. Run the script by running the following command:
+4. Run the script named **AzureMigrateInstaller.ps1** by running the following command:
     ```
-    AzureMigrateInstaller.ps1
+    PS C:\Users\administrator\Desktop\AzureMigrateInstaller> AzureMigrateInstaller.ps1
     ```
 The script will launch the appliance web application when it finishes successfully.
 
+In case of any issues, you can access the script logs at C:\ProgramData\Microsoft Azure\Logs\AzureMigrateScenarioInstaller_<em>Timestamp</em>.log for troubleshooting.
 
+> [!NOTE]
+> Please do not execute the Azure Migrate installer script on an existing Azure Migrate appliance.
 
 ### Verify appliance access to Azure
 
diff --git a/articles/migrate/how-to-set-up-appliance-vmware.md b/articles/migrate/how-to-set-up-appliance-vmware.md
@@ -31,7 +31,7 @@ To set up the appliance you:
 2. In **Discover machines** > **Are your machines virtualized?**, click **Yes, with VMWare vSphere hypervisor**.
 3. Click **Download** to download the .OVA template file.
 
-
+  ![Selections for downloading an OVA file](./media/tutorial-assess-vmware/download-ova.png)
 
 ### Verify security
 
@@ -41,19 +41,17 @@ Check that the OVA file is secure, before you deploy it.
 2. Run the following command, to generate the hash for the OVA:
     - ```C:\>CertUtil -HashFile <file_location> [Hashing Algorithm]```
     - Example usage: ```C:\>CertUtil -HashFile C:\AzureMigrate\AzureMigrate.ova SHA256```
-3. For the latest appliance version, the generated hash should match these settings.
+3. For the latest appliance version, the generated hash should match these [settings](https://docs.microsoft.com/azure/migrate/tutorial-assess-vmware#verify-security).
 
-  **Algorithm** | **Hash value**
-  --- | ---
-  MD5 | c06ac2a2c0f870d3b274a0b7a73b78b1
-  SHA256 | 4ce4faa3a78189a09a26bfa5b817c7afcf5b555eb46999c2fad9d2ebc808540c
 
 
 ## Create the appliance VM
 
 Import the downloaded file, and create a VM.
 
 1. In the vSphere Client console, click **File** > **Deploy OVF Template**.
+![Menu command for deploying an OVF template](./media/tutorial-assess-vmware/deploy-ovf.png)
+
 2. In the Deploy OVF Template Wizard > **Source**, specify the location of the OVA file.
 3. In **Name** and **Location**, specify a friendly name for the VM. Select the inventory object in which the VM
 will be hosted.
diff --git a/articles/migrate/migrate-appliance.md b/articles/migrate/migrate-appliance.md
@@ -30,7 +30,7 @@ Physical machine |  Azure Migrate: Server Assessment |  Discover physical server
 **License** | The downloaded appliance template comes with a Windows Server 2016 evaluation license, which is valid for 180 days. If the evaluation period is close to expiry, we recommend that you download and deploy a new appliance, or that you activate the operating system license of the appliance VM.
 **Deployment** | You deploy the appliance as a VMware VM. You need enough resources on the vCenter Server to allocate a VM with 32-GB RAM, 8 vCPUs, around 80 GB of disk storage, and an external virtual switch.<br/> The appliance requires internet access, either directly or through a proxy.<br/> The appliance can connect to a single vCenter Server.
 **Hardware** | Resources on vCenter to allocate a VM with 32-GB RAM 8 vCPUs, around 80 GB of disk storage, and an external virtual switch. 
-**Hash value** | MD5: c06ac2a2c0f870d3b274a0b7a73b78b1<br/><br/> SHA256: 4ce4faa3a78189a09a26bfa5b817c7afcf5b555eb46999c2fad9d2ebc808540c
+**Hash value** | Check [here](https://docs.microsoft.com/azure/migrate/tutorial-assess-vmware#verify-security)
 **vCenter server/host** | The appliance VM must be deployed on an ESXi host running version 5.5 or later.<br/><br/> vCenter Server running 5.5, 6.0, 6.5, or 6.7.
 **Azure Migrate project** | An appliance can be associated with a single project. <br/> Any number of appliances can be associated with a single project.<br/> 
 **Discovery** | An appliance can discover up to 10,000 VMware VMs on a vCenter Server.<br/> An appliance can connect to a single vCenter Server.
@@ -48,7 +48,7 @@ Physical machine |  Azure Migrate: Server Assessment |  Discover physical server
 **License** | The downloaded appliance template comes with a Windows Server 2016 evaluation license, which is valid for 180 days. If the evaluation period is close to expiry, we recommend that you download and deploy a new appliance, or that you activate the operating system license of the appliance VM.
 **Appliance deployment**   |  You deploy the appliance as a Hyper-V VM.<br/> The appliance VM provided by Azure Migrate is Hyper-V VM version 5.0.<br/> The Hyper-V host must be running Windows Server 2012 R2 or later.<br/> The host needs sufficient space to allocate 16 GB RAM, 8 vCPUs, around 80 GB of storage space, and an external switch for the appliance VM.<br/> The appliance needs a static or dynamic IP address, and internet access.
 **Hardware** | Resources on Hyper-V host to allocate 16-GB RAM, 8 vCPUs, around 80 GB of storage space, and an external switch for the appliance VM.
-**Hash value** | MD5: 29a7531f32bcf69f32d964fa5ae950bc<br/><br/> SHA256: 37b3f27bc44f475872e355f04fcb8f38606c84534c117d1609f2d12444569b31
+**Hash value** | Check [here](https://docs.microsoft.com/azure/migrate/tutorial-assess-hyper-v#verify-security)
 **Hyper-V host** | Running Windows Server 2012 R2 or later.
 **Azure Migrate project** | An appliance can be associated with a single project. <br/> Any number of appliances can be associated with a single project.<br/> 
 **Discovery** | An appliance can discover up to 5000 Hyper-V VMs.<br/> An appliance can connect to up to 300 Hyper-V hosts.
@@ -63,7 +63,7 @@ Physical machine |  Azure Migrate: Server Assessment |  Discover physical server
 **Download link** | [Download link](https://go.microsoft.com/fwlink/?linkid=2105112)
 **Download size** | 59.7 MB
 **Hardware** | Dedicated physical machine, or use a Virtual Machine. The machine running appliance needs 16-GB RAM, 8 vCPUs, around 80 GB of storage space, and an external switch.<br/> The appliance needs a static or dynamic IP address, and internet access.
-**Hash value** | MD5: 1e92ede3e87c03bd148e56a708cdd33f<br/><br/> SHA256: a3fa78edc8ff8aff9ab5ae66be1b64e66de7b9f475b6542beef114b20bfdac3c
+**Hash value** | Check [here](https://docs.microsoft.com/azure/migrate/tutorial-assess-physical#verify-security)
 **Operating System** | Appliance machine should be running Windows Server 2016. 
 **Appliance deployment**   |  The appliance installer script is downloaded from the portal (in a zipped folder). <br/> You unzip the folder, and run the PowerShell script (AzureMigrateInstaller.ps1).
 **Discovery** | An appliance can discover up to 250 physical servers.
diff --git a/articles/migrate/migrate-support-matrix-vmware-migration.md b/articles/migrate/migrate-support-matrix-vmware-migration.md
@@ -30,7 +30,7 @@ Review [this article](server-migrate-overview.md) to figure out which method you
 --- | ---
 **VMware vCenter Server** | Version 5.5, 6.0, 6.5, or 6.7.
 **VMware vSphere ESXI host** | Version 5.5, 6.0, 6.5, or 6.7.
-**vCenter Server permissions** | Agentless migration uses the [Migrate Appliance](migrate-appliance.md). The appliance needs these permissions:<br/><br/> - **Datastore.Browse**: Allow browsing of VM log files to troubleshoot snapshot creation and deletion.<br/><br/> **Datastore.LowLevelFileOperations**: Allow read/write/delete/rename operations in the datastore browser, to troubleshoot snapshot creation and deletion.<br/><br/> - **VirtualMachine.Configuration.DiskChangeTracking**: Allow enable or disable change tracking of VM disks, to pull changed blocks of data between snapshots.<br/><br/> - **VirtualMachine.Configuration.DiskLease**: Allow disk lease operations for a VM, to read the disk using the VMware vSphere Virtual Disk Development Kit (VDDK).<br/><br/> - **VirtualMachine.Provisioning.AllowReadOnlyDiskAccess**: Allow opening a disk on a VM, to read the disk using the VDDK.<br/><br/> - **VirtualMachine.Provisioning.AllowVirtualMachineDownload**: Allows read operations on files associated with a VM, to download the logs and troubleshoot if failure occurs.<br/><br/> - **VirtualMachine.SnapshotManagement.***: Allow creation and management of VM snapshots for replication.<br/><br/> - **Virtual Machine.Interaction.Power Off**: Allow the VM to be powered off during migration to Azure.
+**vCenter Server permissions** | Agentless migration uses the [Migrate Appliance](migrate-appliance.md). The appliance needs these permissions:<br/><br/> - **Datastore.Browse**: Allow browsing of VM log files to troubleshoot snapshot creation and deletion.<br/><br/> - **Datastore.LowLevelFileOperations**: Allow read/write/delete/rename operations in the datastore browser, to troubleshoot snapshot creation and deletion.<br/><br/> - **VirtualMachine.Configuration.DiskChangeTracking**: Allow enable or disable change tracking of VM disks, to pull changed blocks of data between snapshots.<br/><br/> - **VirtualMachine.Configuration.DiskLease**: Allow disk lease operations for a VM, to read the disk using the VMware vSphere Virtual Disk Development Kit (VDDK).<br/><br/> - **VirtualMachine.Provisioning.AllowDiskAccess**: (specifically for vSphere 6.0 and above) Allow opening a disk on a VM for random read access on the disk using the VDDK.<br/><br/> - **VirtualMachine.Provisioning.AllowReadOnlyDiskAccess**: Allow opening a disk on a VM, to read the disk using the VDDK.<br/><br/>- **VirtualMachine.Provisioning.AllowVirtualMachineDownload**: Allows read operations on files associated with a VM, to download the logs and troubleshoot if failure occurs.<br/><br/> - **VirtualMachine.SnapshotManagement.***: Allow creation and management of VM snapshots for replication.<br/><br/> - **Virtual Machine.Interaction.Power Off**: Allow the VM to be powered off during migration to Azure.
 
 
 
