Back to the command prompt shown below, for those of you who have been staying in GUI land. Perhaps you have been working as an admin for quite some time. You might recall your DOS commands. You may even recall some of your NT 4.0 commands for networking and making server adjustments. But even so, there are some new commands to handle newer Windows Server capabilities that you will have to learn. For example, because the server is installed initially without any roles, you need to install those roles and features manually.
Under Server Core, the commands you need to learn are:
- oclist.exe, to show you a list of which roles and features are already installed, and also to show you the proper spelling and case of those roles and features
- ocsetup.exe, to let you install or uninstall the roles and features you need
There are other commands you need to recall to mind (or learn for the first time) to configure the server: netsh, netdom, and slmgr, to name a few.
If you're concerned that you'll be stuck in the CLI forever, relax. Once configured, the Core Server is still managed in familiar GUI ways. For example, once a role is installed, you can usually work with the familiar MMC console to manage that role remotely.
Plus, even within the CLI-oriented Server Core there are GUI tools that you can bring up. Type Notepad and it appears. Type Taskmgr, and it comes up. You can even type Regedit to alter the registry settings. And a few control panel apps remain accessible, like intl.cpl and timedate.cpl.
Are there GUI crutches to configuring and working with Server Core. Naturally. A quick Web search will show you a tool called Windows 2008 Server Core Configurator from CodePlex as one of those tools. And there are others.
But I tend to agree with Microsoft's Jones, who says, "Everyone seems to be in a rush to find crutches for people who don't like the command line. I'm not sure that we, as the experts, are doing people a favor in that regard: They're simply going to have to become more familiar with the CLI (whether via the [command prompt] or PowerShell) if they want to advance in this profession."
Where do you stand on this matter? Are you a CLI-hater, or are you one who embraces the new Server Core and PowerShell command-line interface?