Installing Hyper-V 2016

black3dynamite

@dashrender said in Installing Hyper-V 2016:

Hyper-V installer saw my disk, I parsed off 80 GB for Hyper-V and gave the rest to another partition for VMs.
Installation took about 45 mins (iDRAC on this server maxes at 100 Mb/s).

Upon first boot, you have to provide an Adminstrator password - Set it and then reboot.

On the second boot I changed the computer name, and reboot.
https://i.imgur.com/2D3BAll.png

Now on the third reboot I'll join the AD.
https://i.imgur.com/egcmcId.png

Oddly I was prompted for a new computer name after joining the domain and providing my username/password to complete that. I gave it the same name I already changed to.
It's possible that MS expects that most will need/want a new computer name when joining a domain, so perhaps they just do it by default after you joing a Hyper-V host to a domain, I'm not sure yet.

Upon reboot, I logged in as a Domain Admin.

When you use the Network ID to join a domain on Windows 10, Windows will prompt you to change computer name too.

JaredBusch

@dashrender said in Installing Hyper-V 2016:

Oddly I was prompted for a new computer name after joining the domain and providing my username/password to complete that. I gave it the same name I already changed to.
It's possible that MS expects that most will need/want a new computer name when joining a domain, so perhaps they just do it by default after you joing a Hyper-V host to a domain, I'm not sure yet.

I do not recall it making me rename it, it just offered me to rename it. Windows has done this for a while. Server 2012 at least. Because I am used to it and always change the machine name at domain join time.

Obsolesce

@jaredbusch said in Installing Hyper-V 2016:

@dashrender said in Installing Hyper-V 2016:

Oddly I was prompted for a new computer name after joining the domain and providing my username/password to complete that. I gave it the same name I already changed to.
It's possible that MS expects that most will need/want a new computer name when joining a domain, so perhaps they just do it by default after you joing a Hyper-V host to a domain, I'm not sure yet.

I do not recall it making me rename it, it just offered me to rename it. Windows has done this for a while. Server 2012 at least. Because I am used to it and always change the machine name at domain join time.

Yeah, you can just hit the "No" button.

JaredBusch

@tim_g said in Installing Hyper-V 2016:

@jaredbusch said in Installing Hyper-V 2016:

@dashrender said in Installing Hyper-V 2016:

Oddly I was prompted for a new computer name after joining the domain and providing my username/password to complete that. I gave it the same name I already changed to.
It's possible that MS expects that most will need/want a new computer name when joining a domain, so perhaps they just do it by default after you joing a Hyper-V host to a domain, I'm not sure yet.

I do not recall it making me rename it, it just offered me to rename it. Windows has done this for a while. Server 2012 at least. Because I am used to it and always change the machine name at domain join time.

Yeah, you can just hit the "No" button.

Thought so.

Dashrender

@jaredbusch said in Installing Hyper-V 2016:

Why did you not check the virtualization settings in BIOS prior to doing anything else?

I did, I verified that virtualization was enabled - though it could have disabled after resetting the BIOS.

Dashrender

@jaredbusch said in Installing Hyper-V 2016:

@tim_g said in Installing Hyper-V 2016:

@jaredbusch said in Installing Hyper-V 2016:

@dashrender said in Installing Hyper-V 2016:

Oddly I was prompted for a new computer name after joining the domain and providing my username/password to complete that. I gave it the same name I already changed to.
It's possible that MS expects that most will need/want a new computer name when joining a domain, so perhaps they just do it by default after you joing a Hyper-V host to a domain, I'm not sure yet.

I do not recall it making me rename it, it just offered me to rename it. Windows has done this for a while. Server 2012 at least. Because I am used to it and always change the machine name at domain join time.

Yeah, you can just hit the "No" button.

Thought so.

There was no button, this was on a text screen on Hyper-v.

JaredBusch

@dashrender said in Installing Hyper-V 2016:

@jaredbusch said in Installing Hyper-V 2016:

@tim_g said in Installing Hyper-V 2016:

@jaredbusch said in Installing Hyper-V 2016:

@dashrender said in Installing Hyper-V 2016:

Oddly I was prompted for a new computer name after joining the domain and providing my username/password to complete that. I gave it the same name I already changed to.
It's possible that MS expects that most will need/want a new computer name when joining a domain, so perhaps they just do it by default after you joing a Hyper-V host to a domain, I'm not sure yet.

I do not recall it making me rename it, it just offered me to rename it. Windows has done this for a while. Server 2012 at least. Because I am used to it and always change the machine name at domain join time.

Yeah, you can just hit the "No" button.

Thought so.

There was no button, this was on a text screen on Hyper-v.

Then it offered a choice. most likely hit enter to keep same.

DustinB3403

@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.

JaredBusch

@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.

DustinB3403

@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.

bnrstnr

@jaredbusch said in Installing Hyper-V 2016:

Not much different than KVM.

Way more complicated than XS though.

JaredBusch

@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

JaredBusch

@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.

DustinB3403

@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.

JaredBusch

@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 native sconfig menu system.

bnrstnr

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.

JaredBusch

@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.

bnrstnr

@jaredbusch Maybe it was never best practice, probably just bad advice from SW for having a single host? I can't remember for sure.

JaredBusch

@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.

brianlittlejohn

@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.