22
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 23 Apr 2024
22 points (89.3% liked)
Sysadmin
7721 readers
190 users here now
A community dedicated to the profession of IT Systems Administration
No generic Lemmy issue posts please! Posts about Lemmy belong in one of these communities:
!lemmy@lemmy.ml
!lemmyworld@lemmy.world
!lemmy_support@lemmy.ml
!support@lemmy.world
founded 2 years ago
MODERATORS
If you are using LDAP auth for your hypervisor (vsphere as an example) how do you auth after a kaboom event and your AD server VMs have not auto started.
I remember reading somewhere (prob /r/Sysadmin) that having one bare metal AD server just incase everything goes offline.
You connect directly to the ESXi host with root. Because you're going to have to boot up vCenter in addition to the DC anyway when you're using SSO. I would use DRS rules to prefer host1 for vCenter and the PDCe for that reason.
Only in the very early days of virtualization (2008-2012) did I recommend keeping a physical server around. I know a lot more now than I did then.
But anymore, I don't recommend using SSO for hypervisors or backup infrastructure. It's better to add another wall in front of an attacker trying to laterally move onto these critical platforms for ransom, data exfiltration, etc.
And in reality, these "kaboom events" aren't terribly common unless you've neglected some other part of your infrastructure.
In the same way as if your Windows Server on bare metal doesn't start after an update, via the console.
I recall that ESXi doesn't let you do crap from the console. Just configure management. Be interesting to hear what options Prox and Hyper-V may have.
You use console to turn on embedded shell then Ctrl+Alt+Fn over to it (I forget whether it's on f1 or f2), then you can use
esxcli
and all the rest of that to fix it up.Once you get enough networking/storage pieces sorted out you can get back into the management HTML UI and SSH
Then when you're done fixing, turn shell and SSH back off.