Windows Admins Need To Prepare For GUI-Less Server

[FN-GM]

I found this today, i thought some of us might want a read - Windows Admins Need To Prepare For GUI-Less Server - Slashdot

[synaesthesia]

Interesting. That'll be Powershell stepping forwards then.

[jamesreedersmith]

Windows server core then?

[AngryTechnician]

Not a problem as long as they continue to produce admin MMC snapins so we can administer from the workstation. Omitting any kind of GUI management isn't 'adapting to the market', it's just lazy. I already resent the amount of functionality in Exchange 2010 for which the only exposed interface is Powershell. All it does is slow down basic configuration for no good reason.

[X-13]

'I'm well aware that many Windows admins out there aren't looking forward to a GUI-less server operating system from Microsoft. ... I'm sure Microsoft has, too.They're proceeding anyway. We have two choices: adapt or die.'"

^ From Windows consultant and author Don Jones.

Adapt or Die? [censored] that. I'll just switch to Linux/GNU. Problem?

[DrCheese]

Adapt or Die? [censored] that. I'll just switch to Linux/GNU. Problem?

Well yeah, considering that's going to be much worse when it comes to CLI only configuration. :P

I already resent the amount of functionality in Exchange 2010 for which the only exposed interface is Powershell.

Yup, it was even worse when 2007 first came out as that was the first release they built on top of powershell. It wasn't until SP1 did they bother readding some basic features back to the GUI

[X-13]

Well yeah, considering that's going to be much worse when it comes to CLI only configuration. :P

sudo apt-get update
sudo apt-get install ubuntu-desktop

Now it's Desktop + Server.

Or...

sudo apt-get install gnome-desktop-environment

Server with GUI.

I say again... Problem?

[zag]

Not a problem as long as they continue to produce admin MMC snapins so we can administer from the workstation. Omitting any kind of GUI management isn't 'adapting to the market', it's just lazy. I already resent the amount of functionality in Exchange 2010 for which the only exposed interface is Powershell. All it does is slow down basic configuration for no good reason.

Normally I would agree but having used live@edu extensively now I have never needed a GUI. Just a simple web interface for adding users and groups and powershell if you need it.

Email systems really don't need to be complicated.

[Domino]

I say again... Problem?

I think @DrCheese was actually agreeing with you..... ;-)

Saying that windows would be much worse CLI only...

[CyberNerd]

Every release of windows gets more like unix. One day they'll see sense and just do what apple did and clone BSD.

[X-13]

I think @DrCheese was actually agreeing with you..... ;-)

Saying that windows would be much worse CLI only...

I've only had one coffee and half a cigarette...

I've said it once, and I'll say it again; "I cannot brain today, I have teh dumb."

[AngryTechnician]

Normally I would agree but having used live@edu extensively now I have never needed a GUI. Just a simple web interface for adding users and groups and powershell if you need it.

Email systems really don't need to be complicated.

And yet they are!

Simple example: enabling MailTips. Should be a nothing more than a tickbox in the EMC, but instead you have to look up the PowerShell command. Granted, it's not a complicated command, but you still have to look it up when it could just be a sodding tickbox.

For a more complicated example, I would say that even the simplest transport rule is a lot easier to set up in the EMC than using PowerShell. I don't even want to think about trying a complex transport rule on the command line.

[sted]

from what i read the gui is off by default but can still be enabled if you want it

hopefully its better than virtual server bare metal i managed to get that working once and cant repeat it cant get mmc consoles to actually connect to do owt from a workstation

[sonofsanta]

I'm all for exposing more functionality via CLI, but what's the point in adding it there and taking it away from the GUI? Why are we going backwards? Granted, the GUI is not the right solution for every problem and some tasks are inherently easier via CLI (e.g. creation of new year 7 accounts via script), but isn't the converse true as well?

I don't understand why limiting my options and forcing me to waste time memorising commands and relearn server configuration is a step forward. An OS should empower a user.

[sted]

I'm all for exposing more functionality via CLI, but what's the point in adding it there and taking it away from the GUI? Why are we going backwards? Granted, the GUI is not the right solution for every problem and some tasks are inherently easier via CLI (e.g. creation of new year 7 accounts via script), but isn't the converse true as well?

I don't understand why limiting my options and forcing me to waste time memorising commands and relearn server configuration is a step forward. An OS should empower a user.

i think the idea is to make the server do less so its less vunerable and needs less updating. it also means there is little point in using the console itself so its easier to manage from "your desk" rather than booting up rdp or actually going to the server room (though the amount of time it takes to install rsat on win7 for a few consoles is silly)