Installing Hyper-V 2016

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.

Obsolesce

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

Obsolesce

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

scottalanmiller

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

hobbit666

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

i3

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

dbeato

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

hobbit666

@i3 I'll give that a try when I get 10.

Dashrender

I'm still working on this.
I've confirmed that my processors support SLAT (Intel EPT) E5645.

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

I also confirmed that virtualization was/is enabled.
https://i.imgur.com/AcTk86q.png

I did find this though, SR-IOV was disabled. So I've enabled it.
https://i.imgur.com/N2U2EMu.png

I haven't tried making a VM yet because I'm trying to update all the other firmware first and between the rest of my normal duties and trying to find something that would boot correct and update the hardware, I haven't been able update it yet.

JaredBusch

Dell makes a bootable update tool.

Dashrender

@jaredbusch said in Installing Hyper-V 2016:

Dell makes a bootable update tool.

Yeah I made two USB sticks and a DVD with the ISO, and the system wouldn't boot from them. I finally get the update to run when mounted as a Virtual DVD via iDRAC.

Obsolesce

If you don't mind downloading a large ISO, the Dell Server Update Utility is really great.

Dashrender

@tim_g said in Installing Hyper-V 2016:

If you don't mind downloading a large ISO, the Dell Server Update Utility is really great.

yeah I downloaded the 10 GB ISO, but it didn't appear to be bootable, and when I mounted it virtually to the server, it would not boot via iDRAC.

I have managed to get some of the onboard devices to update via the bootable ISO via iDRAC. I'm now back inside USC and it's downloading and updating the DUP and the iDRAC, everything else was already up to date via the ISO. So I have progress. In fact it just rebooted from installing iDRAC6 update to 2.90.

dbeato

@dashrender said in Installing Hyper-V 2016:

@jaredbusch said in Installing Hyper-V 2016:

Dell makes a bootable update tool.

Yeah I made two USB sticks and a DVD with the ISO, and the system wouldn't boot from them. I finally get the update to run when mounted as a Virtual DVD via iDRAC.

And you couldn't use the Lifecycle controller to update the System?

Obsolesce

@dashrender said in Installing Hyper-V 2016:

@tim_g said in Installing Hyper-V 2016:

If you don't mind downloading a large ISO, the Dell Server Update Utility is really great.

yeah I downloaded the 10 GB ISO, but it didn't appear to be bootable, and when I mounted it virtually to the server, it would not boot via iDRAC.

I have managed to get some of the onboard devices to update via the bootable ISO via iDRAC. I'm now back inside USC and it's downloading and updating the DUP and the iDRAC, everything else was already up to date via the ISO. So I have progress. In fact it just rebooted from installing iDRAC6 update to 2.90.

Do it in the OS. It works for Linux and Windows... no GUI needed.

Dashrender

@dbeato said in Installing Hyper-V 2016:

@dashrender said in Installing Hyper-V 2016:

@jaredbusch said in Installing Hyper-V 2016:

Dell makes a bootable update tool.

Yeah I made two USB sticks and a DVD with the ISO, and the system wouldn't boot from them. I finally get the update to run when mounted as a Virtual DVD via iDRAC.

And you couldn't use the Lifecycle controller to update the System?

Not originally, it was complaining about something. I read online that it had to be a certain version before it would work again, so updating via the ISO got me that far, then I used Lifecycle to get the rest of the way there.

Dashrender

@tim_g said in Installing Hyper-V 2016:

@dashrender said in Installing Hyper-V 2016:

@tim_g said in Installing Hyper-V 2016:

If you don't mind downloading a large ISO, the Dell Server Update Utility is really great.

yeah I downloaded the 10 GB ISO, but it didn't appear to be bootable, and when I mounted it virtually to the server, it would not boot via iDRAC.

I have managed to get some of the onboard devices to update via the bootable ISO via iDRAC. I'm now back inside USC and it's downloading and updating the DUP and the iDRAC, everything else was already up to date via the ISO. So I have progress. In fact it just rebooted from installing iDRAC6 update to 2.90.

Do it in the OS. It works for Linux and Windows... no GUI needed.

I only had Hyper-V installed on it. I'm good to go now though.

Dashrender

All updated and started over
Rebuilt the RAID array for S&Gs - the firmware update actually took the SMART erroring drive out of error state, so I'm at 6 drives in RAID 10 now.
Used iDRAC to mount Hyper-V 2016 ISO, set system to UEFI Boot mode and installed Hyper-V.

During the install I gave 80 GB to Hyper-V (which for those that follow UEFI setups know this was cut into 4 partitions - 79.5 GB left for the drive) and formatted the rest for a drive.

First boot of Hyper-V 2016 requires changing the password then this.
https://i.imgur.com/nPouSeC.png

Some things of note - #4 already shows that Remote Management is enabled - huh.

Now JB says that 2016 will ask to change the computer name while joining a domain, so I'll give that a try.

Domain/Workgroup:
https://i.imgur.com/viZ1vW3.png

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

Prompted for the password of the provided account to join the domain.
https://i.imgur.com/oD8KRm5.png

Now prompted that a reboot will be required. (no image)

You are asked if you want to change the computer name before restarting?
https://i.imgur.com/CxZftxD.png

Click yes and enter the new computer name.
https://i.imgur.com/MKCJwa6.png

You're prompted for the domain credentials again to allow the name change - this just seems stupid - why not ask about changing the name first?
Like above, you get a black window to enter your password into, followed by a notice that you need to reboot to apply the change.

Now we see the normal reboot prompt.
https://i.imgur.com/ff2C0Tr.png

Yes and we're rebooting.

Dashrender

Upon rebooting, you have to press ESC several times to get to a point where you can put in a domain user instead of the local Admin account.

Once logged in I still noticed
https://i.imgur.com/TKEwcWJ.png

So I launched Hyper-V Manager from my Windows 10 domain joined PC, tried to add my new host to it - and it worked like a champ.
https://i.imgur.com/LdASK3x.png

Now I can configure the desired Hyper-V settings.

I tried connecting from Computer Manager (launched using Run As domain admin) and got this
https://i.imgur.com/Jnt1iUU.png

So it appears that you still need to open some firewall rules to allow other remote access.

JaredBusch

@dashrender said in Installing Hyper-V 2016:

Upon rebooting, you have to press ESC several times to get to a point where you can put in a domain user instead of the local Admin account.

I ranted about this back in January.
https://mangolassi.it/topic/12296/my-experiences-with-hyper-v-server-2016/7