Share via

Unable to discover hyper-v cluster

Menna 0 Reputation points Microsoft External Staff
2025-04-13T21:05:39.5+00:00

Hello All,

I’m encountering an issue while trying to discover a Hyper-V cluster using azure migrate. When I add the cluster as a discovery source, the validation succeeds, and discovery is initiated. However, the cluster is never actually discovered, and when checking on the appliance side again, I don't find it in the list of discovered sources (it is somehow removed).

This issue occurs with both of our Hyper-V clusters (they are the only clusters we have). Discovery works fine for standalone hosts.

Here’s what we’ve tried so far:

Adding the cluster using its IP address — same issue persists.

Adding an individual host — it gets resolved to the cluster's FQDN, but the result is the same: the cluster is not discovered.

Any guidance or suggestions would be appreciated.

Azure Migrate
Azure Migrate
A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
903 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Alex Burlachenko 4,875 Reputation points
    2025-04-14T12:12:15.3633333+00:00

    Hi Menna,

    Thank you for reaching out and providing a clear summary of the issue and the steps you’ve already taken here at Q&A portal.

    Based on your description, it appears that the Azure Migrate appliance is unable to successfully complete discovery of the Hyper-V cluster, despite initial validation success. Since standalone hosts are discovered properly, the issue is likely specific to how cluster-level metadata is being handled or retrieved.

    Lets think what should be checked and steps what to do

    Ensure the cluster is running on Windows Server 2016 or later Azure Migrate supports discovery of Hyper-V clusters running supported OS versions. Please verify that both clusters are on a supported platform.

    Cluster Management Tools and PowerShell Access The Azure Migrate appliance uses PowerShell and WMI to gather cluster metadata. Make sure:

    Failover Clustering feature is properly installed and functional.

    The user credentials provided to the appliance have administrative permissions on the cluster nodes and the cluster name object (CNO).

    Remote PowerShell and WMI access is enabled and not being blocked by firewalls or security settings.

    DNS Resolution Since you mentioned the host resolves to the FQDN of the cluster, ensure the Azure Migrate appliance can resolve both the FQDN and NetBIOS names of:

    Each cluster node

    The cluster itself

    You can test this from the appliance using:

    Resolve-DnsName <ClusterName>

Test-Connection <ClusterName>

    Check Event Logs and Azure Migrate Appliance Logs On the Azure Migrate appliance, check the logs under: C:\ProgramData\ASRLogs\Appliance Look for entries related to HyperVDiscovery or cluster lookup failures.

    Try manual re-addition and monitor behavior If the cluster disappears from the source list, try removing any stale records, restart the appliance service, and re-add the cluster using its FQDN rather than IP.

     

    Discovery does not work over IP addresses only for clusters — using FQDN and proper DNS configuration is required.

    Occasionally, if WinRM or DCOM/WMI ports are blocked or partially configured on one node, discovery may silently fail and the source is dropped.

    Helpful Documentation:

    Azure Migrate supported configurations for Hyper-V

     

    Best regards,

    Alex

    P.s. If my answer help to you, please Accept my answer

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.