Newer versions of Windows can give you the exact Powershell code it's executing based on what you've configured in the gui. This is still extremely inconsistent across Windows services though. I don't know that I'd feel comfortable running a headless windows server yet. Too much stuff still assumes you'll use the gui for most things.

[–] hemko@lemmy.world 5 points 1 year ago* (last edited 1 year ago) (1 children)

To be honest, if you really need Windows servers you should run core if possible. Basically all Microsoft's management shit can be run remotely from your jump/management host. That said a lot of shit requires gui and refuses to run on core, like adsync

[–] SeeJayEmm@lemmy.procrastinati.org 3 points 1 year ago (1 children)

Is there a significant performance difference? I'm assuming the attack surface is lower.

[–] hemko@lemmy.world 3 points 1 year ago* (last edited 1 year ago)

There's slight difference in resource usage of course, which does scale if you're unlucky enough to have lot of them.

Minimum ram required is 512mb for core, 2gb for desktop experience so we can safely assume keeping the gui usable eats some 1.5gb memory. 500 servers adds some 750gb overhead in theory.

Then there's of course the fact that less bloat will generally add up to less problems. Ever rdp to a server and start menu refuses to open or other weird gui shit. That's just wasting your time.