Installing SCVMM 2022 on Windows 2022 WinRM Error

Ziad Chafi 0 Reputation points
2023-08-03T08:34:39.9733333+00:00

Hi, I'm trying to install SCVMM 2022 on Windows Server 2022 hosted on VMWare, at the end of the installation, the installations rolls back and I receive the following error:

A Hardware Management error has occurred trying to contact server 'SCVMMA.XXXXX.XXX.XXX.XX' .

WinRM: URL: [http://scvmma.XXXXX.XXX.XXX.XX:5985], Verb: [INVOKE], Method: [AssociateLibrary], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scvmm/AgentManagement]

Check that WinRM is installed and running on server 'SCVMMA.XXXXX.XXX.XXX.XX'. For more information use the command "winrm helpmsg hresult" and http://support.microsoft.com/kb/2742275.

I tried so many ways to resolve this issue, but no luck, I used Domain Admin account and sysadmin SQL user to avoid any permission issues, but the issue still persists, any ideas that might help?

System Center Virtual Machine Manager
{count} votes

2 answers

Sort by: Most helpful
  1. XinGuo-MSFT 18,771 Reputation points
    2023-08-04T02:42:40.62+00:00

    Hi,

    The error you're encountering seems to be related to WinRM (Windows Remote Management) not being properly configured or accessible on the server where you are trying to install SCVMM 2022. WinRM is a crucial component for remote management, and SCVMM relies on it to communicate with the server. Here are some steps you can take to troubleshoot and resolve the issue:

    1. Check WinRM Configuration: First, ensure that WinRM is installed and running on the server 'SCVMMA.XXXXX.XXX.XXX.XX'. You can do this by opening a Command Prompt or PowerShell with administrative privileges and running the following command:
    
    winrm quickconfig
    

    This command will configure WinRM to listen on all IP addresses and create a listener for HTTP.

    1. Verify Firewall Settings: Make sure that the Windows Firewall is not blocking the WinRM traffic. You can temporarily disable the firewall for testing purposes to see if that resolves the issue. If it does, you'll need to create a specific firewall rule to allow WinRM traffic.
    2. Check WinRM Service Status: Ensure that the WinRM service is running. You can check the status and start it by running the following command in an elevated Command Prompt or PowerShell:
    sc query winrm
    sc start winrm
    
    1. Verify Network Connectivity: Ensure that there are no network-related issues preventing communication between the SCVMM server and the target server.
    2. Check WinRM HTTPS Listener: If you are using HTTPS (port 5986) for WinRM communication, make sure the WinRM HTTPS listener is properly configured. Use the following command to check the listener:
    
    winrm enumerate winrm/config/listener
    

    If it's not configured, you can create a self-signed certificate for testing purposes:

    winrm create winrm/config/Listener?Address=*+Transport=HTTPS @{Hostname="<server_fqdn>";CertificateThumbprint="<thumbprint>"}
    

    Replace <server_fqdn> with the fully qualified domain name of the server and <thumbprint> with the certificate thumbprint.

    1. Review Event Logs: Check the Event Viewer for any relevant error messages that might provide more information about the issue.

  2. Shokaku Tanaka 0 Reputation points
    2024-07-17T06:18:29.55+00:00

    I recommend checking your proxy settings, especially by running "netsh winhttp show proxy" in a command prompt and making sure they are set correctly, including any exclusions.

    0 comments No comments

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.