Give an administrator a command-line tool ... and watch how quickly that admin searches the Internet for a GUI counterpart. But what if the CLI (command-line interface) is the only way to accomplish certain administrative tasks? Well, you might balk. That is why I stick with Windows; it has plenty of GUI interfaces.
And yet, some aspects of Exchange 2007's messaging infrastructure can be configured only through the command-line Exchange Management Shell (built on PowerShell). And with the new Server Core version of Server 2008, it might be time for network admins to re-evaluate their view of the CLI for the sake of their own professional advancement. The reason? Server Core takes the Windows out of Windows and only presents a CLI.
Don Jones, a Microsoft MVP (most valuable professional) for PowerShell says, "The GUI is ultimately a handicap to one's career. I think Server Core represents a low-risk way to start embracing the CLI." So Microsoft is steering admins back to the CLI through its focus on Server Core and PowerShell: "More and more is built on the CLI. Providing people with GUI crutches is like giving your kid Velcro shoes -- it saves some time now, but eventually he'll still have to learn to tie shoelaces, and the longer you put that off the harder it'll be," Jones says.
Server Core was designed, not as some torture device for admins, but rather as way to reduce the "attack surface" on the server by avoiding the installation of features that aren't necessary. For example, if you know you want a server to act as a DNS server, do you really need to have all the additional GUI aspects of the server installed? Absolutely not! Some of those features and services are simply targets to be exploited. So, when installing Server 2008, you can choose to install the Server Core version of the OS.
Once Server Core is installed, Windows Server greets you with a traditional command prompt. You may wonder why you aren't greeted with PowerShell, what with all the talk of its being the CLI of the future. But the fact is it requires the .Net Framework, which isn't supported in Server Core. Remember: The whole idea of Server Core is a smaller footprint and modularized architecture.
There are tricks to get PowerShell up and running in Server Core, if you do the Web searches, but you are better off waiting for the Framework Team to come up with the Server Core flavor of .Net before you start opening up security holes in your Server Core server.