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
7719 readers
248 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
Why did you need a bare metal anything?
I realise that with the enshitification of VMware, there's one less viable option for virtualisation, but it's not the only one around.
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.
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
esxcliand 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.