Hyper-V 2016 to 2019 Logical Network Issue

Paul McIver 1 Reputation point

I have a bunch of Hyper-V clustered servers running 2016 in SCVMM 2019 and looking to plan the host upgrade to 2019. I first wanted to deploy a new 2019 cluster to test outside of the production environment to play with and figure out any gotchas before starting to in-place upgrade the clusters and have stumbled pretty quickly.

When I attempt to assign the Logical Switch/Networks that are configured on the 2016 hosts I get the following error;

Error (50362)

Logical networks that use network virtualization and are not managed by Network Controller are not supported on the selected host OS version.

Recommended Action
Logical Networks that use Network Virtualization without Network Controller are not supported on Windows Server 2019 and above. Please manage the logical network using Network Controller for Network Virtualization.

After a little digging this seems to suggest I need to migrate the hosts to use SDN which feels like a massively complex test considering I have a good 60 VM Networks/Subnets setup and all managed by the physical switches today. There also seems to be basically no documentation around doing this, surely I can't be the only person to have hit this brick wall?

System Center Virtual Machine Manager
Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
962 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Limitless Technology 39,426 Reputation points

    Hi there,

    First, you need to make sure that not only the switch but all the VNICs are also available on all the cluster nodes.

    You also need to make sure that all the Switches are bound to a Logical network on the host properties under the hardware section.

    Run below PowerShell in SCVMM shell to find out if any of the logical networks are not selected for a given node:
    Get-SCVirtualNetwork | ft name , logicalnetworks , VMHOST

    Compare the information for all the cluster nodes and try to find out the missing bit.

    If everything is exactly the same, then I guess the issue is with the VMM refresh job where it failed to query the switch information for a given node.

    If none of them is helpful try setting up logical networks in the VMM 2019 UR1 fabric


    --If the reply is helpful, please Upvote and Accept it as an answer--

    0 comments No comments