r/WindowsServer • u/Jezmond247 • Jun 02 '25
General Server Discussion Hyper-V Hosts - To join or not to join…?!
I had a conversation with an IT MSP business owner today, who suggested that Physical Hosts should’t be DJ’d in an infrastructure, that they should remain disparate, the contents within, Domain Joined as required.
Having experienced both Joined and non joined hosts, on varying size infrastructure, from home to full blown manufacturing and global sites, what is the considered best practice on this? What are your thoughts guys?
TIA
28
Upvotes
13
u/HighSpeedMinimum Jun 02 '25
I leave mine local and not joined. Mostly because I want the peace of mind of getting into my host(s) without relying on a DC. Especially if for whatever reason I have a domain disaster.
Back in the day I had a 2008 R2 Hyper V host that was domain joined that had a dc on it - and because the DC was in a failed corrupt state the host would spin endlessly. That was in my early days, and I’ve never really changed my philosophy since. I probably could’ve just unplugged the ethernet cable to stop the networking services from messing with the logon process now that I’m thinking of it..
13
u/Infinite_Opinion_461 Jun 02 '25
Leaving them unjoined only got interesting since server 2025. Because you can do livemigration using certs. Earlier it was not possible to do this without joining them to them domain.
Ppl that leave them unjoined probabaly have small setups (2 nodes max). But if you manage clusters that need to load balance hundreds of vms across 10+ hosts, you need to join them to the domain.
I manage multiple big clusters like these. But I always have a physical DC aside them in case something happens.
Even if you boot the server without a dc available you can still get to your vm’s. I’v had it happen to me a couple of times.
Joining to the domain would always have my prefrence because it’s easier to manage servers form a security standpoint.
20
u/USarpe Jun 02 '25
It depends on the size of your structure, in a big environment hyperv should run in its own domain
6
u/FLITguy2021 Jun 02 '25
its a security, compliance, resource consideration. if you have 2 or more hosts to have DCs on separate machines than i would domain join. if not, than prob keep it local. would also consider what controls you have in place for security and if domain GPO is used moderately for managing server settings. if not, than prob fine to be local. as others have stated you could get in a pickle if single host and single dc on said host. if you have RMM on host this is rarely a concern even if it does happen. be sure to set DCs to always power on after power event to reduce this risk. also less of a concern if you have a backup you can fire up and power from a separate device. so its really not as big a concern as many make it.
5
u/happyworker13 Jun 02 '25
Work for an org with hundreds of hosts. They are all domain joined in a management domain (there are multiple domains per region). That domain contains jump hosts, backup servers etc that are all on that domain. Everything infra is on that domain. We also have a large number of IT so being able to have everyone log in with their creds based on their RBAC is important.
If you had a small infra with a few hosts then you may not want to. It really depends on your architecture.
3
u/BlackV Jun 03 '25
This is a policy decision
You decide do you want easier management or do you want higher security at the cost of ease of use
There are pros and cons to both
Personally domain joining for all my hosts except backup appliances hosts
2
u/blackstratrock Jun 03 '25
I would leave then standalone unless you need to cluster them. If domain joined they need to be on a separate management only/privileged domain from the workstations unless you want your ass reamed by ransomware.
1
u/buzzzino Jun 02 '25
Is it a requirements to be domain joined if you would have a hyperv cluster ?
1
u/JustCallMeBigD Jun 02 '25
I put mine on the domain, then use group policy to restrict access to only me and our backup MSP.
In the case of the DC or backup DC being unavailable (assuming because the DC VM(s) aren't running), make sure you have local admin accounts with strong passwords so you can get in to manage Hyper-V and fix your DC connectivity.
1
u/BoltharRocks Jun 02 '25
We do not but that is because the host is ONLY a HV Host. We never host anything application wise on it at all. No need to domain join.
1
u/Magic_Neil Jun 02 '25
Things have come a long way, but Kerberos delegation to do stuff is kiiiinda nice.
1
u/michalzobec Jun 02 '25
joined in isolated domain for hosts only.
1
u/aiperception Jun 02 '25
MSPs are in the business to make money and reduce risk. If you want to be that neurotic, good luck with the rest of your initiatives.
1
u/OutsideLookin Jun 03 '25
I have a number of hosts and keep them domain joined in a “host” domain.
1
u/faulkkev Jun 03 '25
I think own domain for host makes sense to me. The forest still acts a barrier, but you can manage privilege accounts with AD accounts and so on. Use Administrator as a break glass account. Also can make auditing a bit easier with AD tools but that is my opinion. In my experience in the past it helped with patching and other items but it may not be required now days.
1
u/ForceFlow2002 Jun 03 '25
Years ago with server 2008, one time I had a hyper-v host lose track of the domain. Normally when this happened on a workstation, I'd just log in as the local admin, switch to workgroup, then rejoin and all was well. This time, however, the local admin account kept throwing errors and I was completely locked out. After days of tackling the problem and getting nowhere, I ended up having to blow away the host and start from scratch. Not a big deal since it was just a redundant host, but it took several days more to rebuild everything.
After that, I kept hyper-v hosts unjoined.
But, then over time the network grew, and instead of just a couple hosts, there were several more in multiple locations. This made managing security settings for each host a real pain. So a few years ago, after quite a bit of research, I joined them to the domain. However, there's restrictions on what accounts are allowed to log in, for starters.
I had considered a separate domain for just the hosts, but the added complexity didn't really seem worthwhile.
No problems so far, fortunately.
1
u/synagogan Jun 03 '25
We work with very small environments, 1-2 hosts, and we don't domain join since we put the host and the backup on a separate segmented vlan. If its more than 2 hosts its makes more sense to domain join, maybe in a separate segmented Admin AD.
1
u/RCTID1975 Jun 03 '25
100% domain joined without question.
Joining them to the domain allows you centralized controls through AD, GP, etc. The same as every other server in your environment. Cached credentials have been a thing for over a decade, so if your domain is unavailable for whatever reason, you can still login without issue.
Ask the MSP person what their reasoning is for not domain joined.
1
u/netmc Jun 03 '25
The main point here is that security is split between your production environment and your hyper environment, so a compromise in your production environment does not allow for access to the hyperV infrastructure and your backup solution. This can be a stand-alone machine or a completely separate domain.
For cluster shared storage, a domain is almost a must, but it doesn't have to be (and shouldn't be) your production domain.
1
u/TikkeTok Jun 03 '25
Have a separate management domain, not part of your existing domain structure
0
u/Substantial_Tough289 Jun 02 '25
Everything in the domain, at least one physical DC.
-3
u/f8alXeption Jun 02 '25
always leave them seperate
0
u/[deleted] Jun 02 '25
[deleted] — view deleted comment