Walked into this issue when trying to deploy a logical switch from Virtual Machine Manager:
An internal error has occurred trying to contact the 'Cluster1-Node1' server: : .
WinRM: URL: [http://Cluster1-Node1:5985], Verb: [INVOKE], Method: [GetFinalResult], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scvmm/AsyncTask?ID=1001]
Unknown error (0x80078005)
Recommended Action
Check that WS-Management service is installed and running on server 'Cluster1-Node1'. For more information use the command "winrm helpmsg hresult". If 'Cluster1-Node1' is a host/library/update server or a PXE server role then ensure that VMM agent is installed and running. Refer to http://support.microsoft.com/kb/2742275 for more details.
After some troubleshooting I found out that one of the NICs that I was adding to the switch had still the “Hyper-V Extensible Virtual Switch” enabled:
Apparently when I removed a virtual switch from the server it did not restore the settings on the NIC.
Make sure that no switch is bound to the NIC, and if not to uncheck the box and try to deploy your logical switch again!
—
Thank you for reading my blog.
If you have any questions or feedback, leave a comment or drop me an email.
Darryl van der Peijl
http://www.twitter.com/DarrylvdPeijl
Hi Darryl,
I had this issue myself today on a Windows 2019 server and SCVMM 2019. Why on earth MS cannot update their VMM reference library to make their errors more useful is a mystery to me – Thankfully, we have folk like you with all the answers.
I just wanted to add that yes, this did fix the issue but my hyper-v servers were running windows core. I need to run the following to achieve the above.
Get-NetAdapterBinding -Name -DisplayName Hyp* | Set-NetAdapterBinding -Enabled $false
Simon
This worked for me. Thank you so much!
Thank you very much, I had the same problem and your article helps.
Hi, still the same in SCVMM 2022. LACP is not available anymore. I was forced to change adapters from LACP to SET. But the flag for LBFO teaming hang on all used adapters. This command saved my day. Now I have logical switch running on all nodes in S2D cluster.
Cheers