Share via

How to fix error 426 in SCVMM

William St-Denis 0 Reputation points
2026-02-13T19:07:59.82+00:00

I try to add an Hyper V Host to SCVMM with the perimeter option. I already installed the VMM Agent locally on my Hyper V host but it tells me : Error (426)

The agent is not responding on the perimeter network HYPERV machine because either the agent is not installed; or HYPERV is not accessible from VMM management server.

I know that the SCVMM Agent is running. What can i try to fix this?

Windows for business | Windows Server | Storage high availability | Virtualization and Hyper-V
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Jason Nguyen Tran 12,485 Reputation points Independent Advisor
    2026-02-14T09:01:51.56+00:00

    Hi William St-Denis,

    This error generally indicates that the VMM management server cannot communicate with the agent service on the host, often due to network connectivity, firewall rules, or port configuration.

    As a first step, please ensure that TCP port 443 and 5985/5986 (for WinRM) are open between the SCVMM management server and the Hyper-V host. Firewalls or perimeter network restrictions can block these ports, preventing the agent from responding. Next, verify that the SCVMM agent service is running under the correct account and that the host can resolve the management server’s DNS name. It is also helpful to check whether there are proxy settings or network isolation policies that could interfere with communication.

    If the agent was installed manually, confirm that the version matches the SCVMM server version, as mismatched versions can cause handshake failures. You may also try reinstalling the agent with elevated permissions to ensure proper registration. Another useful step is to run netstat or PowerShell commands on the host to confirm that the agent is listening on the expected ports.

    In some environments, perimeter hosts require certificates or additional configuration to establish trust with the SCVMM server. Reviewing the SCVMM logs on both the management server and the host can provide more detail about why the agent is not responding. If the issue persists, capturing traces and opening a support case with Microsoft Support will allow deeper investigation.

    If you find this answer helpful, please consider clicking Accept Answer so I know your issue has been resolved.

    Jason.


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.