none
Hyper-V Manager from Windows 10 RRS feed

  • Question

  • Hyper-V manager seems to have an issue when used from a client OS as opposed to a server OS.  Googling around shows this has been a problem for the last decade.  Some times it seems people can get it to work with various voodoo that shouldn't be needed, or is not applicable to an actual domain.  Here is the summary issue:

    hyper-V Manager on 2012R2 can manage a remote 2012R2 or 2016 server on the same domain no problem

    Hyper-V Manager on 2016 can manage a remote 2012R2 or 2016 server on the same domain no problem

    Hyper-V Manager from Windows 10 can manage a 2016 server on the same domain no problem

    Hyper-V Manager on Windows 10 can NOT connect to a 2012R2 server in the same domain under any condition. Given the above things that work, this makes no sense.  It points to a fundamental flaw in the Hyper-V Manager app on the client OS as compared to the server OS.

    No special configuration of any kind has to be made for any of the above things that work.  You simply use a domain account that has admin on all machines in question to launch the Hyper-V manager, point to a server, and you're in.  No auth needed, no tricks, no powershell, no command line, no firewall changes, no dcom changes, nothing goofy at all.  

    All indication is the HVM on Win 10 is defective in some way to cause it to fail to connect to a 2012R2 system.  Given all the other stated things that work, nothing special should have to be done to get this to work.  Regardless, if anyone knows a trick to actually make this work, I'd love to hear it.  It would be nice to be able to manage all servers from a single workstation, rather than needing to remote into a server to manage them.

    Monday, October 9, 2017 8:11 PM

All replies

  • Hi Ebonweaver,

    Sorry for the later reply, if your issue still not resolved, please refer to the following information.

    Based on my understanding, you meet issues to connect to Server 2012R2 Hyper V host from Windows 10 host.

    Then what error message do you get?

    Please try if repair the MOF file could work:

    On the HYPER-V SERVER to which you are trying to connect:

    1. Launch Command Prompt with Administrative Privileges

    2. On the prompt run following command to repair the MOF file: MOFCOMP %SYSTEMROOT%\System32\WindowsVirtualization.V2.mof
    3. Now we need to restart the VMMS Service in order to make changes effective. This can also be done from the same command prompt. Run following commands to stop and start the service:

    Net stop vmms
    Net start vmms

    If it still not work, here is a similar thread, for your reference:

    https://social.technet.microsoft.com/Forums/en-US/f7b4d00c-7808-4666-bd81-32e78fdb4087/using-windows-10-hyperv-manager-to-manage-hyperv-server-2012r2-hosts?forum=winserverhyperv

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, October 17, 2017 7:07 AM
    Moderator
  • Hi Ebonweaver,

    Just to check if the above reply could be of help, if yes, you may mark useful reply as answer, if you have other concerns, welcome to feedback.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, October 20, 2017 9:39 AM
    Moderator
  • As should be expected from the information I posted to start this thread, this does not work.  Nor of course should it be needed.  Also, the instructions are incorrect, but regardless rebuilding the mof does nothing to help this problem.
    Friday, October 20, 2017 4:16 PM
  • Thanks.!

    Saturday, October 6, 2018 2:01 PM