Installing Hyper-V 2016

Dashrender

This post is now old

I've create a new post that answered a lot of the troubles I ran into while setting up Hyper-V 2016 over here.

I figured I'd spend some space documenting my getting Hyper-V setup on a hand me down Dell R710.

First things first, one drive was registering SMART errors, so the H700 RAID controller wouldn't allow it to be a part of the array. This left me with 5 working disks. I decided to use only 4 in a RAID 10.

This unit has the enterprise iDRAC 6 enabled, so I wiped the configuration from the previous owners, and setup my own user/password via the F10 System Services prompt during boot. I choose to wipe the hardware config and start over. Then I set the iDRAC password and logged in.
https://i.imgur.com/72fDD60.png

As you can see here I opened the remote console and the Virtual Media console.
https://i.imgur.com/G5S7ioE.png

I choose the Hyper-V ISO, but it wouldn't mount by default, instead you get this error
https://i.imgur.com/wQe7E3c.png
Either Virtual Media is detached or Virtual Media redirection for the selected virtual disk is already in use.
To solve this, return to the iDRAC webpage, navigate to System (on the left) Console/Media (tab on the top) Configuration.
https://i.imgur.com/foBnbO9.png

Change Status from Detach to Auto Mount, click apply. You'll be warned that users will be temporarily disconnected, but no one will be forced to log back in.
https://i.imgur.com/xAK9pkW.png

Now when you click the box under Mapped next to your added ISO, it will populate
To eject a disk from the command line
powershell "(new-object -COM Shell.Application).NameSpace(17).ParseName('D:').InvokeVerb('Eject')"

Reboot the server, this time press F11 to choose the boot option (I actually booted into the BIOS and changed it to UEFI mode), Choose to boot from your Virtual CD/DVD.
You should see Windows starting to boot (I'm booting to the Hyper-V 2016 ISO).

Dashrender

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.

Dashrender

From my Windows 10 pro 1709 machine (with 1709 RSAT tools installed), I'm logged in as a non local admin user, I lauch Hyper-V Manager as a Domain Admin.

Right click Hyper-V Manager in the menu, choose Connect to server choose Another computer:,
https://i.imgur.com/F9ps2kg.png

Fill in the name of my Hyper-V host - and error.
Quick search on Google turns up I need to run
powershell Enable-PSRemoting
on the Hyper-V host to allow remote control access.

The command requires powershell at the front unless you launch a powershell prompt on the Hyper-V server.
The command runs fine, I return to Windows 10 and Hyper-V Manager, add it again, and it's there!
https://i.imgur.com/bY658lR.png

Dashrender

Now to open up the needed ports to manage things like Computer Management.

Dashrender

Crap

https://i.imgur.com/vb39oDv.png

Now to see if there are options I can enable in the BIOS/UEFI.

Dashrender

hold 4

JaredBusch

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

JaredBusch

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

Also, you need to setup your network team and such all before you go playing with Hyper-V Manager.

JaredBusch

Then you open Hyper-V manager and setup your vSwitch and your default locations and such.

JaredBusch

Thyen you can finally worry about creating a VM.

Obsolesce

You can configure NIC Teaming and all that via "Server Manager" on a Win10 desktop if you want to do it via GUI. Same interface as on Server GUI.

JaredBusch

@tim_g said in Installing Hyper-V 2016:

You can configure NIC Teaming and all that via "Server Manager" on a Win10 desktop if you want to do it via GUI. Same interface as on Server GUI.

I do not run RSAT on my desktop. I only enable Hyper-V Manager.

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.