Best Practices - DC in Hyper-V Environment.
-
@thecreativeone91 said:
@thanksajdotcom said:
@scottalanmiller said:
@thecreativeone91 said:
ESXi isn't free with all feature. ESXi does have a free version but the essentials license are $560/year if you want updates which is for three servers (with a max of 2 cpu's per server).
HyperV isn't free with all the features either. But with more than ESXi. I think blocking the backup API was SO foolish on VMware's part. It made their free version never make sense. Either XenServer or HyperV is always a better choice.
I get what you mean but you can back up the machines, just not at the block level. While this is a limiter, for someone who uses it in a very small business or even at home, this isn't really an issue. I use my UEB to back up at the file level. It's not as efficient and recovery times are slower, but it works.
Traditional Backups don't understand Virtulization They also may not be hardware/platform independent. You also can't do snapshots inside of the OS.
Exactly. That's what I said.
-
@thecreativeone91 said:
I do the DC's (including the one with the PDC emulator) as VM's. I don't usually put the VM host in the domain but, with hyper-v you pretty much have to. If you have more than one host and DC's and each host it's not a big deal. if you only have one host you really need to look into putting a second DC somewhere even if it's physical.
This makes absolutely zero sense.
Hyper-V Server is designed to be joined to the domain and as has been pointed out a pain in the ass to manage if it is not.
It does not matter if your only DC (or both) is on the host and fails to come up,
You can ALWAYS log in locally with the domain account and cached Kerberos credentials or if those are expired, you can STILL log in with the local account setup when the Hyper-V server was initially installed.
Basically, there is never a reason NOT to join the Hyper-V servers to the domain.
-
@JaredBusch said:
This makes absolutely zero sense.
Maybe to you. But most people don't domain join the VM host (espcially if it's not Hyper-v) as both me @scottalanmiller and @GregoryHall said you really want to make sure Domain is redundant if you join the vm host.
If you are running the full server with hyper-v role you can RDP into it to manage no problem without a domain, If you have the hyper-v only server there are just a few powershell commands needed to enable management without a domain via RTAS. There's also free third party tools that can be run remotely or directly on the server.
Best option is still to put a second DC on @MattSpeller 's second VM host.
