none
Hyper-v could not create virtual switch on window server 2019 RRS feed

  • Question

  • hi,

    I try to create a External Virtual switch on hyper-v virtual switch manager.

    But it failed and shows as below, any idea?

    [Window Title]
    Virtual Switch Manager for DC

    [Main Instruction]
    Error applying Virtual Switch Properties changes

    [Content]
    Adding ports to the switch 'New Virtual Switch' failed.

    The operation failed because the file was not found.

    [Close]
    Sunday, December 1, 2019 4:57 AM

All replies

  • I'd check that the hardware has support for Server 2019 and latest patch level has been applied.

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Sunday, December 1, 2019 5:16 AM
  • [Window Title]

    Virtual Switch Manager for DC
    "DC" as in "Domain Controller"? Installing Hyper-V with ADDS is thoroughly unsupported, absolutely guaranteed to cause problems, and does nothing positive in the handful of situations where it happens to work.

    Eric Siron
    Altaro Hyper-V Blog
    I am an independent contributor, not an Altaro employee. I accept all responsibility for the content of my posts. You accept all responsibility for any actions that you take based on the content of my posts.

    Sunday, December 1, 2019 6:16 AM
  • Do u mean Hyper-V will not work at a computer that has role "DC"?

    Currently, the server plays like:

    Server(A) - Roles

        |- DC

        |- Hyper-V

                |- VM1

    What if i orginaze it like:

    Server(A) - Roles

        |- Hyper-V

                |- VM1 - 

                |- VM2 - DC

    • Edited by Qianbiao.NG Sunday, December 1, 2019 8:03 AM
    Sunday, December 1, 2019 8:01 AM
  • Do u mean Hyper-V will not work at a computer that has role "DC"?


    The two roles are conflicting. A better option is to install Hyper-V role as only role on host, then stand up guests for the various roles. Active directory domain services should be on it's own windows instance.

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    • Proposed as answer by Tim CerlingMVP Monday, December 2, 2019 2:33 PM
    Sunday, December 1, 2019 1:43 PM
  • Ditto to what Dave said. I have seen it work for some people, but it will never work well for anyone. When it does work, it doesn't give any benefits. You can't save money on licensing and it makes the domain less reliable than running it in a VM.

    What if i orginaze it like:

    Server(A) - Roles

        |- Hyper-V

                |- VM1 - 

                |- VM2 - DC

    That is how I build mine. Install Hyper-V, then make a DC VM, then join the Hyper-V host to the domain, then build the rest of the VMs.

    Eric Siron
    Altaro Hyper-V Blog
    I am an independent contributor, not an Altaro employee. I accept all responsibility for the content of my posts. You accept all responsibility for any actions that you take based on the content of my posts.

    • Proposed as answer by Tim CerlingMVP Monday, December 2, 2019 2:33 PM
    Sunday, December 1, 2019 5:27 PM
  • Hi ,

    The best practice for Hyper-v is to run nothing but expect Hyper-v on the host.

    Please refer to the following link:

    Hyper-V should be the only enabled role

    You can install Hyper-v on physical server and configure virtual machines, as Eric said ,domain controller can be virtual.

    You could mark the useful reply as answer if you want to end this thread up.

    If you have anything unclear, please feel free to post in the forum.

    Best Regards,
    Candy


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


    Tuesday, December 3, 2019 2:03 AM
  • Hi ,

    Just want to confirm the current situations.

    Please feel free to let us know if you need further assistance.                   

    Best Regards,

    Candy


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

    Thursday, December 5, 2019 1:50 AM