Installing Hyper-V 2016
-
@jaredbusch said in Installing Hyper-V 2016:
Why did you not check the virtualization settings in BIOS prior to doing anything else?
@jaredbusch said in Installing Hyper-V 2016:
Also, just joining to a domain and attempting to manage will not work. You still need to enable a few things int he host system firewall.
https://mangolassi.it/topic/12296/my-experiences-with-hyper-v-server-2016/10
@jaredbusch said in Installing Hyper-V 2016:
Also, you need to setup your network team and such all before you go playing with Hyper-V Manager.
@jaredbusch said in Installing Hyper-V 2016:
Then you open Hyper-V manager and setup your vSwitch and your default locations and such.
So many steps to go through to get Hyper-V setup. My god.
@jaredbusch said in Installing Hyper-V 2016:
Thyen you can finally worry about creating a VM.
-
@dustinb3403 said in Installing Hyper-V 2016:
@jaredbusch said in Installing Hyper-V 2016:
Why did you not check the virtualization settings in BIOS prior to doing anything else?
@jaredbusch said in Installing Hyper-V 2016:
Also, just joining to a domain and attempting to manage will not work. You still need to enable a few things int he host system firewall.
https://mangolassi.it/topic/12296/my-experiences-with-hyper-v-server-2016/10
@jaredbusch said in Installing Hyper-V 2016:
Also, you need to setup your network team and such all before you go playing with Hyper-V Manager.
@jaredbusch said in Installing Hyper-V 2016:
Then you open Hyper-V manager and setup your vSwitch and your default locations and such.
So many steps to go through to get Hyper-V setup. My god.
@jaredbusch said in Installing Hyper-V 2016:
Thyen you can finally worry about creating a VM.
Not much different than KVM.
-
@jaredbusch said in Installing Hyper-V 2016:
@dustinb3403 said in Installing Hyper-V 2016:
@jaredbusch said in Installing Hyper-V 2016:
Why did you not check the virtualization settings in BIOS prior to doing anything else?
@jaredbusch said in Installing Hyper-V 2016:
Also, just joining to a domain and attempting to manage will not work. You still need to enable a few things int he host system firewall.
https://mangolassi.it/topic/12296/my-experiences-with-hyper-v-server-2016/10
@jaredbusch said in Installing Hyper-V 2016:
Also, you need to setup your network team and such all before you go playing with Hyper-V Manager.
@jaredbusch said in Installing Hyper-V 2016:
Then you open Hyper-V manager and setup your vSwitch and your default locations and such.
So many steps to go through to get Hyper-V setup. My god.
@jaredbusch said in Installing Hyper-V 2016:
Thyen you can finally worry about creating a VM.
Not much different than KVM.
I know, it's just a quip.
Hypervisor devs need to streamline the process a bit.
-
@jaredbusch said in Installing Hyper-V 2016:
Not much different than KVM.
Way more complicated than XS though.
-
@dustinb3403 said in Installing Hyper-V 2016:
So many steps to go through to get Hyper-V setup. My god.
Let's look at each step you have to take with any hypervisor
- Verify BIOS Virtualization
- For most SMB, setup hardware RAID 10 array
- Install Hypervisor on to partition of RAID 10 array
- Add guest storage location to Hypervisor
- Create NIC team.
- Create vSwitch using team
- Hyper-V only: add some basic firewall rules
- Hyper-V only: join to domain
- Set your defaults for guests such as storage locations
- Create VMs
-
@bnrstnr said in Installing Hyper-V 2016:
@jaredbusch said in Installing Hyper-V 2016:
Not much different than KVM.
Way more complicated than XS though.
Totally not.
-
@jaredbusch said in Installing Hyper-V 2016:
@bnrstnr said in Installing Hyper-V 2016:
@jaredbusch said in Installing Hyper-V 2016:
Not much different than KVM.
Way more complicated than XS though.
Totally not.
I have to agree with Jared, not way more complicated, just a bit more tedious when you go through this process on paper.
Having to add firewall rules and joining it to the domain (while not big tasks) do make things more complicated.
-
@dustinb3403 said in Installing Hyper-V 2016:
@jaredbusch said in Installing Hyper-V 2016:
@bnrstnr said in Installing Hyper-V 2016:
@jaredbusch said in Installing Hyper-V 2016:
Not much different than KVM.
Way more complicated than XS though.
Totally not.
I have to agree with Jared, not way more complicated, just a bit more tedious when you go through this process on paper.
Having to add firewall rules and joining it to the domain (while not big tasks) do make things more complicated.
And it is only 4 lines that you can copy/paste into your powershell window.
Joining the domain is part of the nativesconfigmenu system. -
I haven't done this in a while, and back when I did, it was best practice to not join the host to the domain. Which does make managing it far more complicated. It's always been my understanding that joining it to the domain would make managing much easier. I guess I'm still bitter about using that damn hvremote tool.
-
@bnrstnr said in Installing Hyper-V 2016:
I haven't done this in a while, and back when I did, it was best practice to not join the host to the domain. Which does make managing it far more complicated. It's always been my understanding that joining it to the domain would make managing much easier. I guess I'm still bitter about using that damn hvconfig tool.
It has never been a best practice to not be domain joined. Can you provide some documentation stating as much?
It has always been Microsoft's recommendation that it should be domain joined.
-
@jaredbusch Maybe it was never best practice, probably just bad advice from SW for having a single host? I can't remember for sure.
-
@bnrstnr said in Installing Hyper-V 2016:
@jaredbusch Maybe it was never best practice, probably just bad advice from SW for having a single host? I can't remember for sure.
That is entirely likely. SW people love to say that you should never domain join because you cannot log in if the guests fail. Just WTF. There is always the original local adminsitrator account on the hypervisor.
-
@jaredbusch said in Installing Hyper-V 2016:
@bnrstnr said in Installing Hyper-V 2016:
@jaredbusch Maybe it was never best practice, probably just bad advice from SW for having a single host? I can't remember for sure.
That is entirely likely. SW people love to say that you should never domain join because you cannot log in if the guests fail. Just WTF. There is always the original local adminsitrator account on the hypervisor.
and cached credentials.
-
@jaredbusch said in Installing Hyper-V 2016:
@bnrstnr said in Installing Hyper-V 2016:
@jaredbusch said in Installing Hyper-V 2016:
Not much different than KVM.
Way more complicated than XS though.
Totally not.
I agree. Everything seems complicated at first when you aren't familiar with something and compare it against something you are familiar with.
Take a step back and look at the steps Jared laid out.
The only two things he lists that are Hyper-V only, are beneficial features that you'd want to do to enhance your experience over other hypervisors... at least the joining to domain part.
But each step is basically the same with any hypervisor. But with KVM for example, still need to enable "psremoting" which is like enabling SSH on linux so you can remotely manage KVM and with GUI tools. Same thing kinda.
-
@jaredbusch said in Installing Hyper-V 2016:
@bnrstnr said in Installing Hyper-V 2016:
@jaredbusch Maybe it was never best practice, probably just bad advice from SW for having a single host? I can't remember for sure.
That is entirely likely. SW people love to say that you should never domain join because you cannot log in if the guests fail. Just WTF. There is always the original local adminsitrator account on the hypervisor.
Only idiots can't log in to their hypervisors if for some reason their poorly implemented domain fails.
That's definitely a SW-only thing. -
@bnrstnr said in Installing Hyper-V 2016:
@jaredbusch Maybe it was never best practice, probably just bad advice from SW for having a single host? I can't remember for sure.
Definitely bad SW advice. That's one of those perennial myths that gets repeated there. Just like always having a physical DC - you ask poeple why they recommend these things and quickly you always see tha tthey had no idea why and were just saying it. SW has a culture of "recommend anything, no one will quesiton it" and so people start doing just that. So teh amount of myth that gets repeated is really high.
-
@JaredBusch @scottalanmiller I think I've been burned by this.
I have a HyperV 2012 server not joined to their domain (seeds), since I've had a few PC's/Laptops and I working in a different domain (HQ) I can't manage it anymore and can't remember what I did to manage it.
One solution was to use 5nine manager but that doesn't even work.At the moment I have 5nine manager installed on VM on the host that I RDP into and check the other VMs from lol
Hoping soon they will want the server here at HQ all on the same domain etc so I reinstall on KVM (XenServer at least)
-
@hobbit666 said in Installing Hyper-V 2016:
at HQ all on the same domain etc so I reinstall on KVM (XenServer at least)
It has been a while since I was testing this in a workgroup environment, but I had this link in my notes.
http://pc-addicts.com/12-steps-to-remotely-manage-hyper-v-server-2012-core/ -
@jaredbusch said in Installing Hyper-V 2016:
@bnrstnr said in Installing Hyper-V 2016:
@jaredbusch Maybe it was never best practice, probably just bad advice from SW for having a single host? I can't remember for sure.
That is entirely likely. SW people love to say that you should never domain join because you cannot log in if the guests fail. Just WTF. There is always the original local adminsitrator account on the hypervisor.
Exactly this!
-
@i3 I'll give that a try when I get 10.
