Building a Hyper-V 2016 host Take 2
-
@jaredbusch said in Building a Hyper-V 2016 host Take 2:
@brrabill said in Building a Hyper-V 2016 host Take 2:
@jaredbusch said in Building a Hyper-V 2016 host Take 2:
@brrabill said in Building a Hyper-V 2016 host Take 2:
@jaredbusch said in Building a Hyper-V 2016 host Take 2:
@brrabill said in Building a Hyper-V 2016 host Take 2:
QUESTION:
Let's say you have 3 NICs in the server, and you give them static addresses of 10.0.0.1 10.0.0.2 and 10.0.0.3
When you team them, the multiplexor adapter is created.
This then gets its own static IP address?
I keep losing connection here at this step, and I can fix it, but might be worth a small discussion on...
No, when you team them the static addressing is lost. The best thing to do is have everything DHCP and then team. The team will pull an IP and then you can make it static.
Just to confirm ... if you set them all, it means nothing?
AKA, those static addresses all disappear?
Yes. When you make a team hat has static ip on the original interfaces it tells you that that static config will be lost. But stupidly, it does not set it to dhcp either.
Actually, I think it does now. Because I ended up going to the physical console, and it had pulled a new address. Maybe that is new.
Well, 2012 R2 did not do that. Haven't deployed a new 2016 to test that theory.
Confirmed with 2012 R2, that's exactly how it worked.
Static IPs on NICs, turn them into a team, gone.
All my Hyper-V hypervisors are now on 2016, and they use teams, but there is no sense in giving two NICs statically assigned IPs if you turn them into a team, so I have had no reason to try it on 2016.
As JB said, make everything DHCP... then after you team them, then you can make a DHCP reservation if you want a specific IP... I rarely do static assignments, usually reservations unless it's a DC or something like that.
-
@obsolesce said in Building a Hyper-V 2016 host Take 2:
@jaredbusch said in Building a Hyper-V 2016 host Take 2:
@brrabill said in Building a Hyper-V 2016 host Take 2:
@jaredbusch said in Building a Hyper-V 2016 host Take 2:
@brrabill said in Building a Hyper-V 2016 host Take 2:
@jaredbusch said in Building a Hyper-V 2016 host Take 2:
@brrabill said in Building a Hyper-V 2016 host Take 2:
QUESTION:
Let's say you have 3 NICs in the server, and you give them static addresses of 10.0.0.1 10.0.0.2 and 10.0.0.3
When you team them, the multiplexor adapter is created.
This then gets its own static IP address?
I keep losing connection here at this step, and I can fix it, but might be worth a small discussion on...
No, when you team them the static addressing is lost. The best thing to do is have everything DHCP and then team. The team will pull an IP and then you can make it static.
Just to confirm ... if you set them all, it means nothing?
AKA, those static addresses all disappear?
Yes. When you make a team hat has static ip on the original interfaces it tells you that that static config will be lost. But stupidly, it does not set it to dhcp either.
Actually, I think it does now. Because I ended up going to the physical console, and it had pulled a new address. Maybe that is new.
Well, 2012 R2 did not do that. Haven't deployed a new 2016 to test that theory.
Confirmed with 2012 R2, that's exactly how it worked.
Static IPs on NICs, turn them into a team, gone.
All my Hyper-V hypervisors are now on 2016, and they use teams, but there is no sense in giving two NICs statically assigned IPs if you turn them into a team, so I have had no reason to try it on 2016.
As JB said, make everything DHCP... then after you team them, then you can make a DHCP reservation if you want a specific IP... I rarely do static assignments, usually reservations unless it's a DC or something like that.
You can do this if you know 100% that the DHCP server does not exist on a VM running on that host.
The Hypervisor hosts are one of the few things I set a static on. But not until it is all teamed and such.
-
@jaredbusch said in Building a Hyper-V 2016 host Take 2:
You can do this if you know 100% that the DHCP server does not exist on a VM running on that host.
Yeah, if it is, you:
- Set static IP on your hyper-v host
- Set static IP on your DHCP VM on above host
- Set static IP on your DC on above host
- Set DHCP VM to start up first when you boot up the host
@jaredbusch said in Building a Hyper-V 2016 host Take 2:
The Hypervisor hosts are one of the few things I set a static on. But not until it is all teamed and such.
Right
-
A reminder to myself
-
@Dashrender whoa, back from the dead.
-
@scottalanmiller said in Building a Hyper-V 2016 host Take 2:
@Dashrender whoa, back from the dead.
Look who is talking....
-
@JaredBusch said in Building a Hyper-V 2016 host Take 2:
@scottalanmiller said in Building a Hyper-V 2016 host Take 2:
@Dashrender whoa, back from the dead.
Look who is talking....
Hey, takes a zombie to know a zombie
-
@scottalanmiller said in Building a Hyper-V 2016 host Take 2:
@JaredBusch said in Building a Hyper-V 2016 host Take 2:
@scottalanmiller said in Building a Hyper-V 2016 host Take 2:
@Dashrender whoa, back from the dead.
Look who is talking....
Hey, takes a
zombienecromancer to know azombienecromancerI've FTFY
-
FYI - Hyper-v 2019 currently is broken. The March 2019 update supposedly fixes the RDP issue.
Though you still can't run
Set-NetFirewallRule -DisplayGroup 'Windows Firewall Remote Management' -Enabled true -
@Dashrender said in Building a Hyper-V 2016 host Take 2:
FYI - Hyper-v 2019 currently is broken. The March 2019 update supposedly fixes the RDP issue.
Though you still can't run
Set-NetFirewallRule -DisplayGroup 'Windows Firewall Remote Management' -Enabled trueWhat about PowerShell Remoting, that still working?
-
@Dashrender said in Building a Hyper-V 2016 host Take 2:
FYI - Hyper-v 2019 currently is broken. The March 2019 update supposedly fixes the RDP issue.
Though you still can't run
Set-NetFirewallRule -DisplayGroup 'Windows Firewall Remote Management' -Enabled trueList things form the local console.
Get-NetFirewallRule | fl Name,DisplayGroupEdit better solution (on Hyper-V Server 2012R2):
Get-NetFirewallRule | Group-Object -Property DisplayGroup | Format-Table -Property Count,Name
-
Looks like they might have renamed it
-
@Dashrender said in Building a Hyper-V 2016 host Take 2:
Looks like they might have renamed it
See my edit.
-
New command for firewall remote management
Set-NetFirewallRule -DisplayGroup 'Windows Defender Firewall Remote Management' -Enable true -
just to show the list
-
I can confirm that RDP works again.
