Forum Discussion
Windows Server 2019 Preview Build 17623 Hyper-V Issue
Hi Marco,
Good to hear that you might have found a solution.
I am curious about your previous post though, you have both a vEthernet (External) adapter and a vEthernet (Internal) adapter on your VM Host. Are you using the vEthernet (Internal) adapter?
In my environment if my VM Host has more than one physical NIC I tend to Team them for redundancy and performance. I do this before I install the Hyper-V role.
I can post the PowerShell commands that I use to create a teamed NIC. Then after installing Hyper-V role I disable DHCP and tcpip6, set a static IP Address and DNS on the Hyper-V Virtual Ethernet Adapter.
Also Project Honolulu is a good way to manage Server core versions in conjunction with PowerShell and RSAT. Below is the link.
https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewserver
Regards,
Matt
Hello Matt,
I created the internal switch to test the communication between 2 virtual machines that have no need to access other networks; I created the external switch to assign it to a management virtual machine where to I want to install Project Honolulu and RSAT to test them.
Because this is a server for a test I don't teamed the nic (until now) and usually, as you do, I disable dhcp and assign a static address; previously, even on my Windows 10 machine, I've seen that if you install the Hyper-V role it creates a virtual adapter and then bind it to the physical and so the former takes the static ip address of the latter: is it still true or on Windows 10 and on Hyper-V standalone server is so while if I installa Windows Server and then Hyper-V role I may assign different the static ip address to both (virtual and physica) nics?
I thought that create an external switch and check the box to allow to use the management interface does the bind and I have a unique ip address.
What I don't understand?
Marco