Share via

Azure Migrate discovery error. The CIM namespace root/virtualization/v2 is invalid.

AJ 0 Reputation points
2025-11-11T17:15:31.6833333+00:00

I'm in the process of migrating four servers from our on-premises environment to Azure using a lift-and-shift approach. The server landscape includes:

  • One physical server running Windows Server 2012 R2
  • Three virtual machines hosted on Azure Stack HCI

To facilitate the assessment and migration, I'm leveraging Azure Migrate. I have followed the recommended setup steps (Hyper-V). Deployed the Azure Migrate appliance using the AzureMigrateInstaller PowerShell script method on a Windows Server 2022 VM within the Azure Stack HCI environment

However, encountered an issue during the Appliance Configuration Manager setup phase. Specifically, when attempting to add servers for discovery and authenticate using domain credentials (Administrator), the process fails with the following error:

Azure Migrate Discovery Error: "The WS-Management service cannot process the request. The CIM namespace root/virtualization/v2 is invalid."

This error is blocking the discovery setup of servers hosted in Azure Stack HCI.

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

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2025-11-11T17:15:54.2+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The error message "The WS-Management service cannot process the request. The CIM namespace root/virtualization/v2 is invalid" typically indicates an issue with the configuration or permissions related to the Windows Management Instrumentation (WMI) on the server you are trying to discover.

    Here are some steps you can take to troubleshoot and potentially resolve this issue:

    1. Verify WMI Namespace: Ensure that the root/virtualization/v2 namespace exists on the server. You can check this by running the following command in the Command Prompt: wmic /namespace:\.

    oot\virtualization\v2 path __namespace

    If the namespace does not exist, it may indicate a problem with the Hyper-V installation or configuration.

2. **Check User Permissions**: Ensure that the user account you are using for authentication has the necessary permissions to access the WMI namespaces. The account should be a member of the appropriate groups such as Remote Management Users and Performance Monitor Users.

3. **Enable WS-Management**: Make sure that the WS-Management service is properly configured and running on the server. You can check this by running the following command:

    winrm qc

    This command will configure the WS-Management service if it is not already set up.

    1. Validate Hyper-V Installation: Since you are using Azure Stack HCI, ensure that the Hyper-V role is installed correctly on the server and that the required features are enabled.
    2. Firewall and Network Settings: Ensure that the firewall settings allow traffic on the necessary ports for WMI and WS-Management. The default ports are 5985 for HTTP and 5986 for HTTPS.
    3. Review Logs: Check the event logs for any related errors that might provide more context on what is failing during the discovery process.

    By following these steps, you should be able to identify and resolve the issue preventing the discovery of your servers in Azure Migrate.

    References:

    0 comments

Your answer

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