Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, June 1, 2018 8:51 PM
exact error was:
Error (20406)
VMM could not enumerate instances of class Msvm_VirtualEthernetSwitch on the server d1h-ucs1-5.lasd.sheriff.sdn. Failed with error HRESULT 0x80041001 The WS-Management service cannot process the request. The WMI service or the WMI provider returned an unknown error: HRESULT 0x80041001
All replies (4)
Friday, June 1, 2018 9:20 PM
Hi!
Is this a standalone setup or a cluster? What is the OS of your Hyper-V hosts and what is the build version of VMM 2016?
Best regards,
Leon
Blog: https://thesystemcenterblog.com LinkedIn:
Friday, June 1, 2018 9:28 PM
standalone setup. Hyper-V is on Win Server 2012 R2 Datacenter. VMM version is 4.0.1662.0
Friday, June 1, 2018 9:36 PM
Okay, you are running the RTM version. There's been other cases with the same problem as you but different errors.
Are the Server 2012 R2 fully patched? You could also try to install the latest RollUp 5 of VMM to see if it helps.
Best regards,
Leon
Blog: https://thesystemcenterblog.com LinkedIn:
Monday, June 4, 2018 7:31 AM
Hello kevscom888,
On the Hyper-V host, please open the Hyper-V Manager, and check out the virtual switch settings from the Virtual Switch Manager, and make sure the following option has been enabled for the external virtual switch.
Allow management operating system to share this network adapter
By the way, please install the most recent update for the VMM server.
Best regards,
Andy Liu
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.