No registered Hyper-V hosts were found

Question

No registered Hyper-V hosts were found

Peter Kandra 0

I'm looking to migrate 2 premise based Hyper-V VMs to Azure. I went through the assessment process just fine and it discovered my servers. I downloaded the Hyper-V Replication provider and installed it and it registered the server fine, but it shows 0 connected Hyper-V hosts in the Azure portal.

Screen shots attached. Azure1

Azure2

Azure3

SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-04-14T20:30:18.1533333+00:00
Hi @Peter Kandra Thank you for reaching out to us on Microsoft Q&A platform. Sorry for the inconvenience this may have caused. If Azure Migrate is showing 0 connected Hyper-V hosts in the Azure portal, it means that Azure Migrate is not able to discover your Hyper-V hosts. To resolve this issue, you can try the following steps:

Check if the Azure Migrate appliance is running and is able to communicate with the Azure Migrate service. You can check the status of the appliance in the Azure portal. Check if the Hyper-V hosts are running and are accessible from the Azure Migrate appliance. You can try to ping the Hyper-V hosts from the appliance to check the connectivity.

Check if the firewall on the Hyper-V hosts is configured to allow incoming connections from the Azure Migrate appliance. You can add an inbound rule to the firewall to allow incoming connections on the Hyper-V hosts.

Check if the Hyper-V hosts are configured to allow remote management. You can enable remote management on the Hyper-V hosts by using the Hyper-V Manager.

Check if the Hyper-V hosts are added to the Azure Migrate project. You can add the Hyper-V hosts to the project by using the Azure Migrate portal. If none of the above steps resolve the issue, you can refer to the Azure Migrate troubleshooting guide for more information on how to troubleshoot
Peter Kandra 0 Reputation points

2023-04-14T20:56:18.6166667+00:00

Thanks @SadiqhAhmed-MSFT The Azure Migrate Appliance is fine. It discovered 6 VMs (including itself) and the appliance services are connected fine and I can ping the Hyper-V host from the appliance, so #1 is fine. As far as #2, I already have a rule allowing any traffic. #3 should already be done, but I will check...I didn't see anywhere in Hyper-V Manager to enable remote management. For #4, I don't see how to check (and add if needed) Hyper-V hosts to the project.
Peter Kandra 0 Reputation points

2023-04-18T17:20:30.85+00:00

Just bumping this thread to see if there's anything additional I can check.

2 answers

Your answer

SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-04-14T20:30:18.1533333+00:00

Hi @Peter Kandra Thank you for reaching out to us on Microsoft Q&A platform. Sorry for the inconvenience this may have caused. If Azure Migrate is showing 0 connected Hyper-V hosts in the Azure portal, it means that Azure Migrate is not able to discover your Hyper-V hosts. To resolve this issue, you can try the following steps:

Check if the Azure Migrate appliance is running and is able to communicate with the Azure Migrate service. You can check the status of the appliance in the Azure portal. Check if the Hyper-V hosts are running and are accessible from the Azure Migrate appliance. You can try to ping the Hyper-V hosts from the appliance to check the connectivity.

Check if the firewall on the Hyper-V hosts is configured to allow incoming connections from the Azure Migrate appliance. You can add an inbound rule to the firewall to allow incoming connections on the Hyper-V hosts.

Check if the Hyper-V hosts are configured to allow remote management. You can enable remote management on the Hyper-V hosts by using the Hyper-V Manager.

Check if the Hyper-V hosts are added to the Azure Migrate project. You can add the Hyper-V hosts to the project by using the Azure Migrate portal. If none of the above steps resolve the issue, you can refer to the Azure Migrate troubleshooting guide for more information on how to troubleshoot
Peter Kandra 0 Reputation points

2023-04-14T20:56:18.6166667+00:00

Thanks @SadiqhAhmed-MSFT The Azure Migrate Appliance is fine. It discovered 6 VMs (including itself) and the appliance services are connected fine and I can ping the Hyper-V host from the appliance, so #1 is fine. As far as #2, I already have a rule allowing any traffic. #3 should already be done, but I will check...I didn't see anywhere in Hyper-V Manager to enable remote management. For #4, I don't see how to check (and add if needed) Hyper-V hosts to the project.
Peter Kandra 0 Reputation points

2023-04-18T17:20:30.85+00:00

Just bumping this thread to see if there's anything additional I can check.

Answer 1

SadiqhAhmed-MSFT 49,331 Microsoft Employee Moderator

Hello @Peter Kandra Apologies for the delayed response.

First thing, the Azure Migrate appliance will only work for the discovery and assessment. You need to install the provider in the Hyper-V host for the replication. The same as in ASR (Azure Site Recovery) - Migrate Hyper-V VMs to Azure with the Migration and modernization tool - Azure Migrate | Microsoft Learn

For migrating Hyper-V VMs, the Migration and modernization tool installs software providers (Microsoft Azure Site Recovery provider and Microsoft Azure Recovery Service agent) on Hyper-V Hosts or cluster nodes. Note that the Azure Migrate appliance isn't used for Hyper-V migration.

Hope this answers your question. Feel free to ping if you have any questions!

If the response helped, do "Accept Answer" and up-vote it

Peter Kandra 0 Reputation points

2023-05-03T16:49:15.3266667+00:00

I understand the process, and have already installed the tools and Site Recovery provider (one of my screen shots showed that). My issue is that the Hyper-V host server never shows up in the Azure portal.

Answer 2

Peter Kandra 0

To update this thread for anyone who may be going through this same process, the problem was that I had an old install of SCVMM that wasn't being used. The discovery process was registering the host under the System Center VMM section instead of the Hyper-V Sites section. Once I uninstalled SCVMM, cleaned up the vault and all the associated objects and re-did the process from scratch, it worked fine. For anyone also wondering, the VM appliance is ONLY needed for the assessment...it's not needed for the actual migration. The AzureSiteRecoveryProvider installs all the tools needed.

AzureFix

SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-05-11T11:34:43.84+00:00

@Peter Kandra Thanks for the update! Glad to hear it is resolved :)

Thanks once again for sharing the solution with the community!
Anonymous

2023-10-31T12:11:23.57+00:00

Hello @Peter Kandra how did you get to this blade?
Peter Kandra 0 Reputation points

2023-10-31T17:26:53.12+00:00

@Marcelo Salvatori it's in Azure under Recovery services vaults, choose the vault you created for site recovery and then it's Site Recovery infrastructure.

Share via

No registered Hyper-V hosts were found

2 answers

Your answer