22
I had to migrate from Samba AD to Windows Server AD and I'm sad (RIP Samba) (lemmy.zip)
submitted 7 months ago by possiblylinux127@lemmy.zip to c/sysadmin@lemmy.world
14 comments fedilink hide all child comments

Samba is amazing, Windows server is a lot less so. The problem with Windows server is that it takes tons of steps to do basic things. On Samba I had Samba tool and it was very nice and friendly. On Windows server you have a ton of different management panels.

If there was a way I could hold off I would but due to changing requirements I didn't have much of a choice. (We needed Windows Server bare metal and I was not about to go and buy another machine.)

you are viewing a single comment's thread
view the rest of the comments
[-] vk6flab@lemmy.radio 4 points 7 months ago

In the same way as if your Windows Server on bare metal doesn't start after an update, via the console.

[-] slazer2au@lemmy.world 1 points 7 months ago

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.

[-] computergeek125@lemmy.world 5 points 7 months ago* (last edited 7 months ago)

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.

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
DarraignTheSane@lemmy.world
00Lemming@lemmy.world
L3s@lemmy.world