Migrating Virtual Machines to Azure | Server Virtualization and Azure Migration

Migrate Virtual Machines to Azure

Question

You have three servers named Server1, Server2, and Server3 that run Windows Server and have the Hyper-V server role installed. Server1 hosts an Azure

Migrate appliance named Migrate1.

You plan to migrate virtual machines to Azure.

You need to ensure that any new virtual machines created on Server1, Server2, and Server3 are available in Azure Migrate.

What should you do?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

D

The correct answer for this question is D. On Migrate1, add a discovery source.

Explanation:

Azure Migrate is a service offered by Microsoft Azure that allows users to migrate their virtual machines to the Azure cloud. In this scenario, the three servers named Server1, Server2, and Server3 that run Windows Server and have the Hyper-V server role installed will be used to create virtual machines that will be migrated to Azure.

To ensure that any new virtual machines created on Server1, Server2, and Server3 are available in Azure Migrate, we need to add a discovery source to Migrate1. A discovery source is a component of Azure Migrate that is responsible for discovering the virtual machines that are running on a physical or virtual machine.

To add a discovery source to Migrate1, we need to perform the following steps:

  1. Open the Azure Migrate portal and select the project that we want to add the discovery source to.
  2. On the project page, select the Servers tab and click on the Discover option.
  3. On the Discover page, select the Discovery source as Hyper-V and select the appropriate subscription and resource group.
  4. Next, we need to provide the Hyper-V server details such as the server name, username, and password. We can also specify whether we want to use a secure connection and the port number.
  5. Once we have provided all the details, click on the Discover servers button to add the Hyper-V server as a discovery source.

After we have added the Hyper-V server as a discovery source, Azure Migrate will start discovering the virtual machines running on the Hyper-V server. Any new virtual machines created on Server1, Server2, and Server3 will also be discovered by Azure Migrate.

Option A (On the network that has Migrate1 deployed, deploy a WINS server) and Option C (On the DNS server used by Migrate1, create a GlobalName zone) are not relevant to this scenario and will not help in discovering the virtual machines. Option B (On Migrate1, set the Startup Type of the Computer Browser service to Automatic) is also not relevant to this scenario and will not help in discovering the virtual machines.