|
| 1 | +--- |
| 2 | +title: Deploy the Azure Migrate appliance for discovery and assessment of Hyper-V VMs to Azure with the Azure Migrate Server Assessment | Microsoft Docs |
| 3 | +description: Describes how to deploy the Azure Migrate appliance to discover and assess on-premises Hyper-V VMs to Azure, using Azure Migrate Server Assessment. |
| 4 | +author: rayne-wiselman |
| 5 | +ms.service: azure-migrate |
| 6 | +ms.topic: tutorial |
| 7 | +ms.date: 11/14/2018 |
| 8 | +ms.author: raynew |
| 9 | +ms.custom: mvc |
| 10 | +--- |
| 11 | + |
| 12 | +# Discover and assess on-premises Hyper-V VMs for migration to Azure with the Server Assessment Service |
| 13 | + |
| 14 | +As you move on-premises resources to the cloud, use [Azure Migrate](migrate-overview.md) to discover, assess, and migrate machines and workloads to Microsoft Azure. This article describes how to set up the Azure Migrate appliance to discover and assess on-premises Hyper-V VMs to Azure. After the appliance is deployed, you can run assessments. |
| 15 | + |
| 16 | + |
| 17 | +> [!NOTE] |
| 18 | +> Azure Migrate Server Assessment for Hyper-V VMs currently in public preview. |
| 19 | +
|
| 20 | +In this tutorial, you learn how to: |
| 21 | + |
| 22 | +> [!div class="checklist"] |
| 23 | +> * Create an Azure subscription if you don't have one, and make sure it has the correct permissions. |
| 24 | +> * Create an account that Azure Migrate can use to discover VMs on Hyper-V hosts/clusters. |
| 25 | +> * Create the appliance VM by downloading a zipped VHD template, and importing it to a Hyper-V host to create the VM. Make sure the the appliance VM can connect to the required Azure Migrate URLs. |
| 26 | +> * Set up the appliance for the first time, and start discovery. Verify that the discovered VMs appear in the Azure portal. |
| 27 | +
|
| 28 | + |
| 29 | +## Before you start |
| 30 | + |
| 31 | +We recommend you do the following before you start: |
| 32 | + |
| 33 | +- Review the [new features and limitations](migrate-overview.md#azure-migrate-services-public-preview) for Server Assessment. |
| 34 | +- Learn about [Hyper-V](migrate-overview.md#hyper-v-architecture) assessment architecture and processes. |
| 35 | + |
| 36 | + |
| 37 | +If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/pricing/free-trial/) before you begin. |
| 38 | + |
| 39 | + |
| 40 | +## Prerequisites |
| 41 | + |
| 42 | +- **Azure account permissions**: When you log into Azure to set up discovery and assessment, your Azure account needs permission to create Azure Active Directory (Azure AD) apps. |
| 43 | +- **Hyper-V host requirements**: Requirements are as follows: |
| 44 | + - The Hyper-V host should running Windows Server 2012 R2 or 2016, with the latest updates. In a cluster, all hosts should run one of these operating systems. |
| 45 | + - PowerShell remoting should be enabled on each host. Run this command as an admin in the PowerShell console: **Enable-PSRemoting -force**. |
| 46 | +- **Account for discovery**: You need a domain or local account with admin permissions on the Hyper-V hosts/cluster. Azure Migrate uses this account to discover the on-premises VMs. |
| 47 | +- **Azure Migrate appliance**: The Azure Migrate appliance runs on a Hyper-V VM. It's deployed using a zipped VHD file that you download from the Azure portal. This VHD runs Hyper-V VM version 5.0. |
| 48 | + - You need permissions to import this VM on a Hyper-V host. |
| 49 | + - The Hyper-V host on which the appliance VM is located must be running Windows Server 2012 R2 or later, with the latest updates. |
| 50 | + - You should have enough capacity to allocate 16 GB RAM, four virtual processors, and one external virtual switch for the VM. |
| 51 | + - The appliance VM can have a static or dynamic IP address. |
| 52 | + - The appliance VM requires internet access. |
| 53 | +- **Requirements for VHDs on SMB**: If you run VHDs on SMB in your on-premises site, you need to enable delegation of credentials from the appliance VM to the Hyper-V hosts/cluster running the VMs that you want to discover. This enables Azure Migrate to capture required information from the discovered machines. |
| 54 | + |
| 55 | + |
| 56 | +## Set up Azure permissions |
| 57 | + |
| 58 | +Either a tenant/global admin can assign permissions to create Azure AD apps to the account, or assign the Application Developer role (that has the permissions) to the account. |
| 59 | + |
| 60 | +### Grant account permissions |
| 61 | + |
| 62 | +The tenant/global admin can grant permissions as follows |
| 63 | + |
| 64 | +1. In Azure AD, the tenant/global admin should navigate to **Azure Active Directory** > **Users** > **User Settings**. |
| 65 | +2. The admin should set **App registrations** to **Yes**. |
| 66 | + |
| 67 | +  |
| 68 | + |
| 69 | +> [!NOTE] |
| 70 | +> This is a default setting that isn't sensitive. [Learn more](https://docs.microsoft.com/azure/active-directory/develop/active-directory-how-applications-are-added#who-has-permission-to-add-applications-to-my-azure-ad-instance). |
| 71 | +
|
| 72 | + |
| 73 | + |
| 74 | +### Assign Application Developer role |
| 75 | + |
| 76 | +The tenant/global admin has permissions to assign the role to the account. [Learn more](https://docs.microsoft.comazure/active-directory/fundamentals/active-directory-users-assign-role-azure-portal). |
| 77 | + |
| 78 | + |
| 79 | + |
| 80 | +## Set up an account to access Hyper-V hosts |
| 81 | + |
| 82 | +Create an account that the Azure Migrate appliance can use to access Hyper-V hosts and cluster for VM discovery. |
| 83 | + |
| 84 | +- A single set of credentials is required for all hosts and clusters that you want to include in the discovery. |
| 85 | +- The account can be a local or domain account, and needs admin privileges on Hyper-V host/cluster servers. |
| 86 | + |
| 87 | + |
| 88 | +## Sign in to the Azure portal |
| 89 | + |
| 90 | +Sign in to the [Azure portal](https://portal.azure.com). |
| 91 | + |
| 92 | +## Open Azure Migrate |
| 93 | + |
| 94 | +1. In the Azure portal, click **All services**. |
| 95 | +2. Search for **Azure Migrate**, and select **Azure Migrate - PREVIEW** in the search results. This opens the Azure Migrate dashboard. |
| 96 | + |
| 97 | + |
| 98 | +## Set up the appliance VM |
| 99 | + |
| 100 | +Deploy the Azure Migrate appliance as a Hyper-V VM: |
| 101 | + |
| 102 | +- The appliance discovers on-premises Hyper-V VMs, and sends VM metadata and performance data to Azure Migrate. |
| 103 | +- To set up the appliance you download a zipped VHD file, and import it to the on-premises Hyper-V host/cluster to create a VM. |
| 104 | + |
| 105 | +### Download the VHD |
| 106 | + |
| 107 | +1. In the Azure Migrate dashboard, click **Discover a new site** > **Discover & Assess** > **Discover Machines**. |
| 108 | +2. In **Discover machines** > **Are your machines virtualized?**, click **Yes, with Hyper-V**. |
| 109 | +3. Click **Download** to download the zipped VHD. |
| 110 | + |
| 111 | +  |
| 112 | + |
| 113 | + |
| 114 | +### Verify security |
| 115 | + |
| 116 | +Check that the zipped file is secure, before you deploy it. |
| 117 | + |
| 118 | +1. On the machine to which you downloaded the file, open an administrator command window. |
| 119 | +2. Run the following command to generate the hash for the VHD |
| 120 | + - ```C:\>CertUtil -HashFile <file_location> [Hashing Algorithm]``` |
| 121 | + - Example usage: ```C:\>CertUtil -HashFile C:\AzureMigrate\AzureMigrate.ova SHA256``` |
| 122 | +3. The generated hash should match these settings. |
| 123 | + |
| 124 | + |
| 125 | + For OVA version 1.0.9.14 |
| 126 | + |
| 127 | + **Algorithm** | **Hash value** |
| 128 | + --- | --- |
| 129 | + MD5 | C78457689822921B783467586AFB22B3 |
| 130 | + SHA1 | F1338F9D9818DB61C88F8BDA1A8B5DF34B8C562D |
| 131 | + SHA256 | 0BE66C936BBDF856CF0CDD705719897075C0CEA5BE3F3B6F65E85D22B6F685BE |
| 132 | + |
| 133 | + |
| 134 | +### Create the appliance VM |
| 135 | + |
| 136 | +Import the downloaded file to the Hyper-V host, and create a VM from it. |
| 137 | + |
| 138 | +1. Extract the zipped VHD file to a folder on the Hyper-V host on which you'll set up the appliance VM. |
| 139 | +2. Open Hyper-V Manager. In **Actions**, click **Import Virtual Machine**. |
| 140 | + |
| 141 | +  |
| 142 | + |
| 143 | +2. In the Import Virtual Machine Wizard > **Before you begin**, click **Next**. |
| 144 | +3. In **Locate Folder**, specify the folder in which the extracted VHD is located. Then click **Next**. |
| 145 | +1. In **Select Virtual Machine**, click **Next**. |
| 146 | +2. In **Choose Import Type**, click **Copy the virtual machine (dreate a new unique ID)**. Then click **Next**. |
| 147 | +3. In **Choose Destination**, leave the default setting unless you want a specific location. Click **Next**. |
| 148 | +4. In **Storage Folders**, leave the default setting unless you need to modify. Click **Next**. |
| 149 | +5. In **Choose Network**, specify the virtual switch that the VM will use. The switch needs internet connectivity to send data to Azure. |
| 150 | +6. In **Summary**, review settings. Then click **Finish**. |
| 151 | +7. In Hyper-V Manager > **Virtual Machines**, start the VM. |
| 152 | + |
| 153 | + |
| 154 | +### Verify internet connectivity |
| 155 | + |
| 156 | +The appliance VM needs internet connectivity to Azure. If you're using a URL-based proxy to control outbound connectivity, make sure these URLs are allowed. |
| 157 | + |
| 158 | +**URL** | **Reason** |
| 159 | +--- | --- |
| 160 | +*.portal.azure.com | Reach the Azure portal. |
| 161 | +*.windows.net<br/><br/> *microsoftonline.com | Log in to Azure.<br/><br/> Create Azure AD app and Service Principal objects for agent to service communications. |
| 162 | +management.azure.com | Communicate with Azure Resource Manager to set up Azure Migrate artifacts. |
| 163 | +dc.services.visualstudio.com | Upload app logs for internal monitoring. |
| 164 | +*.vault.azure.net | Communication between agent and service (persistent secrets). |
| 165 | + |
| 166 | +## Set up the appliance |
| 167 | + |
| 168 | +Set up the appliance for the first time, and register it with Azure Migrate. |
| 169 | + |
| 170 | +1. In Hyper-V Manager > **Virtual Machines**, right-click the VM > **Connect**. |
| 171 | +2. Provide the language, time zone, and password preferences for the appliance. |
| 172 | +3. On the desktop of the appliance VM, click the **Start discovery** shortcut to open the appliance web app. Alternatively, run the web app remotely from **https://*appliance name or IP address*:44368**. |
| 173 | +2. In the appliance web app, click **Check for updates** to verify that you're running the latest version of the app. If not, you can download the latest upgrade. |
| 174 | +3. In **Set up prerequisites**, do the following: |
| 175 | + - **License**: Accept the license terms, and read the third-party information. |
| 176 | + - **Connectivity**: The app checks that the VM has internet access. If the VM accesses the internet via a proxy and not directly: |
| 177 | + - Click **Proxy settings**, and specify the proxy address and listening port, in the form http://ProxyIPAddress or http://ProxyFQDN. |
| 178 | + - Specify credentials if the proxy needs authentication. |
| 179 | + - Only HTTP proxy is supported. |
| 180 | + - The collector checks that the collector service is running. The service is installed by default on the collector VM. |
| 181 | + - **Time sync**: The time on the appliance should be in sync with internet time for discovery to function correctly. |
| 182 | + |
| 183 | +### Register the appliance with Azure Migrate |
| 184 | + |
| 185 | +1. Click **Log In**. |
| 186 | +2. On the new tab, log in using the Azure credentials with the required permissions. |
| 187 | +3. After a successful logon, go back to the web app. |
| 188 | +4. Select the subscription, resource group, and region in which you want to store the list of discovered VMs, and the VM metadata. |
| 189 | +5. Select a site name. A site gathers together a group of discovered VMs. |
| 190 | + |
| 191 | + |
| 192 | +## Start discovery |
| 193 | + |
| 194 | +Now, connect to the Hyper-V host/cluster, and start discovery. |
| 195 | + |
| 196 | +1. In **User name** and **Password**, specify the account credentials that you created for the appliance to discover VMs on the Hyper-V host/cluster. Specify a friendly name for the credentials, and click **Save details**. |
| 197 | +2. Click **Add host**, and specify the Hyper-V hosts/clusters on which you want to discover VMs. Click **Validate**. After validation, the number of VMs that can be discovered on each host/cluster is shown. |
| 198 | + - If validation fails for a host, reivewing the error by hovering over the icon in the **Status** column. Fix and validate again with **Validate list**. |
| 199 | + - To remote any hosts/clusters, select > **Delete**. |
| 200 | + - You can't remove a specific host from a cluster. You can only remove the entire cluster. |
| 201 | + - You can add a cluster even if there are issues with specific hosts in the cluster. |
| 202 | +3. After validation, click **Save and start discovery** to kick off the discovery process. |
| 203 | + |
| 204 | +It takes around 15 minutes for metadata of discovered VMs to appear in the portal. |
| 205 | + |
| 206 | +### Verify VMs in the portal |
| 207 | + |
| 208 | +After discovery finishes, you can verify that the VMs appear in the portal. |
| 209 | + |
| 210 | +1. Open the Azure Migrate dashboard |
| 211 | +2. In the **Server Assessment Service** page, click the icon that displays the count for the discovered machines. |
| 212 | + |
| 213 | +Note the following: |
| 214 | +- The appliance continuously profiles the on-premises environment and sends metadata. |
| 215 | +- You can create as-is assessments immediately after discovery. |
| 216 | +- For performance assessments, we recommend that you wait at least a day after discovery: |
| 217 | + - Collecting performance data takes time. Waiting at least a day ensures that there are enough performance data points before you run the assessment. |
| 218 | + - For performance data, the appliance collects real-time data points every 20 seconds for each performance metrics, and rolls them up to a single five minute data point. The appliance sends the five-minute data point to Azure every hour for assessment calculation. |
| 219 | + |
| 220 | + |
| 221 | +## Next steps |
| 222 | + |
| 223 | +After discovery, you can run assessments, and migrate VMware VMs to Azure: |
| 224 | + |
| 225 | +- [Learn](tutorial-server-assessment-hyper-v.md) how to create assessments for Hyper-V VMs. |
| 226 | +- [Learn more](https://docs.microsoft.com/azure/migrate/concepts-collector#what-data-is-collected) about the data that's collected by the appliance. |
| 227 | + |
0 commit comments