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 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.
-
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.pngI did find this though, SR-IOV was disabled. So I've enabled it.
https://i.imgur.com/N2U2EMu.pngI 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.
-
Dell makes a bootable update tool.
-
@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.
-
If you don't mind downloading a large ISO, the Dell Server Update Utility is really great.
-
@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.
-
@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?
-
@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.
-
@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.
